Create a VM
To create a virtual machine (VM) do the following steps:
- Open the Virtual datacenters view by clicking on its icon in the top menu
- If there are no virtual appliances to hold groups of VMs, click Create a virtual appliance
Enter a Name and select a Virtual datacenter, and enter optional values and click Save
- Open a virtual appliance to hold a group of VMs by clicking on its name
- To create a VM, drag and drop a VM template from the Templates tab into the Virtual machines pane. You can also double-click the VM template
- If there is more than one version of the VM template, you can select another version
- If your cloud provider uses hardware profiles, select one
If required, select the Tier, which is the datastore service level, for your VM disk/s
Click here to show/hide the screenshot
The platform will create your VM. The status bar on the VM icon says it is NOT_ALLOCATED, which means that the VM has not been launched into the cloud.
Filter templates for creating VMs
The Template tab contains compatible templates only. If you cannot see an expected template, contact your system administrator. If there are a lot of templates, you may wish to filter the templates first.
To filter templates in the left-hand Templates tab:
- Click the filter button and select a Category from the pull-down list
- To display only ISOs, select the checkbox
- Enter text (including * wildcards) in the Search box and press Enter
To clear the search:
- Click the Clear link on the Category filter popup, which will clear both category and text search box
- Click the grey X button beside the Search box
Configure a VM before you deploy
To configure your VM before you launch it, do the following steps:
- On the VM icon, click on the options menu button, and from the options menu, select Edit
- Change the configuration options as described in this section
- Click Save
To configure the basic general VM settings, optionally set the following:
- Name, which is a friendly name for the VM. Power-on is in alphanumeric name order
- Guest setup in private cloud
- You can request a Guest initial password that will be sent by SMS or email
- Fully qualified domain name that the platform will set at deploy time
- Hardware profile and/or CPU, RAM and Cores per socket
To enable remote access to the VM:
- Select the Enable remote access check-box
- Display and optionally change the password for the remote access connection
Before you deploy:
For SSH access, check that your user account has an SSH public key. See Configure your user account. You will need the SSH private key to log in to your VM
In public cloud regions, assign:
a public IP to your VM. See VM Network
- a firewall policy to allow access to the appropriate SSH or RDP port. See VM Firewall
You can now continue with further configuration or Save and deploy your VM.
If you don't add any IP addresses, the platform will automatically add one on the default network.
To configure IP addresses on your VM, do these steps:
- Select the Private, External, or Public tab
- For private or external networks, select the network
- Create NICs as required:
- To use an existing IP address, drag and drop it into the NICs list
- To request an automatically created NIC and IP, drag and drop the Automatically generated IP tag into the NICs pane
- For private networks, to create a new IP address and NIC, click the + button
- For public networks, to obtain a new IP address, click the + button, select the network, and select the IP address
- Continue configuring your VM or click Save to finish
In private cloud, you can create additional hard disks that are not persistent. This means that when you undeploy the VM or remove the hard disk, the platform will delete your hard disks and destroy all data on them. To save the contents of a hard disk, create an instance template, which is a copy of the VM hard disk/s in the template library.
To add a hard disk:
At the top-right of the Storage tab, click the + add button
Select Assign virtual disk
In the dialog the options will depend on the platform configuration
You must enter the Size and the Controller type
- Advanced options: to force the creation of a new SCSI Controller, assign a new Bus value. The platform will return the bus value assigned by the provider
- Optionally select the Datastore tier with the appropriate storage service level
- Click Save
- You cannot change the size of the primary disk before you deploy a VM.
Select the Firewall policies to add. You can add as many firewall policies as necessary, up to the cloud provider's limit. If you can't see the expected policies, you may need to synchronize with your provider or wait for the platform to update provider data
Select the Load balancers to use for the VM.
To enable monitoring and metrics do these steps:
- Select the Fetch metrics checkbox, which will retrieve all metrics
- Select from the available options for your provider, for example, for AWS, you can select Basic or Advanced monitoring
- Select the metrics you would like to display for your VM
Obtain an estimate for the price of your VMs
To obtain a pricing estimate for deploying a complete virtual appliance now:
- Go to Virtual datacenters → Virtual appliances and open a virtual appliance
- Click the $ Estimate button. The Estimate button will have code for your currency or the default $ dollar symbol.
- The pricing message may also display when you deploy the virtual appliance.
- API users can also request a pricing message through the API.
The virtual appliance and VM pricing estimates only include the costs that are directly related to VMs. The virtual datacenters resources estimate includes other costs such as the VLAN cost, and the cost of datastore disks without a datastore tier, such as a cloud-init ISO. The VDC resources cost also includes public IP addresses because they are billed for the time of reservation, which may be longer than the time they are attached to a VM.
Screenshot: pricing estimate button
This screenshot shows an example pricing message.
Deploy to launch into the cloud
To launch your VMs, click Deploy virtual appliance
above the Virtual machines pane
on the right-hand side of the screen.
The platform will launch the VMs and power them on. The status bar below each VM icon will be coloured green. And the Deploy virtual appliance button changes to become the Undeploy virtual appliance button, which you can click to destroy the VMs.
Display VM details
To display VM details, select a VM icon. The platform will display the control panel below the VMs with details on different tabs, such as General
Click here to show/hide the screenshots
Here are some examples of VM control panel tabs
- The General tab contains the CPU and RAM and other information such as the remote access password for connecting to the VM.
- The NICs tab contains the details of the IP addresses of the VM.
- The Storage tab contains the details of the hard disks and volumes attached to the VM
Display VM metrics
To display metrics of a deployed VM with metrics enabled, click the Metrics
symbol on the VM icon
To refresh metrics data, click the circular arrows refresh button on the right-hand side of the panel. To toggle the display of metrics, click the selection list symbol on the left-hand side, and select the desired metrics.
To filter metrics, click the funnel symbol. Enter the Granularity, Statistics, Period, and/or Dimensions.
To configure the display of metrics at the virtual appliance level, do these steps.
- Select a Virtual appliance and go to Monitoring
- Optionally configure the refresh interval. To do this, select the Refresh data every checkbox and enter a number of minutes.
- Choose the metrics you wish to display and filter by metric statistics.
Click here to show/hide the screenshot
Screenshot: filtering metric statistics
VM power actions
The multicloud platform supports power actions to easily stop, start, pause, and reset VMs.
To stop a VM that is deployed and powered on:
- Select the VM icon
- Click the Power off button, which is a square button.
- Select from the following options:
Shut down: The platform will try to gracefully shut down the VM. This option may require hypervisor and guest VM configuration
Power off: The platform will perform a hard power off on the virtualization technology. Warning: Using this option may cause loss of data
Microsoft Azure (ARM)
- To deallocate a VM in ARM, select the Power off option
- To power off a VM in ARM, select the Shut down option
Screenshot: Shutdown and Power Off options
Remember that stopping a VM does not destroy it in the cloud provider and the VM is still consuming resources.
To power on a VM, click the Start button, which is an arrow in a circle.
Depending on the cloud provider, you may also be able to perform the following actions:
- pause a VM to suspend it using the double vertical bar button
- reset a VM to restart it using the circular arrows button.
The platform displays the appropriate buttons for the provider and the current state of the VM.
Click here to show/hide walkthrough screenshots
The following screenshots show two VMs: the VM on the left is selected to perform an action; the VM on the right shows how the result of the action will look.
Screenshot: Power on
Connect to a VM
The platform enables you to connect to a console of a VM for remote access.
Before you begin, configure the VM to allow remote access.
- User account: on the Advanced tab, add an SSH public key
- In the VM configuration, add a firewall to allow access to the appropriate ports, for example, RDP for Windows
- In AWS, add a private IP on a public subnet and a public IP
- In Azure, add a public IP
- To obtain the remote access password, select the VM and go to the VM control panel → General → click Show password
The VM must be deployed and powered on.
- It make take up to 15 minutes after deploy for the initial guest password to propagate to a VM, especially for Windows systems
- To obtain VM credentials check your email or SMS, or click the key button to display guest initial password or the default credentials button
To connect to your VM from the user interface:
- Select the VM and on the control panel, click the Eye icon
- In the Remote access dialog, enter the credentials, for example:
- For VNC to hypervisors: the Remote access password
- For SSH to Linux VMs: the SSH private key (in the Decryption password box)
- For RDP to Windows VMs: the VM user name and the password
- Then, if necessary, log in to the VM with the appropriate credentials
The remote access connection to the VM will open and you can log in and work with the VM.
- Remember to change your administrator password as soon as possible.
- On ESXi, you cannot change the remote access password using hot reconfigure. You must restart the VM for the password change to take effect
- If you cannot connect due to an unsecured certificate error, open a new tab in the same browser, enter the host IP of the VM, and accept the certificate.
Add more VMs to a deployed virtual appliance
When you add another VM to a deployed virtual appliance, the platform does not launch it directly into the cloud.
You can deploy new VMs individually or click the Deploy all VMs button in the top right-hand corner of the screen.
Change the configuration of a deployed VM
After you deploy a VM, the changes you can make will depend on your cloud provider. To change the configuration of a deployed VM do these steps:
- Select the VM
- If your provider or operating system does not support using hot add and hot reconfigure, power off the VM, using the Stop button on the control panel
- Mouse over the VM and from the options menu, select Edit.
- In the Edit VM dialog, go to General, and make changes as required to:
- Name, which is the VM friendly name
- CPU and RAM (if your VM is not using hardware profiles)
- Remote access
- If you disable remote access, hypervisor configuration will remain but you cannot access it through the Eye icon
- If you change the password, the change will be applied when you save the VM. Remember that it can be a maximum of 8 alphanumeric characters, i.e.. a to z, A to Z, 0 to 9. If you delete the password, the screen requesting the password will not appear. On ESXi hypervisors, if you set a password and later delete it, the password will be blank, not null. The screen requesting the password will appear, and you should press <Enter> to continue.
- Description of the VM
- Hardware profiles
- Make changes to Networks and Storage, Firewalls, and Load balancers as required
- Click Save
The changes will be applied in the cloud provider directly.
- To change a VM's Fully qualified domain name (FQDN), make the change in the VM's operating system and the platform will detect the new value
- For ESXi hypervisors, you cannot change the Remote access password using hot reconfigure
Do NOT change the Abiquo tag in public cloud
Do not change the Abiquo platform's tag on a VM in a public cloud provider (e.g. on an AWS instance) because you could break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo.
Save VM disks to create an instance template
An Abiquo instance is a new template that you create from VM disks.
- In Azure the Abiquo instance functionality has been disabled in Abiquo 4.7.0 pending further development.
To create an Abiquo instance, do these steps:
- Select and shut down each VM that you want to copy, then click Create instance
- Select a VM from the dialog
- Enter a Name that will enable you to identify the new template
- Optionally select the VM disks to save to a new template in the template library. If no disks are selected, the instance will copy all disks
- To create more instances, select Keep window open
- Click Create instance. The platform will lock the VM to create the instance
- If you kept the dialog open, click Back to list and create more instances as required, then close the dialog
The platform will store your new templates in the Apps library.
- In vCloud Director, when you create an instance template from a multi-disk VM, the template will be correctly created in vCloud with all of the disks. The platform will display only one disk with the sum of the sizes of all the disks. It will also display only one disk when you create a VM from the template. When you deploy the VM, the Broker will correctly detect the disks and display them on the VM details Storage panel.
- In Amazon, when you create a VM from an instance template, the platform will display one disk only, with the total size of all disks. After you deploy the VM, the platform will update the additional disks.
Use a saved template in private cloud
To use an instance template in a VM, double-click or drag and drop the original template and an instance menu will open. Select the instance template.
Click here to show/hide the screenshot
Display all VMs
To display all VMs of your enterprise, go to Virtual datacenters
→ All virtual datacenters
→ Virtual machines
To display all the VMs in a specific virtual datacenter, select the Virtual datacenter.
To select icon or grid view, click the icon symbol or the grid symbol in the top right hand corner.
To jump directly to the virtual appliance or virtual datacenter of the VM, go to Grid view and use the shortcut links by clicking on the Name fields.
To filter the VMs, in the Search box, enter text from the VM details with wildcards as required. See Search for VMs and filter the search
Move a VM to another virtual appliance
To move a VM to another VApp in the same virtual datacenter:
Select the VM
On the VM control panel, click the VM move button
Select the virtual appliance or create a new one, and click Accept
If you have the privilege to restrict VMs, you may also be able to move the VM to a restricted VApp in the same virtual datacenter.
Move a VM to a restricted virtual appliance
When you move a VM to a restricted virtual appliance, your administrator or platform provider will control the VM. Your provider may offer this as an option to Outsource a VM.
To move a VM to a restricted virtual appliance:
Click the VM move button on the VM control panel
Select the option to move the VM to a restricted VApp OR select a restricted VApp from the list, or create a new one
Click here to show/hide the screenshots
Move a deployed VM to another virtual datacenter
You can move a deployed VM to a virtual datacenter within the same Abiquo datacenter. The target VDC must have the same hypervisor type. If the VM is not deployed, the Move VM button will allow you to Move the VM to another virtual appliance
in the same virtual datacenter.
To move a deployed VM to another VDC:
- If your VM does not support hot-reconfigure, shut down the VM. This is because moving a VM will change the configuration of the VM, for example, the NICs
- Select the VM and click the Move VM button
- For a deployed VM, the platform will display a list of compatible virtual datacenters (with the same hypervisor technology and network device) and virtual appliances.
- After you select the virtual appliance, the platform will display the configuration dialog.
- You must select at least one network address. It is possible to select the same external IP address that was already attached to the VM.
- Optionally select firewalls and load balancers
- The platform may display a pricing estimate dialog for you to accept the new VM price.
The platform will move the VM to the new virtual datacenter. If the move is not successful, the VM will be restored to the original virtual datacenter.
This feature does not move VMs with the following configuration:
- External storage volumes
- NAT rules
- Scaling groups
- Anti-affinity layers.
- The platform will attempt to remove the VM from its layer and if it cannot do so, then the move will fail. For more details of layer constraints, see Configure VM High Availability. The platform will not add the VM to a layer in the target VDC.
Delete a VM
To delete a VM, move the mouse over the VM and from the VM options menu, select Delete.
If the virtual appliance or VM is deployed, you do not need to undeploy it. You can directly delete a VM that is deployed.