This page gives a brief introduction to how to manage virtual machines and the virtual machine lifecycle in Abiquo. However, you should also read the other sections on virtual machine and virtual appliance configuration.
To create a new virtual machine in the platform, from the Templates tab, select a template just double-click or drag and drop to the Virtual machines pane.
It is that easy to create virtual machines in Abiquo!
If you are working in a public cloud region, select a hardware profile for your virtual machine.
In AWS, the smallest hardware profile for use with a free starter account is t1.micro.
Abiquo will display the CPU and RAM for your selected profile.
If there are other copies (instances) of the virtual machine template you are adding to your virtual appliance, the following pop-up is shown so you can select an instance or the master template. Note that by default the master template is selected but you can deselect it.
The new virtual machine you created it is not deployed, which means it is not allocated to a cloud node and it is not consuming compute resources.
You can now configure the virtual machine to change the compute resources and add network and storage resources, as well as other configuration. Please note that your cloud provider may charge you for network and storage resources, even if you are not using compute resources.
Of course, you can create a group of related virtual machines in the same virtual appliance, just add more templates!
To launch a single virtual machine to a virtualization technology or Docker host:
The platform will check your access and schedule or allocate your virtual machine to a hypervisor, public cloud region or Docker. Then the platform will configure it in the virtualization technology, then power it on.
Sometimes you will have a virtual machine that is deployed, while another is not deployed. For example, when you add new virtual machine or deploy only one virtual machine out of a group. This means that the virtual appliance is deployed but not synchronized with the hypervisor, public cloud or Docker. So the green Deploy virtual appliance button changes to become the blue Sync virtual appliance button.
To deploy the virtual machine(s) that are not allocated, click the blue Sync virtual appliance button.
When a group of virtual machines are all deployed, you will see the red Undeploy buttons for a selected virtual machine and a virtual appliance.
To stop a virtual machine and remove it from the platform, destroying all data on non-persistent volumes, select the virtual machine and click the Undeploy VM button.
When you undeploy a virtual machine, then the virtual machine will be DESTROYED on the hypervisor and all changes and DATA on non-persistent disks will be lost.
When you undeploy a virtual machine, it will return to the not allocated state.
Of course, you can also undeploy a virtual appliance, which will undeploy the whole group of virtual machines at the same time.
If your virtual machine did not deploy properly, for example, because you did not have enough resources in your Enterprise, then you may see an error symbol on the virtual machine icon.
To view recent events, move the mouse over the virtual machine and then click the error symbol.
To see the full text of a field, move the mouse over it.
To view an event trace, select the event in the list. The trace will display below the list.
To remove the warning symbol, after checking the Event messages, click Yes.
If you have the privilege to Manage Users, you can delete warnings for the users of the enterprises that you manage.
If you select a virtual machine, the platform will display a control panel below the virtual machines panel. Here you can check the details of the virtual machine.
The General tab contains the CPU and RAM and other information such as the remote access address for connecting via VNC or RDP.
The Network tab contains the details of the IP addresses of the virtual machine.
The Storage tab contains the details of the hard disks and volumes attached to the virtual machine.
To display the virtual machine configuration, on the virtual machine icon, click the pencil edit button.
The virtual machine configuration popup will open.
If you are working with ESXi and your virtual machine template and operating system support hot add and hot reconfigure, you can change the configuration in this dialog, without powering off the virtual machine.
The following screenshots show two virtual machines: the virtual machine on the left is selected to perform an operation. The virtual machine on the right shows the result of the operation.
To power on a deployed virtual machine that is OFF or PAUSED, click the power on button. After power on, the virtual machine is running in the cloud node and its icon displays a green bar with the ON state.
To pause a virtual machine that is ON, click the pause button. The platform will suspend the virtual machine, which will still exist in the cloud node. The virtual machine icon will display a yellow bar with the paused state.
To reset a virtual machine, click the reset button. The platform will reboot the virtual machine.
To stop a virtual machine, click the power off button. A pull-down menu will open. Select from two options: graceful shutdown and hard power off.
Undeployed vs Powered Off Virtual Machines
If a virtual machine is powered off, this does not mean that the virtual machines is undeployed.
A powered off virtual machine is still consuming resources because the virtual machine still exists in the cloud node.
Before you connect to your virtual machine, edit your VM to obtain the connection details. Click the pencil edit button on the VM icon.
On the Edit virtual machine dialog on the General information tab, check that remote access is enabled. Select the checkbox to Show password and copy the remote access password (for VNC and RDP access). If they are available, you can also copy the SSH user and password.
Now close the VM configuration popup.
To connect to your virtual machine, click the remote access eye icon.
A noVNC dialog may open, similar to the one shown below. In the Password field, enter the remote access password.
The remote access connection to the virtual machine will open and you can work with the virtual machine.
If remote access is not supported, the platform may display a popup window with connection details.
You may then use an appropriate remote access client to connect to the virtual machine.
The user will not be able select the virtual machine to view the details or perform platform operations on this virtual machine. The platform will display a small padlock symbol in the top left-hand corner of the virtual machine icon.
Move the mouse over the virtual machine and click the pencil edit button.
In the virtual machine configuration dialog, make your changes following the instructions in the section on how to Configure Virtual Machines.
If the virtual machine is deployed, the changes will be applied in the hypervisor directly. Otherwise, the final configuration will be created when you deploy.
Virtual machine templates can be persistent or non-persistent, depending on the system disk type.
To save a new template disk from virtual machine disks, select the virtual machine, power it off and click Create instance.
Select the virtual machine.
Then select the virtual machine disks to save to a new template in the template library. Click Create instance.
To use an instance template in a virtual machine, double-click or drag and drop the original template and an instance menu will open. Select the instance template.
You can select a template and save it to a volume as a persistent virtual machine. The persistent virtual machine will deploy using the volume and the changes you make to the virtual machine will be saved on the volume.
To create a persistent virtual machine, open the Persistent VM template tab and click the + button.
Select the master or instance template that you would like to save to the persistent volume.
Then select the disks and click Start conversion.
Persistent VMs are available on the Persistent VM tab of the virtual appliance templates panel.
You can create a single virtual machine from the persistent VM and deploy it in the usual way. A virtual machine with a persistent system disk has a disk symbol on the virtual machine icon.
When you undeploy the persistent virtual machine, the volume will remain intact and the persistent virtual machine will return to the Persistent VM tab.
The following screenshots are based on a virtual appliance with two virtual machines, which has already been deployed. One of the virtual machines is running and one is powered off.
First delete the powered-off machine.
After you confirm the delete, the icon for the deleted virtual machine is removed from the virtual appliance.
If the virtual appliance is deployed and the virtual machine is running, you do not need to undeploy - the deployed virtual machine can also be deleted directly.
Success status code: 200
To manage the virtual machine using the API, first you need to retrieve the virtual machine and find the links for different actions. Remember to see VirtualMachineResource for full details of virtual machine operations using the Abiquo API.
Send a PUT request to the virtual machine state link
The virtual machine state link is a link in the virtual machine object with the "rel" attribute set to state. The "title" attribute contains the current state. You can send a PUT request of a virtualmachine state object to the link (in the "href" attribute) to change the state of the virtual machine.
Hard power off
To hard power off a VM using the API, perform a request like the one shown below.
The API will return a link where you can monitor the progress of this operation.
To perform a graceful shutdown, your virtual machine will need to have guest extensions installed on it. After an operation completes, you can view the status of the task by performing a get request on the accepted request link. In this case, the graceful shutdown was not supported and failed.
To reset a virtual machine using the API, use a POST request to the reset action link.
API example removed: POST_cld_vdcs_X_vapps_X_vms_X_act_reset_AC_acrq_j
You can download the API examples archive from ABI38Confluence-space-export-152334-314.html.zip