| Table of Contents |
|---|
Introduction
When you add vCenter hosts to Abiquo, Abiquo supports vMotion with the capabilities functionality and limitations described belowhere.
| Info | ||
|---|---|---|
| ||
Abiquo supports vMotion between different versions of ESX. For example, from an ESX 4.x to ESX 5 host, or from an ESX 5 to ESX 4.x host. |
| Note | ||
|---|---|---|
| ||
If the machines are not connected to a dvSwitch, you must have the same Network Service Type for both Source and Destination machine network interfaces or you will not be able to use the moved VMs in Abiquo. See Manage Network Service Types |
...
When you add vCenter Clusters as hosts to Abiquo, all VMs in the cluster are effectively on a single host in Abiquo, which means that vMotion is transparent to Abiquo and there are no limitations. See Add VMware vCenter clusters as servers |
vMotion functionality supported by Abiquo for vCenter hosts:
- The events are detected properly independently of the polling interval, which only affects the state change detection velocity.
- False DESTROYED/CREATED events are detected (and not propagated) using VCenter vCenter to check if the virtual machine VM has vMotion or Relocation tasks in progress.
- Abiquo detects vMotion movements (virtual machines VMs in power on)
- Abiquo detects Relocation movements (virtual machines VMs in power off)
- In early tests, Abiquo detects movements produced by VMWare VMware DRS because (and it properly manages the repeated names of virtual machines in the caches.
- Abiquo supports vMotion between different versions of ESXi
Limitations of vMotion in Abiquo
- MOVED events are not propagated when the virtual machine VM is moved to a host in vCenter that is not managed by Abiquo (it is not added to Abiquo and not monitored by the Monitor Manager/Virtual System Monitor) but it is managed by vCenter. The virtual machine . The VM will remain with the last known state. Then:
- if If the destination host is added to Abiquo, a MOVED event will be generated properly.
- if If the virtual machine VM goes back to the original host, its state will be updated.
- VMWare HA is not supported.
- Abiquo does not support Abiquo supports movements between machines with different Network Service Types unless Types if the machines are connected to a dvSwitch. You must configure the same network service type for source and destination machine network interfaces or you will not be able to use the moved VM in Abiquo.
- dvSwitch : Abiquo will only allow you to change the Network Service Type of a dvSwitch if there are no virtual machines VMs deployed on any of the machines hosts attached to that dvSwitch.
- Abiquo supports Storage vMotion to the same ESX host is supported since version 3.0ESXi host
- When you are performing a vMotion operation, vCenter asks if you want to migrate the datastore on which the VM is located. If you vMotion a VM to the same host and you just change the destination datastore, this will work in vCenter and Abiquo will detect it when it synchronizes the virtual machine VM definition. You can set the frequency of this check with the abiquo.vsm.vmsyncfrequency.vmx_04 property. See Abiquo Configuration Properties#vsm
vMotion
...
The following vMotion configuration requirements are requires the following configuration as explained below:
- Abiquo properties
- Shared datastore on VMWareVMware
- Shared datastore enabled in Abiquo
Configuring Abiquo Properties for vMotion
In order to detect movements, the Monitor Manager requires the following Abiquo Configuration Properties for DvS and vCenter. Set these properties in the abiquo.properties file on the Remote Services machine.
- abiquo.dvs.vcenter.user
- abiquo.dvs.vcenter.password
- abiquo.vcenter.port.connection
...
- the platform
Configure iSCSI Shared Storage
On the storage device, check you have properly configured the initiator group to include each ESX/ESXi, by adding the hypervisors' IQNs to the list.
Also remember to add the Abiquo IQN, which can be found at /etc/iscsi/initiatorname.iscsi
NetApp
For example, for NetApp, open the Filer WebUI at http://<Filer_IP>/na_admin/ then click the FilerView button.
Make changes under LUNs > Initiator Groups > Manage. In this case, the hypervisor and Abiquo IQNs should be part of abiGroup.
If you have previously used the NetApp storage with an ESX/ESXi host outside of Abiquo, the ESX/ESXi host's IQN will probably may have been added to another initiator group. You will need to manually remove it from that group before you can use it in Abiquo. You can add it to abiGroup the appropriate group manually or Abiquo will add it automatically.
Configuring the Hypervisor to Use a Shared VMFS Datastore
...
Configure a shared VMFS datastore
To get vMotion® working with Abiquo you need to ensure that all the hypervisor hosts have a shared VMFS datastore.To do this, first create
- Create a volume (that will be shared by all your ESX hypervisors) in your preferred storage system
...
- Add it to an
...
- ESXi hypervisor using the static discovery method.
...
- From the iSCSI Software Adapter properties window
...
- , go to Static Discovery
...
- . Then click the Add button
...
- .
- Complete the dialog
...
- with the server hostname or IP and the target IQN. The port should be the default, which is 3260.
- Click OK and close the properties windows.
...
- If a message suggesting you rescan all the HBAs appears
...
- , click Yes.
...
- After the rescan you should see your volume(s) in the list of devices.
...
- Format the volume with the VMFS file system.
...
- Add the volume as a datastore
...
- . Go to Configuration --> Storage
...
- , then follow the instructions,
...
- and select the
...
- recently created
...
- volume.
- On the other hypervisors
...
- , add the volume with the static discovery and it will be automatically recognized as a new datastore.
...
When adding the your hypervisors to Abiquo make sure , check that the newly created shared datastore is visible, and activatedenable it.