Mapping cloud constructs to BMC ProactiveNet classes


Warning

Note

By default, a ResourcePool CI is created whenever cloud consuming is initialized although there is no construct by that name in BMC Cloud Lifecycle Management.

Constructs to classes mapping

The following table shows mapping of BMC Cloud Lifecycle Management constructs to BMC ProactiveNet classes and unique attributes for each class.

BMC Cloud Lifecycle Management construct

BMC ProactiveNet class

Unique class attributes

POD

BMC_ConcreteCollection

CollectionType = Pod

Static Pool

BMC_ResourcePool

Type = Compute
SubType = Fully qualified class name of the Pooled Object

NetworkContainer

BMC_ConcreteCollection

CollectionType = NetworkContainer

Service Offering Instance

BMC_ServiceOfferingInstance

 

Service Offering

BMC_ServiceOffering

 

Virtual Guest

BMC_ComputerSystem

isVirtual = 1 (Yes)
VirtualSystemType = 3 (VM or VM Guest)

Physical Server

BMC_ComputerSystem

 

Virtual Host

BMC_ComputerSystem

VirtualSystemType = 0 (other system type)

Zone

BMC_ConcreteCollection

CollectionType = Zone

Organization

BMC_Organization

isTenant = Yes

Virtual Cluster

BMC_Cluster

 

Virtual Data Store

BMC_ConcreteCollection

CollectionType = VirtualDatastore

Location

BMC_PhysicalLocation

 

Virtual Resource Pool

BMC_ConcreteCollection

CollectionType = VirtualResourcePool

Common attributes mapping

The following table shows attributes mapping for attributes shared by all classes.

BMC Cloud Lifecycle Management
attribute Name

BMC Cloud Lifecycle Management
attribute retriever

BMC ProactiveNet attribute

reconciliationID

getReconciliationID

mc_udid

tokenId

TokenId

TokenId

name

getName

Name

Component Aliases mapping

The following table shows how component aliases are fromed in BMC ProactiveNet. All other constructs get reconciliation Id.

BMC Cloud Lifecycle Management construct

BMC ProactiveNet alias

POD

BMC_ConcreteCollection: <TokenId>

VirtualCluster

<TokenId> ( Token id is formed as :BMC_CLUSTER:Fully qualified domain name : <morID>)

NetworkContainer

BMC_ConcreteCollection: <TokenId>

Zone

BMC_ConcreteCollection: <TokenId>

VirtualGuest

BMC_ComputerSystem: <TokenID>

VirtualHost

<TokenId> ( Token id is formed as :BMC_ComputerSystem:<hostname> : <domain>)

VirtualDataStore

<TokenId>

VirtualResourcePool

<TokenId>

Relationships mapping

The following table shows how BMC Cloud Lifecycle Management relationships are mapped to BMC ProactiveNet.

Source

Target

Relationship

VirtualGuest

Zone

Name = VMINZONE

VirtualGuest

NetworkContainer

Name = VmInContainer

Zone

NetworkContainer

Name = ZoneInContainer

VirtualGuest

ServiceOfferingInstance

Name = CSForSOI

ServiceOfferingInstance

Organization

Name = ProvisionedForCustomer

ServiceOfferingInstance

ServiceOffering

Name = ServiceOfferingDeliveredBy

NetworkContainer

Organization

Name = ContainerAssignedToOrganization

NetworkContainer

Pod

Name = ContainerInPod

VirtualDatastore

StaticPool

Name = MemberOfPool

VirtualResourcePool

StaticPool

Name = MemberOfPool

VirtualCluster

StaticPool

Name = MemberOfPool

VirtualHost

StaticPool

Name = MemberOfPool

PhysicalServer

StaticPool

Name = MemberOfPool

Pod

Location

Name = PodAtLoation

StaticPool

Pod

Name = PoolInPod

VirtualGuest

VirtualHost

Name = VMInHost

VirtualHost

VirtualCluster

Name = HostInCluster

StaticPool

NetworkContainer

Name = PoolInNetworkContainer

ServiceOfferingInstance

NetworkContainer

Name = SOIToNC

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6