Header Background Image

Virtualization

CodiLime Glossary

Some common networking terms clearly explained

Glossary /V /

Virtualization

What is virtualization technology in hardware?

Virtualization is technology that makes it possible to create multiple, distinct and secure environments based on one physical hardware system. Such environments are called Virtual Machines (VMs). Software called a hypervisor, which manages the allocation of resources such as CPU (Central Processing Unit or simply processor) memory, storage and others, allows you to split one physical machine into many virtual ones. The resources can be reallocated, if any need arises, e.g. if one VM needs more memory or CPU cycles. The physical hardware with installed hypervisor is called a host, whilst VMs are called guests.

Thanks to virtualization, it is possible to make the most use of computer hardware and thus increase the return on investment (ROI). Instead of having one server on one physical system, you can create many virtual servers (or virtual machines) and assign them necessary computing resources (CPU, memory, storage, etc.). Over-provisioning—assigning extra resources that can be used when needs arise—is a key term here. For example, over-provisioned memory can be used in running an application that is particularly resource-hungry and the VM has to cope with the demand.

Read more:

Thumbnail of an article about Kubernetes: what is it and how you can use it (part 1/2)
CLOUD

Kubernetes: what is it and how you can use it (part 1/2)

Kubernetes is an open-source system for container orchestration enabling automated application deployment, scaling and management. Read this two-part blog post to understand the business perspective on Kubernetes. I will present a brief story of virtualization methods, the key concepts on which Kubernetes is built and how it can help your business when it comes to running containerized applications. The second part covers six main reasons to adopt Kubernetes. First, let’s take a look at the market data on the adoption of Kubernetes.
Thumbnail of an article about How to create a custom resource with Kubernetes Operator
NETWORKS
CLOUD

How to create a custom resource with Kubernetes Operator

While developing projects on the Kubernetes platform I came across an interesting problem. I had quite a few scripts that ran in containers and needed to be triggered only once on every node in my Kubernetes cluster. This could not be solved using default Kubernetes resources such as DaemonSet and Job. So I decided to write my own resource using Kubernetes Operator Framework. How I went about it is the subject of this blog post. When I confronted this problem, my first thought was to use a DaemonSet resource that utilizes initContainers and then starts a dummy busybox container running `tail -f /dev/null` or another command that does nothing.
Thumbnail of an article about Edge computing and virtualization — living on the edge
NETWORKS

Edge computing and virtualization — living on the edge

Cloud offers considerable benefits to businesses. Yet in some cases where low latency is critical, it has serious drawbacks. An emerging paradigm of edge computing is the answer to these problems. In 2016, Cisco announced the beginning of the Zettabyte Era. Since then, the amount of data produced and processed has increased zettafold, if you will. This is especially true when you look at M2M applications (machine-to-machine or more commonly referred to as Internet of Things—IoT) such as video surveillance, healthcare monitoring, the smart home, smart meters and the like.

Get your project estimate

For businesses that need support in their software or network engineering projects, please fill in the form and we’ll get back to you within one business day.

For businesses that need support in their software or network engineering projects, please fill in the form and we’ll get back to you within one business day.

We guarantee 100% privacy.

Trusted by leaders:

Cisco Systems
Palo Alto Services
Equinix
Jupiter Networks
Nutanix