I have prepared this blog post to help students to the understanding of the Hypervisor support Matrix introduced by OpenStack . These information are spread along different webs and manuals. Many of sources are Linux / redhat and OpenStack. I have tried to provide more general explanation when possible and reference links to other sources.
The respective feature commands syntax are of course different along various cloud platforms. This version of the blog such a kind of information is not provided. I hope to improve this blog with received comments.
Launch (boot) – Command to launch an instance. Specify the server name, flavor ID (small., large..), and image ID.
Reboot – Soft or hard reboot a running instance. A soft reboot attempts a graceful shut down and restart of the instance. A hard reboot power cycles the instance. By default, when you reboot a server, it is a soft reboot.
Terminate – When an instance is no longer needed, use the terminate or delete command to terminate it. You can use the instance name or the ID string.
Resize – If the size of a virtual machine needs to be changed, such as adding more memory or cores, this can be done using the resize operations. Using resize, you can select a new flavor for your virtual machine and instruct the cloud to adjust the configuration to match the new size. The operation will reboot the virtual machine and take several minutes of downtime. Network configuration will be maintained but connectivity lost during the reboot so this operation should be scheduled as it will lead to application downtime.
Rescue – An instance’s filesystem could become corrupted with prolonged usage. Rescue mode provides a mechanism for access even when the VM’s image renders the instance inaccessible. It is possible to reboot a virtual machine in rescue mode. A rescue VM is launched that allows a user to fix their VM (by accessing with a new root password).
Pause / Un-pause – This command stores the state of the VM in RAM. A paused instance continues to run in a frozen state.
Suspend / Resume – Administrative users might want to suspend / resume an instance if it is infrequently used or to perform system maintenance. When you suspend an instance, its VM state is stored on disk, all memory is written to disk, and the virtual machine is stopped. Suspending an instance is similar to placing a device in hibernation; memory and vCPUs become available to create other instances.
Inject Networking – Allows to set up a private network between 2 or more virtual machines. This network won’t be seen from the other virtual machines nor from the real network.
Inject File – It is a feature that allows to include files during the boot. Normally the target is a root partition of guest images. There are sub features that enable enables further functionality to inspect arbitrarily complex guest images and find the root partition to inject to.
Serial Console Output – It is possible to access VM directly using the TTY Serial Console interface, in which case setting up bridged networking, SSH, and similar is not necessary.
VNC Console – VNC (Virtual Network Computing) is a software for remote control, it is based on server agents installed on the hypervisor. This feature indicates the support of VNC for the hypervisor and VMs.
SPICE Console – Red Hat introduced the SPICE remote computing protocol that is used for Spice client-server communication. Other components developed include QXL display device and driver, etc. solution for interaction with virtualized desktop devices.The Spice project deals with both the virtualized devices and the front-end. It is needed to enable the spice server in qemu and also needs a client to view the guest.
RDP Console – It allows to connect the hypervisor and VMs via Remote Desktop Protocol based console.
Attach / Detach Volume – Allows to add / remove new volume in the volume pool. This feature also allows to add / remove extra Volumes to existing running VMs.
Live Migration – Migration describes the process of moving a guest virtual machine from one host physical machine to another. This is possible because guest virtual machines are running in a virtualized environment instead of directly on the hardware. In a live migration, the guest virtual machine continues to run on the source host physical machine while its memory pages are transferred, in order, to the destination host physical machine.
Snapshot - A snapshot creates a coherent copy of a number of block devices at a given time. Live snapshot if a snapshot taken while a virtual machine is running. Ideal for live backup of guests, without guest intervention.
iSCSI – iSCSI is Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities. This feature of an Hypervisor means that you can add iSCSI based disks to the storage pool.
iSCSI CHAP – Challenge Handshake Authentication Protocol (CHAP) is a network login protocol that uses a challenge-response mechanism. You can use CHAP authentication to restrict iSCSI access to volumes and snapshots to hosts that supply the correct account name and password (or “secret”) combination. Using CHAP authentication can facilitate the management of access controls because it restricts access through account names and passwords, instead of IP addresses or iSCSI initiator names.
Fibre Channel – This feature indicates that the hypervisor support optical fiber connectivity. In particular for Fibre Channel storage network which are cabled and configured with the appropriate Fibre Channel switches. This has implication on how the zones are configured. KVM virtualization with VMControl supports only SAN storage over Fibre Channel. Typically, one of the fabric switches is configured with the zoning information. Additionally, VMControl requires that the Fibre Channel network has hard zoning enabled.
Set Admin Pass – This feature is the use of a guest agent to change the administrative (root) password on an instance.
Get Guest Info – To get info about the guest machine of the hypervisor. This info can be retrieved within VM, An Hypervisor can handle several guest machines which are resource configurations assigned by the virtualisation environment.
Get Host Info – To get information about the node which is hosting the VMs.
Glance Integration – Glance is the image storage system used to store images of VM. This feature indicates that the hypervisor integrates glance storage capabilities.
Service Control – The hypervisore / compute is a collection of services that enable you to launch virtual machine instances. You can configure these services to run on separate nodes or the same node. Most services run on the controller node and the service that launches virtual machines runs on a dedicated compute node. This feature also allow to install and configure these services on the controller node.
VLAN Networking – It indicates that it is possible to pass VLAN traffic from a virtual machine out to the wider network.
Flat Networking – FlatNetworking uses ethernet adapters configured as bridges to allow network traffic to transit between all the various nodes. This setup can be done with a single adapter on the physical host, or multiple. This option does not require a switch that does VLAN tagging as VLAN networking does, and is a common development installation or proof of concept setup. When you choose Flat networking, Nova does not manage networking at all. Instead, IP addresses are injected into the instance via the file system (or passed in via a guest agent). Metadata forwarding must be configured manually on the gateway if it is required within your network.
Security Groups – This is a feature of the hypervisor (compute). There are similar features offered by cloud Networking Service using a mechanism that is more flexible and powerful than the security group capabilities built in. In this case the built in should be disabled and proxy all security group calls to the Networking API . If you do not, security policies will conflict by being simultaneously applied by both services.
Firewall Rules – Allows service providers to apply firewall rules at a level above security group rules.
Routing – It is the feature of the hypervisor to map internal addresses and external public addresses. The network part of the hypervisor essentially functions as an L2 switch and routing.
Config Drive – Auto configure disk – Automatically reconfigure the size of the partition to match the size of the flavor’s root drive before booting
Evacuate – As cloud administrator, while you are managing your cloud, you may get to the point where one of the cloud compute nodes fails. For example, due to hardware malfunction. At that point you may use server evacuation in order to make managed instances available again.
Volume swap – The hypervisor support the definition of a swap volume (disk) to be utilised as additional virtual memory.
Volume rate limiting – It is rate limiting (per day , hour ) for volume access, It is used to enable rate-limiting for all back-ends regardless of built-in feature set of back-ends.