Deploy a VM & Hyperconverged Virtualization
Deploy a VM & Hyperconverged Virtualization
With the components and choices in hand, it's time to actually deploy a virtual machine — and to understand the alternative to piecing compute together at all: hyperconverged infrastructure.
Deploy a Virtual Machine
The exact process varies by cloud provider and VM type, and permissions and access controls still govern instance management throughout — depending on settings, you may be able to over-allocate resources. Here are the general steps for deploying a t2.micro general-purpose instance on AWS. Click through each step.
Hyperconverged Virtualization
Converged virtualization combines CPU, memory, storage, and network configurations into a single entity — but the four components stay independent and can still be separated. Hyperconverged virtualization combines the same four subsystems far more tightly, to the point where they can't be pulled apart.
Hyperconverged deployments run on off-the-shelf hardware, which makes them well suited to private clouds and organizational data centers — easier to deploy and maintain because the entire structure is managed as one unit, rather than specifying individual CPU, GPU, memory, storage, and network components separately.
Worth keeping straight: a hyperconverged environment combines CPU, memory, storage, and networking technologies — it isn't a setting on any one of them. Provisioning cloud resources is mainly about deploying virtualized resources like these, but plenty of other concerns still come into play when planning and deploying cloud services.