This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Virtualization modeling

A number of different techniques are currently referred to as virtualization. In the Common Data Model, two design patterns are used to represent these techniques:

  • A design pattern that considers the host to be running inside a virtual machine. This denotes software based machine emulation for a virtual machine.
  • A design pattern that considers the host to be running on a fractional allocation of the underlying physical hardware. This denotes fixed partitioning of a larger hardware resource.

The BMC_VirtualSystemSettingData class (derived from BMC_Settings) is an important class in virtualization as it contains vital information related to virtualization. This class provides additional granularity about a virtual system’s settings through a set of virtualization-specific properties.

This section provides:

Virtual machine design pattern

This design pattern is appropriate where the supporting system is one of the following:

  • A conventional operating system running a third party or internal virtual machine using virtualization technology
  • A kernel micro-partitioning scheme such as Solaris Containers or IBM POWER Systems Workload Partitions (WPARs)
  • Bare metal virtual machine-based hypervisors such as VMware ESX and Microsoft Hyper-V

Note

The virtual machine model design pattern is not appropriate for Chassis Blade type systems and Hardware partitioning based hypervisors such as Solaris LDOM or IBM POWER Systems Dynamic Logical Partitions (DLPAR).

By design, a system running in a virtual machine should be indistinguishable from one running in a physical machine. For both this conceptual and practical reason, the

BMC_ComputerSystem

class and attributes are used for both systems.

To distinguish the two types of machine, the BMC_ComputerSystem.isVirtual attribute flag is set. The isVirtual attribute values include:

  • 1(Yes) if the system is known to be running in a virtual machine
  • 0(No) if the system is known to be running in a physical machine
  • NULL if neither state is known with sufficient confidence

Virtual systems design pattern

While the design pattern accounts for systems to be explicitly marked as physical, most data sources do not set BMC_ComputerSystem.isVirtual to 0 (No). If you wish to set the isVirtual attribute strictly correct, data from different sources often does not reconcile. In these circumstances, leave the value as NULL.

In the following virtual systems model design pattern:

  • A shows a virtual system, thus denoted as BMC_ComputerSystem.isVirtual is set to 1 (Yes).
  • B shows system which could either be physical or virtual. In such case, the BMC_ComputerSystem.isVirtual and BMC_ComputerSystem.ManufacturerName attributes are set to NULL.
  • C shows a physical system denoted as BMC_ComputerSystem.isVirtual is set to NULL.

Virtual systems design model

To show the technology aspects of the virtualization, an instance of BMC_VirtualSystemEnabler is used. This is a single instance per supporting system. It is related to the supporting system by BMC_HostedSystemComponents with Name=HOSTEDSYSTEMCOMPONENTS) where the supporting system is the source and the virtualization technology is the destination. It is related to the virtual systems by BMC_Dependency with Name=VIRTUALSYSTEMOS where the virtualization technology is the source and the virtual systems is the destination.

The following diagram shows a physical virtual machine system supporting two virtual systems. To show the dependency of the virtual systems on the supporting system, the BMC_ComputerSystem virtual system instances are related to the supporting BMC_ComputerSystem instance using BMC_Dependency relationship with Name=HOSTEDVIRTUALSYSTEM.  

  • A shows the technology details such as version, type, and so on.
  • B and C show two virtual machines, with the BMC_ComputerSystem.isVirtual attribute set to 1 (Yes).
  • D shows the physical server which retains the BMC_ComputerSystem.isVirtual value as NULL to ease reconciliation.

Partitioned host design model

Partitioned host design pattern is based on the division of a single server into several completely independent logical partitions, where each partition is an independent virtual server. This design pattern is appropriate for hardware partitioning-based hypervisors such as a Oracle Solaris LDOM or IBM POWER Systems Dynamic Logical Partitions (DLPAR). 

An instance of BMC_VirtualSystemEnabler is used to represent the virtualization technology software that enables virtualization. This is a single instance per supporting system. It is related to each of the partitioned system by BMC_HostedSystemComponents with Name=HOSTEDSYSTEMCOMPONENTS where the partitioned system is the source and the virtualized technology (BMC_VirtualSystemEnabler) is the destination. It is related to the virtual systems by BMC_Dependency with Name=VIRTUALSYSTEMOS where the virtualization technology (BMC_VirtualSystemEnabler) is the source and the virtual systems is the destination.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Michael Henigin

    Should the Hosted System Component in the virtual systems design model be a Virtual System Enabler and not Computer System?  Thanks for the info.  

    Mar 17, 2016 09:17
    1. Amol Redij

      Hi Michael,

      Thank you for your patience.

      You were right about the hosted system component. We have updated the image accordingly.

      Regards,

      Amol

      Nov 21, 2016 02:41
  2. Sergei Nikishin

    Amol, were you referring to the image in "Virtual systems design model" section? It still has BMC_ComputerSystem instead of BMC_VirtualSystemEnabler, and I believe it is incorrect. 

    May 26, 2017 11:10
    1. Nidhi Das

      Hello Sergei,

      We have updated the image.

      Regards,
      Nidhi

      Jul 31, 2017 01:48
      1. Sergei Nikishin

        Thank you, Nidhi! Looks better.

        Jul 31, 2017 04:30
  3. Vinay Bellare

    Hi Sergei,

    Thanks for pointing this out. I will get in touch with the SME to resolve the image issue.

    Regards,
    Vinay

    May 29, 2017 12:55
  4. Kunal Bhatt

    I have small doubt - when can we use BMC_VirtualSystemSettingData class.? what relationship details? to be followed - some graphical e.g. will be very helpful.

    Nov 26, 2018 02:05
    1. Maithili Deshpande

      Hi Kunal, 

      Thanks for your query. Will speak to the SME and respond at the earliest. 

      Regards,

      Maithili

      Nov 29, 2018 11:32
    1. Maithili Deshpande

      Hi Kunal, 

      I discussed this with the SME and suggest that you reach out to the Customer Support team (https://www.bmc.com/support/resources/issue-defect-management.html)

      Please check this link, if you haven't already. It has a couple of examples, but not graphical ones. 

      Do let me know if you have any other queries.

      Regards,

      Maithili

      Dec 27, 2018 04:29
  5. Kunal Bhatt

    In "Virtual systems design model" Diagram....I guess - Physical Server (ComputerSystem) need to be "Source" and "VirtualSystemEnabler" will be "Destination" - hence relationship arrow direction will go from ComputerSystem towards VirtualSystemEnabler - Please correct me if something wrong I understood from CDM.

    Dec 16, 2018 04:48
    1. Maithili Deshpande

      Hi Kunal, 

      Thank you for your query. Will check with the SME and respond at the earliest. 

      Regards,

      Maithili

      Dec 17, 2018 05:36
      1. Kunal Bhatt

        Hi Maithili - I would like to follow-up on my suggestion.

        Dec 22, 2018 04:19
        1. Maithili Deshpande

          Hi Kunal,

          We are working on this. Will keep you posted.

          Thanks, Maithili

          Dec 24, 2018 01:49
    1. Maithili Deshpande

      Hi Kunal, 

      Thank you for pointing this out. Have changed the image accordingly. 

      Regards,

      Maithili

      Jan 17, 2019 03:56
  6. Kunal Bhatt

    Thanks Maithili !

    Jan 17, 2019 04:07