After your RPC-VMware environment is configured for Guest OS Services, an automated system that has been registered with the vCenter Server will receive vCenter event notifications when certain VM actions are performed by you.
VM event types#
VM creation notifications are used to determine when new Virtual Machines are created in RPC-VMware in order to make them available for GOSS enrollment. When a create notification is received, the automation system interrogates vCenter for VM container details that allows a CMDB entry for the VM to be created. Also, the automation system adds a custom attribute to the VM contain that contains the CMDB device number associated with that VM.
VM creation events might be triggered by creating a new VM container, deploying a new VM from a template, deploying a new VM from OVA/OVF, adding a VM to inventory from the local datastore, migrating a VM into RPC-VMware, restoring a VM from a backup or certain 3rd party tool functions that result in the enrolled VM being added to the RPC-VMware vCenter inventory.
It is important that you never remove or modify the custom attribute of the VMs in RPC-VMware.
VM deletion events are used to determine when a VM that has been enrolled in GOSS has been deleted. When a deletion event is received, the automation system will set the CMDB entry associated with the VM to "Computer no longer active". This will remove the VM from your "Online" device list in the MyRackspace Portal. The Automation system will also remove all entries from associated service enrollment management systems so that Monitoring, Patching and Antivirus systems no longer expect the VM to be available.
VM deletion events might be triggered by deleting the VM, de-registering the VM from vCenter inventory, migrating the VM out of the RPC-VMware environment, restoring the VM in place from a backup, failing the VM to another RPC-VMware environment in another data center using VMware Site Recovery Manager or certain 3rd party tool functions that result in the enrolled VM being removed from the RPC-VMware vCenter inventory.
Cloning a VM triggers a VM creation event as described above. When a VM enrolled in GOSS is cloned, the internal OS changes that were made during enrollment are no longer correctly associated with the new CMDB entry. The cloned VM will still contain internal OS assiciations with the source VM CMDB entry. When you clone a VM enrolled in GOSS it will be necessary for you to contact your support team to have the CMDB association corrected in the new VM. You might need to reboot the new VM after corrective actions have been taken.
VM IP changes#
Changing the local IP of a VM that has been enrolled in GOSS will disrupt the configured services and associated automated processes as well as the ability of Rackspace Support to quickly access the OS of your enrolled VMs.
If you need to change the local IP of an enrolled VM, contact your Support team to coordinate activities necessary to update the Rackspace CMDB entries and associated hosted firewall NATs.