Prerequisites for creating the Infrastructure Management cloud integrator
Before creating the Infrastructure Management cloud integrator, ensure that you perform the tasks listed below:
- Identify the different cloud constructs that you want to create in Infrastructure Management
- Create the topology and relationships on paper
- Finalize the configuration items (CIs) and the relationships for the cloud construct topology
- Identify routing information from the cloud construct
- Identify the top level node of your construct
To help explain these tasks, consider the example of VMware vCloud Director.
Identifying the different cloud constructs
Integrating Infrastructure Management with VMware vCloud Director displays the following constructs in the operator console:
- Provider vDC (PVDC)
- Organization vDC (OVDC)
- Virtual machines (VM)
- vApps (VAPP)
Creating the topology and relationships on paper
The following is pictorial representation of what the VMware vCloud Director topology must look like:
In this image, ESX represents a physical construct. The other constructs are logical constructs.
Finalizing CIs and their relationships
Assign a CI to a cloud construct and identify which properties of the cloud construct you want to populate in the CI attribute. Also, identify a token ID for the CI. A token ID is a unique identifier that can distinctly identify a CI or a cloud construct.
For example, for the Provider vDC, assign the BMC_ConcreteCollection class. The token ID for the Provider vDC can be its unique VMware vCloud reference ID. The name of the Provider vDC can be the name of the CI attribute.
The following table represents the mapping between the VMware vCloud Director constructs in Infrastructure Management and their special attributes and relationships.
VMware vCloud construct | Represented in Infrastructure Management as | Special attribute |
|---|---|---|
Provider vDC | BMC_ConcreteCollection | CollectionType=ProviderVDC |
Organization vDC | BMC_ConcreteCollection | CollectionType=OrganizationVDC |
vApps | BMC_ConcreteCollection | CollectionType=VApp |
Virtual machine | BMC_ComputerSystem | isVirtual=1, VirtualSystemType=0, PrimaryCapability=14 |
The following table represents the relationships among the constructs:
Source | Destination | Relationship class | Relationship name |
|---|---|---|---|
Organization vDC | Provider vDC | BMC_MemberOfCollection | OvdcInPvdc |
vApps | Organization vDC | BMC_Dependency | VappInOvdc |
Virtual machine | vApps | BMC_Component | VmInVapp |
Identifying routing information from the cloud construct
Routing information is brought into Infrastructure Management by external agents. You must identify if any construct in the topology is brought in by external agents such as BMC PATROL or an ESX host machine, or a physical server and find the relationship between the agent and the construct in the topology. You can then use this construct to route information.
Identifying the top level node
The top level node is the top most node in the topology. The top node is the node from which the entire topology can be traced. The top level node is usually the root node and it does not have a logical parent.