How BMC Atrium Orchestrator Run Book for NetApp Solutions works

This section provides a high-level view of the use cases that the run book addresses.

Provisioning storage

The BMC Atrium Orchestrator storage provisioning workflows validate the request for storage. The storage provisioning workflows verify whether the storage requests can be fulfilled. If a storage request cannot be fulfilled, BMC Atrium Orchestrator retrieves details about the request. This information is used to trigger a change that contains the necessary information for you to approve or reject the change request.

After the storage provisioning request is validated and approved, the request is fulfilled. The workflows interface with VMware to create a datastore from the provisioned storage.

Provisioning a virtual server

Virtual machine requests are based on the storage service profile: Gold, Silver, or Platinum. Before the BMC Atrium Orchestrator workflows provision a virtual server, they use the storage profile to check for the appropriate datastore for the placement of the virtual machine.

If the datastores have the required space, then the workflows provision the virtual server to the datastore with the available space. Based on the virtual server provisioning request, the workflows perform the following action:

  • Deploy the VM from a VMware template
  • Deploy the VM from scratch (bare metal)
  • Clone the VM from a template by using NetApp cloning technology within the same or a different datastore

After the virtual server provisioning request is validated and approved, the request is fulfilled. BMC Atrium Orchestrator run book workflows provision the virtual server requested and associate the name of the server with the datastore. The workflows interface with VMware to associate the virtual server to a datastore.

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.

Comments