This topic contains a scenario in which a virtual machine (VM) migrates to another VMware ESX server in a VMware VirtualCenter environment.
This unplanned migration of a VM is captured, and a change request is logged so that the migration is documented and available for reference for any subsequent problems.
The unplanned migration of a VM to a new server triggers a BMC Atrium Discovery and Dependency Mapping (BMC Atrium Discovery) scan and synchronization to BMC Atrium CMDB so that the IT infrastructure data will be accurate in the CMDB.
Prerequisites
- Change templates have been created in BMC Change Management to be created automatically by BMC Atrium Orchestrator when it detects a VM image migration.
- A BMC Atrium Discovery job is defined to discover VirtualCenter.
- BMC Atrium Orchestrator is configured to trigger a VirtualCenter discovery scan in BMC Atrium Discovery.
- BMC Atrium Discovery is configured to continuously synchronize to the CMDB.
- BMC Atrium CMDB Reconciliation Manager is configured to run a BMC Atrium Discovery reconciliation job.
Technical use case
- A virtual system undergoes an unplanned change. Here, it migrates to another ESX server (an unplanned VMware VMotion event).
- BMC Atrium Orchestrator creates a change request based on the change template for an unplanned change of the VM.
- The change is automatically approved.
- BMC Atrium Orchestrator detects the VMotion event and triggers BMC Atrium Discovery to immediately run the VirtualCenter discovery task. BMC Atrium Discovery synchronizes changes to the relationship to indicate that the VM image runs on a new ESX server, so data in BMC Atrium CMDB is up to date. Continuous reconciliation in the BMC Atrium CMDB Reconciliation Engine merges the change to the production dataset.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
1 Comment
Kelly Holcomb