Configuring Savvis resources in BMC Cloud Lifecycle Management

After you have installed and configured the Savvis Provider in your environment, you can begin managing Savvis resources within BMC Cloud Lifecycle Management. This topic describes how to register and configure Savvis resources.

Before you begin

• Ensure that you have set up the Savvis Provider, as described in Configuring-the-Savvis-Provider.
• Ensure that your Savvis user account has the required permissions to access and work with the Savvis APIs and resources.
• Ensure that the IP address of the computer from which the Savvis APIs are called is white-labeled with Savvis. 

To configure Savvis resources

1. Log on to the BMC Cloud Lifecycle Management Administration Console with an account that has cloud admin privileges.
2. Onboard a pod by selecting a Savvis region, as described in Onboarding-and-offboarding-network-pods.

3. Import the container blueprint for the onboarded pod, as described in Importing-network-container-blueprints.

   Note

   You can import Premier, Balanced, or Essential container blueprint. See Savvis-service-offering-specifications for details.

4. Create a network container for the Savvis region, as described in Creating-network-containers.
    You need to enter only the container Name, Provider, Tags, Pod, and Container Blueprint details when creating a network container. You need not to specify the Add NAT Address Pools details. The following figure shows the settings for creating a network container.
   

   Note

   When you create a network container

   • Only alphanumeric characters are allowed.
   • Underscore ( _ ), Minus ( - ) , Dot ( . ) are not allowed in the network container name.
   • The network container name cannot be less than 3 characters or more than 29 characters.
   • A maximum of 14 virtual machines (VMs) can be provisioned in an Essential Virtual Private Data Center (VPDC) in Savvis Provider.
   • The Savvis Provider allows provisioning of a maximum of 30 VMs each in Tier01, Tier02, and Tier03.
   • A default Linux VM is automatically created in the Savvis Provider according to Savvis requirements.
   • Select the Provider as Savvis.

5. Onboard a compute resource (virtual cluster), as described in Onboarding-and-offboarding-compute-resources.

   Note

   • A virtual disk repository is automatically on boarded with a virtual cluster. 
   • Select a virtual cluster with the same name as the pod. 
6. Create a virtual cluster compute resource pool for the Savvis region, as described in Creating-compute-resource-pools. The following figure shows the settings for the virtual cluster compute resource pool: 
   
7. Create a virtual disk repository (VDR) compute resource pool for the Savvis region, as described in Creating-compute-resource-pools. 
    The following figure shows the settings for the VDR compute resource pool: 
   
8. Map tenants to the network container, as described in Mapping-tenants-to-network-containers.
9. Map virtual cluster compute pool to the network container, as described in Mapping-resource-pools-to-network-containers.
10. If an OS is not present in the catalog, run a Publish Catalog Job to the enterprise BMC Remedy AR System from BMC Server Automation, as described in Publishing-the-Product-Catalog. 
     The OSGi computer does not need to be connected to BMC Server Automation for this to work. 
11. Create a blueprint, as described in Creating-copying-or-editing-a-service-blueprint, according to Savvis-service-offering-specifications. 
    Specify the resource set in the blueprint as follows:
    1. In the Installable Resource field on the Compute Resources pane, enter the DML entry that is auto-onboarded. 

    2. In the Network Resources pane, specify the network tags for the onboarded networks.

        

12. Create a Service Catalog, as described in Creating-cloud-services. 

13. Provision VMs in the Savvis Provider, as described in Cloud-end-user-using-My-Cloud-Services-Console.

    Note

    Users must contact the cloud administrator for the user name and password of the provisioned VMs.

14. To enable support for modify VM operations, perform the following post deployment tasks: 
    1. Create a post deployment action for CPU and Memory, as described in Creating a requestable offering.
        Before creating the post deployment action, make sure that you understand the limitations of configuring CPU and Memory, as described in Savvis limitations.
    2. Attach this post deployment action with the service created for Savvis provisioning.