...
...
...
...
...
...
| Table of Contents | ||
|---|---|---|
|
This tutorial describes how to capture a remote VM that is connected to a network not managed by Abiquo.
1. Prepare Abiquo to capture virtual machines
To prepare to capture a remote VM, first of all you need a physical machine from which you will capture the VM:
Create the datacenter and rack, then add the physical machine
Select Retrieve virtual machines.
Screenshot: The platform marks the retrieved (or imported) VMs with the
...
symbol.
...
Create the networks that the captured VM will be in.
For example, in the datacenter, create public or external networks with the same specifications as the VM networks.
This means the same VLAN tag, network address, available IPs.
...
Create the IPs for your VMs in
...
Abiquo
Create a virtual datacenter in the datacenter for your VM.
If you created a public network, you need to purchase public IPs for your virtual datacenter from the Network / Public tab.
...
You will also need a virtual appliance. You can create it now or wait to do it as part of the capture process.
Import the VMs from the physical machine. To do this, go to the datacenter, select the physical machine and click
...
the
...
Retrieve VMs from
...
managed datastores
...
button.
...
The platform will now display the VMs running on the hypervisor that are not managed by Abiquo.
2. Capture the remote VM via GUI
Now you will capture the VM so that the platform can manage it.
Select the VM you want to capture and click the
...
Capture VM
...
button.
The GUI will then ask you for the virtual appliance to store the VM. Select your virtual appliance in the virtual datacenter with the network addresses purchased. If you didn't create a virtual appliance earlier, you can do so now by clicking the + add button.
...
Check the General Information, on the Network tab, select the appropriate NICs and IP address, and check the Disks.
VM General information
VM NetworkAccept the capture and the remote VM will be added to the virtual appliance and managed by Abiquo.
You can check the VM configuration on the details panel or when you edit the VM.
The platform will now display the Release VM button instead of the Capture VM button. The Release VM button is a box with an arrow pointing outwards.
...
3. Capture a VM using the API
You can capture a VM using the API and once you get started, it's not such a daunting task as it might first seem! A good working knowledge of the Abiquo API is required, but as always, if you get stuck, you can always open your browser console and take a look at how the Abiquo UI does it!
Note that the Abiquo UI enables you to create a virtual appliance or a network address as part of the capture process but these steps are not included in this tutorial.
First be sure to do the preparatory steps and obtain the information about the VM and the environment that you will require to create the VM object.
Before you begin:
In Abiquo, determine the ID of:
The enterprise the VM will be captured for
The datacenter where it will be captured
The physical machine (hypervisor) where it will be captured from
In the hypervisor:
Check the VM name
Check the network details including the VLAN tag
In the virtual machine
Check the IP addresses of the NICs
In Abiquo, create the following and make a note of the IDs:
The virtual datacenter that the VM will be captured into
The networks that the VM will belong to
The IP addresses for the VM in the networks
The virtual appliance that the VM will be captured into
To capture a VM using the API
Retrieve the virtual appliance the VM will be captured into
The POST to capture the VM is made to the virtual machines URL of the virtual appliance.
It's not really necessary to get the whole virtual appliance, but by doing so, you can validate the link and check that you have the right virtual appliance!
Retrieve the virtual machine with resources from the hypervisor in Abiquo
You will modify this virtualmachineflat object to create the request payload for the POST request
Retrieve network interfaces for configuration
You will need the network link and the IP address, to include them in the virtualmachineflat object
Optionally retrieve a costcode object to add to the VM
Modify the virtualmachineflat object
Post the virtualmachineflat object to the virtual machines URL of the virtual appliance
3.1.
Retrieve virtual appliance
Using the virtual datacenter ID, retrieve all virtual appliances. See https://wiki.abiquo.com/api/latest/VirtualAppliancesResource.html#list-virtual-appliances
...
| Code Block |
|---|
curl --verbose -k -u admin:xabiquo -X GET "https://mjsabiquo.bcn.abiquo.com/api/cloud/virtualdatacenters/3/virtualappliances" -H "accept:application/vnd.abiquo.virtualappliances+json;version=4.7" | jq '.' |
| Expand | ||
|---|---|---|
| ||
|
3.2. Retrieve virtual machine from the hypervisor
Retrieve all the VMs from the hypervisor, using sync=true. Identify the required VM. Obtain a flat representation of the VM that includes the disks and network interface details (MAC address and sequence number).
| Code Block |
|---|
curl --verbose -k -u admin:xabiquo -X GET "https://mjsabiquo.bcn.abiquo.com/api/admin/datacenters/2/racks/2/machines/3/virtualmachines/174?sync=true" -H "accept:application/vnd.abiquo.virtualmachineflat+json;version=4.7" | jq '.' |
| Expand | ||
|---|---|---|
| ||
|
3.3. Retrieve network details and IP addresses
Retrieve IPs from the external network that are available in the datacenter and then retrieve the appropriate IP for the VM.
| Code Block |
|---|
curl --verbose -k -u admin:xabiquo -X GET "https://mjsabiquo.bcn.abiquo.com:443/api/admin/enterprises/1/limits/2/externalnetworks/7/ips/16" -H "accept:application/vnd.abiquo.externalip+json;version=4.7" | jq '.' |
| Expand | ||
|---|---|---|
|
Retrieve IPs from the public network that have been purchased and are available to the virtual datacenter. Select and retrieve the appropriate public IP. To start with, first we used the "has" parameter to identify the required IP address.
...
| Code Block |
|---|
curl --verbose -k -u admin:xabiquo -X GET "https://mjsabiquo.bcn.abiquo.com:443/api/cloud/virtualdatacenters/3/publicips/purchased/30" -H "accept:application/vnd.abiquo.publicip+json;version=4.7" | jq '.' |
| Expand | ||
|---|---|---|
|
3.4. Create virtualmachineflat data transfer object
Change the virtual machine links as follows.
...
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
For example, from the public IP address, obtain the link with a "rel" value of "publicnetwork".
Change the "rel" value to "vlan".
For this network, also note the IP value
And for example, for the external IP address, obtain the link with a "rel" value of "externalnetwork".
Again, change the value of the "rel" attribute to "vlan".
And note the value of the IP
Add the links to the nics / collection / links section for each NIC and the IP to the main section of each NIC after the tag value (don't forget the comma). |
...
| Expand | ||
|---|---|---|
|
3.5. Optionally retrieve a cost code to add to the VM
You can optionally add a cost code to the VM as part of the capture process. You can use the "has" parameter to search for the cost code name, then retrieve the required cost code by ID.
...
The platform will account the VM by its template cost code.
3.6. Capture the virtual machine
To capture the machine, send the virtualmachineflat data transfer object as part of a post request to the virtual machines URL of the virtual appliance that will hold the captured virtual machine.
...
| Expand | ||
|---|---|---|
|