CDM Mapping for Cloud
This topic provides information about mapping for cloud nodes. The CIs created are described in this topic.
Data models
CMDB version differences
The default mapping works with CMDB versions 7.5, 7.6, and 7.6.03 and later. The data model in each is slightly different.
BMC_Impact
relationships are not normally created with CMDB 7.6.03 and later, since the CMDB automatically maintains them itself. See the information about impact relationships for more details.
BMC_CloudInstance (Provider)
The CloudProvider node is mapped to a BMC_CloudInstance CI with the following attributes:
Attribute | Details |
---|---|
Name | Cloud provider |
ShortDescription | Cloud provider |
Description | Cloud provider |
ManufacturerName | Cloud provider |
Model | Cloud provider |
TokenId | Cloud provider key |
Company | Cloud provider |
Category | " |
Type | " |
Item | " |
BMC_CloudInstance relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
Impacted |
|
BMC_CloudInstance (Region)
The CloudRegion node is also mapped to a BMC_CloudInstance CI. It has the following attributes:
Attribute | Details |
---|---|
Name | Cloud region |
ShortDescription | Cloud region |
Description | Cloud region |
ManufacturerName | Cloud provider |
Model | Cloud region code |
TokenId | Cloud region key |
Company | Cloud region |
Category | " |
Type | " |
Item | " |
BMC_CloudInstance relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
Impacted |
BMC_CloudInstance (Service)
The CloudService node is also mapped to a BMC_CloudInstance CI. It has the following attributes:
Attribute | Details |
---|---|
Name | Cloud service |
ShortDescription | Cloud service |
Description | Cloud service |
ConsumedService | Cloud service type |
Model | Cloud service code |
TokenId | Cloud service key |
Category | " |
Type | " |
Item | Cloud service |
BMC_LogicalSystemComponent
The cloud LoadBalancerService is mapped to BMC_LogicalSystemComponent. It has the following attributes:
Attribute | Details |
---|---|
TokenId | TokenId is of the form "ADDM:%lb_service.key%" . |
Name | Load balancer service |
ShortDescription | Load balancer service |
Description | Load balancer service |
isCloud |
|
Company | Cloud service Company |
Category |
|
Type |
|
Item |
|
BMC_LogicalSystemComponent relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_ResourcePool
The cloud LoadBalancerPool is mapped to BMC_ResourcePool. It has the following attributes:
Attribute | Details |
---|---|
TokenId | TokenId is of the form "ADDM:%lb_pool.key%" . |
Name | Load balancer pool |
ShortDescription | Load balancer pool short.name |
Description | Load balancer pool |
ResourceType | Other (0) |
Company | Cloud service Company |
Category |
|
Type |
|
Item |
|
BMC_ResourcePool relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Component | HOSTEDRESOURCEPOOL | BMC_CloudInstance (Service) | BMC_ResourcePool |
|
|
|
|
BMC_AdminDomain (AdminCollection)
The cloud AdminCollection node is mapped to BMC_AdminDomain. It has the following attributes:
Attribute | Details |
---|---|
Name | Administrative collection |
ShortDescription | Administrative collection |
Description | Administrative collection |
Model | Administrative collection type |
TokenId | Administrative collection
|
Company | Cloud service Company |
Category |
|
Type |
|
Item | Administrative collection |
BMC_AdminDomain (AdminCollection) relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | CLOUDADMINCOLLECTION | BMC_CloudInstance (Service) | BMC_AdminDomain |
|
|
|
|
BMC_AdminDomain (CloudManagementGroup)
The cloud CloudManagementGroup node is mapped to BMC_AdminDomain. This mapping was updated in the November 2020 TKU. It has the following attributes:
Attribute | Details |
---|---|
Name | Management Group name |
ShortDescription | Management Group short_name or name |
Description | Management Group name |
ConsumedService | Management Group type |
isCloud |
|
LastScanDate | Cloud service last_update_success |
Model | Management Group type |
SerialNumber | Management Group id |
TokenId | Management Group |
Company | Cloud service Company |
Category | "Cloud" |
Type | "Cloud Management Group" |
Item | Management Group type |
BMC_AdminDomain (CloudManagementGroup) relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_MemberOfCollection | CLOUDMANAGEMENTGROUPPROVIDER | BMC_CloudRegion | BMC_CloudManagementGroup |
|
|
|
|
BMC_MemberOfCollection | CLOUDMANAGEMENTGROUPOWNEDACCOUNT | BMC_CloudManagementGroup | BMC_ CloudManagementGroup (owned) |
BMC_ConcreteCollection
The cloud Deployment node is mapped to BMC_ConcreteCollection. It has the following attributes:
Attribute | Details |
---|---|
Name | Deployment |
ShortDescription | Deployment |
Description | Deployment |
Model | Deployment type |
TokenId | Deployment
|
Company | Cloud service Company |
Category |
|
Type |
|
Item | Deployment |
BMC_ConcreteCollection relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | CLOUDDEPLOYMENT | BMC_CloudInstance (Service) | BMC_ConcreteCollection |
BMC_Dependency | CLOUDDEPLOYMENT | BMC_Cluster (Service) | BMC_ConcreteCollection |
|
|
|
|
Mapping of VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes
Where VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes that are cloud hosted are populated, it is done so using the same rules as for those on a Host node. The mapping rules are shown below:
BMC_VirtualSystemEnabler and virtualization
When a physical machine hosts one or more virtual machines, the Discovery model represents it as a number of Virtual Machine nodes related to the physical Host, one Virtual Machine node per virtual host. A BMC_VirtualSystemEnabler CI is created for each VirtualMachine node.
Difference with previous releases
Previous releases of BMC Discovery, before version 11.2 created a single BMC_VirtualSystemEnabler CI to represent all virtual machines hosted by a physical machine. Upon first synchronization after upgrade from versions before 11.2, these singleton CIs will be marked as deleted, and new separate CIs will be created corresponding to the separate virtual machines.
Attribute | Details |
---|---|
Name | VirtualMachine name |
ShortDescription | VirtualMachine |
Description | VirtualMachine |
BuildNumber | VirtualMachine |
EnablerType | Enumeration representing the type of virtualization technology |
InstanceName |
where Introduced in the November 2019 TKU to support integrations. |
isCloud | Yes if the virtual machine is known to be cloud hosted; null if not |
ManufacturerName | Publisher. |
MarketVersion | VirtualMachine |
Model | VirtualMachine |
PatchNumber | VirtualMachine |
ServicePack | VirtualMachine |
VersionNumber | VirtualMachine |
ComponentAliases | VirtualMachine cdm_component_aliases |
Company | Host Company |
Category | " |
Type | " |
Item | " |
Virtualization relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_HostedSystemComponents | HOSTEDSYSTEMCOMPONENTS | BMC_CloudInstance | BMC_VirtualSystemEnabler Impacted |
|
|
|
Impacted |
|
|
|
|
BMC_SoftwareServer and BMC_ApplicationSystem
Each SoftwareInstance
in the Discovery model is mapped to either a BMC_SoftwareServer CI or a BMC_ApplicationSystem CI:
SoftwareInstance
nodes with DDD triggers are directly running on a single host, and are mapped toBMC_SoftwareServer
SoftwareInstance
nodes composed of otherSoftwareInstance
nodes are mapped toBMC_ApplicationSystem
.
SoftwareInstance
nodes are also mapped (in an indirect manner) to BMC_Product
.
Except as noted, the attributes set are the same in BMC_SoftwareServer and BMC_ApplicationSystem.
Attribute | Details |
---|---|
TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources.TokenId is of the form "ADDM: hashedkey", where hashedkey is a hash of Software Instance key |
Name | Software Instance |
ShortDescription | Software Instance |
Description | Software Instance |
BuildNumber | Software Instance |
InstanceName |
where Introduced in the November 2019 TKU to support integrations. |
isCloud | Yes if the software instance is known to be cloud hosted; null if not |
ManufacturerName | Publisher specified in the maintaining Pattern or on the Software Instance |
MarketVersion | Software Instance |
Model | Software Instance |
OtherSoftwareServerType | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
SoftwareServerType | Enumeration representing the type of SoftwareServer. Often 0 meaning "Other". (Only in |
VersionNumber | Software Instance |
ComponentAliases | Software Instance cdm_component_aliases |
Company | Software Instance Company. |
Category | " |
Type | " |
Item | Product category from the maintaining Pattern |
Item values
The Item
attribute is populated from the Pattern that is maintaining the Software Instance. To obtain a list of all the possible Item
values, perform the following query in the Discovery Generic Query page:
search Pattern show categories processwith countUnique(0)
BMC_SoftwareServer and BMC_ApplicationSystem relationships
As shown in the table, BMC_SoftwareServer and BMC_ApplicationSystem CIs can be related to each other with a BMC_Dependency relationship. This is mapped from both Dependency and Communication relationships between the SoftwareInstance nodes in the Discovery model.
BMC_SoftwareServer and BMC_ApplicationSystem CIs also have relationships to BMC_Product
, shown in the Product relationships table.
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_Component | APPLICATIONSYSTEMHIERARCHY | BMC_SoftwareServer (containing) | BMC_SoftwareServer (contained) |
|
|
|
|
| APPLICATIONSYSTEMDEPENDENCY | BMC_SoftwareServer (facet) | BMC_SoftwareServer (main facet)Impacted |
Communication relationships between nodes are mapped to a dependency between CIs.
Relationship | Name | Source | Destination |
---|---|---|---|
|
| Server (depended upon)
| (dependant)
Impacted |
|
| Client (dependant)
Impacted | Server (depended upon)
|
Observed Communication relationship between nodes mapped to Dependency between CIs. Due to the very high volume of Observed Communication relationships, only those that are part of application models are synchronized.
Relationship | Name | Source | Destination |
---|---|---|---|
|
| Listening
|
Impacted |
|
|
| Connecting
Impacted |
Management relationships
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | SYSTEMMANAGER | First-order SI. Second-order SI
|
|
BMC_Dependency | SOFTWAREMANAGER |
| BMC_SoftwareServer First-order SI.BMC_ApplicationSystem Second-order SI. |
Although the manager impacts the CI it is managing, we do not mark the relationship as impactful, to avoid impact cycles.
BMC_Document
The new synchronization mapping attribute DocumentType "TLS Certificate" has been added to the BMC_Document CIs. When SoftwareInstance or LoadBalancerService nodes represent web servers for which TLS/SSL certificates have been discovered, they have related Detail nodes with type "TLS Certificate". The BMC_Document mapping was introduced in Technology Knowledge Update TKU 2020-Sep-1. For more information, see TLS Certificates Discovery for Unix.
These Detail nodes are mapped to BMC_Document CIs with the following attributes:
Attribute | Details |
---|---|
Name | Detail name |
ShortDescription | Detail short_name |
Description | Detail common_name |
Author | Detail issuer. The certificate issuer. |
DocumentType | "TLS Certificate" |
EndDate | Detail expiry_date. The certificate end (valid to) date. |
SerialNumber | Detail serial. The certificate serial number. |
StartDate | Detail start_date. The certificate start (valid from) date. |
Company | Host Company. |
Category | "Software" |
Type | "TLS Certificate" |
Item | "BMC Discovered" |
BMC_Document relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_DataBase
Database
nodes (logical databases) are mapped to BMC_DataBase
:
Attribute | Details |
---|---|
TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources.TokenId is of the form "%hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance%" or "%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance%" |
Name | Database |
ShortDescription | Database |
Description | Description is of the form
|
InstanceName |
where Introduced in the November 2019 TKU to support integrations. |
IsCloud | Yes if the database is known to be cloud hosted; null if not |
Model | DatabaseDetail |
Company | Host Company. |
Category | " |
Type | " |
Item | " |
ManufacturerName | Software Instance |
MarketVersion | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
BMC_DataBase relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
| MANAGEDDATABASE | BMC_ApplicationSystem | BMC_DataBase Impacted |
| MANAGEDDATABASE | BMC_Cluster | BMC_DataBase Impacted |
Comments
Log in or register to comment.