BMC Server Automation enables IT organizations to manage both physical and virtual environments from one platform, allowing organizations to achieve the same level of operational efficiency for both their physical and virtual environments. This topic describes:
The BMC Server Automation administrator must install and configure the virtual environment. For more information, see Setting up BMC Server Automation for virtual environments.
The server auditing and compliance capabilities in BMC Server Automation involve:
The following table describes the capabilities in BMC Server Automation that are useful in managing, controlling, and enforcing configuration changes to your server and application environments, regardless of whether the environment is virtual or physical.
Base-lining the environment
Use a Snapshot Job to establish a baseline of the virtual environment (for example, a host, virtual machine, LPAR, and so on), so that you can then track audit discrepancies or compliance violations using an Audit or Compliance Job.
Auditing the environment
To ensure that there are no unauthorized changes in server configuration, the BMC Server Automation operator can run an Audit Job periodically to compare each virtual asset configuration with one or more baseline configurations. Any detected differences in the configurations are treated as audit discrepancies in BMC Server Automation and can be rectified by running a remediation job (automatically or manually) to synchronize the virtual assets (servers, virtual systems, and so on).
Ensuring compliance to standards
To prevent unauthorized or unwanted changes in the virtual infrastructure, the BMC Server Automation operator can run a Compliance job periodically that compares the configuration of each virtual asset against certain rules and policies (for example, operational or regulatory policies).
Remediating issues in the environment
You can create a remediation package for a virtual asset that has failed an Audit or Compliance Job. You create a BLPackage that consolidates all remediation actions specified in the audit or compliance rules that the target component has failed.
You can run Snapshot, Audit, and Compliance Jobs on a variety of virtual infrastructure server nodes (including clusters, hosts, AIX LPARS, VIO Servers, Solaris non-global zones, and so on) to verify that virtual inventory configurations meet corporate standards.
For example, you could run a Snapshot Job on a vCenter server's Inventory node to check to see if any virtual machines have been added to, or removed from, a given data center. To see what virtual environments are supported, see Overview of virtualization support.
Snapshot Jobs and Audit Jobs are not supported at the root level, for Citrix XenServer.
You can then remediate the virtual assets that fail audit or are found to be non-compliant, using a remediation job. For example, suppose you run a Compliance Job and discover that a virtual machine's memory settings are non-compliant. You can run a Deploy Job to deploy a BLPackage with the proper configuration settings that remediates the problem on the virtual machine. For additional information about remediating problem systems, see Creating a remediation package.
You can use the general principles from the following example to perform snapshot and audit operations on nodes in a virtual environment.