Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Infrastructure Provisioning use case

The goals of the Infrastructure Provisioning use case are:

  • Heterogeneous and reusable packaging
  • Nondisruptive updates
  • Virtual and physical cross-platform provisioning

BMC Server Automation (BSA) can provision both physical and virtual servers using the same system packages. The following diagram shows the flow of information and the components involved in the use case.

infrastructure_provisioning3.jpg

This use case has the following steps:

  1. The BMC Server Automation operator creates a system package.
  2. The operator creates a job to deploy the package to on one or more bare metal servers, physical or virtual.
  3. If required, the operator can create a batch job to combine the provisioning job with additional software deployment jobs.
  4. Executing the provisioning or batch job provisions the server and enrolls it as a managed server in BMC Server Automation. The Operator Initiated Change use case can be employed if the provisioning activity requires change approval, or if real-time CMDB updates are needed. Otherwise, the CMDB is updated in batch using the BMC Server Automation integration with BMC Atrium CMDB.

 

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