Performance results

Overview

A performance testing exercise was carried out to evaluate the performance of BMC Continuous Compliance for Server Automation 8.1 solution.  These performance testing results provide the details used to size the BMC BladeLogic Automation Suite 8.1 solution.

The scope of performance testing was limited to Closed Loop Server Compliance workflows comprising following products:

• BMC Atrium Orchestrator
  • BMC Atrium Orchestrator Content version 7.6.05.00
  • BMC Atrium Orchestrator Platform version 7.6.01.04
• BMC Remedy Action Request (AR) System version 7.6.04
• BMC Atrium CMDB version 7.6.04
• BMC Remedy ITSM version 7.6.04
• BMC BladeLogic Server Automation version 8.1 build 291

Methodology

The following methodology was used to conduct the performance testing for the Closed Loop Server Compliance workflows:

1. An environment based on last release’s recommendations was set up.
2. Scenarios describing the total number of targets that contained compliant and noncompliant targets were identified and executed.
3. One hundred physical virtual machines (VMs) were available as target machines; additional machines were created by using aliases (that is, the same IP was assigned to multiple machine names).
4. A template of 20 rules was created out of which 7 rules were unique.
5. BMC BladeLogic Server Automation Console was used to execute the Closed Loop Server Compliance jobs for testing the compliance of targets against the rule template.
6. The percentage of noncompliant targets was kept at 1 percent of total targets.
7. The BMC Atrium Orchestrator CDP logs and Grid logs were enabled and used for identifying the time taken for important processes to execute at the BMC Atrium Orchestrator server.
8. The BMC BladeLogic Server Automation console was used to determine the time taken to execute the compliance job on the BMC BladeLogic Server Automation server.
9. BMC Remedy ITSM was used for determining the time taken to create the CRs for noncompliant targets.

The following unique Compliance Rules were added to the template:

1. Unix User /root Must Exist
2. Configuration File Entry /etc/group//root Must Exist AND (Value3 as String (All OS) = "root")
3. Configuration File Entry /etc/passwd//root Must Exist AND (Value4 as String (All OS) = "root")
4. File /etc/aliases Must Exist
5. File /bin/df Must Exist
6. File /etc/mail.rc Must Exist AND (Contents contains "Status")
7. Unix User /patqa1 Must Exist