This topic describes how to create and manage Savvis service offerings that cloud users can request from the BMC My Cloud Services Console.

A service offering describes a function or capability that a cloud administrator makes available to users in the cloud. Application stacks, single servers, and adding a new account to a Microsoft Exchange server are all examples of services. For more general information about services, see Services overview.

After you have mapped the tenants to the Logical Data Centers or Network Containers, you then can define your service blueprint for the Savvis Provider. Service blueprints define the software, hardware, and deployment options for a service in the Service Catalog. A service blueprint is required before you can create a service. For service blueprint overview information, see Service blueprints overview.

You can group requestable offerings into packages, to which different tenants can be entitled. This makes it easier for service providers to partition and manage services created specifically for particular tenants.

The following topics provide information and instructions for creating and managing an Savvis service using the BMC Cloud Lifecycle Management:

To create Savvis blueprints

Create service blueprints, as described in Building service blueprints and according to the Savvis service offering specifications. Ensure that you follow the guidelines that are specific to the Savvis blueprints:

• In the Compute Resources pane, add the Installable Resource that you have auto-onboarded.
  

• To enable software installation as a part of Savvis service offering, you must create a BMC Server Automation Deploy Job or an application component template.

• You must create the DML entries for the software to be installed as per Executing the Publish Product Catalog Job documentation.

• You must ensure that the Install Software option is checked.

• You must define the network tags on the onboarded networks.

  Note

  • Ensure that you specify the Tier01 label for the Essential service profile. For the Balanced and Premier service profiles you can specify virtual machine (VM) Tier01, VM Tier02, and VM Tier03 label values, but the VM will be provisioned only in the selected label.
  • Custom images will always be provisioned in Tier01. For details, see Limitations of the Savvis Provider
• Select Private IP as Dynamic if the IP needs to be selected dynamically while provisioning the VM. In case of Static, select the IP for VM provisioning.

• The Assign NAT Address does not have any impact on Savvis provisioning. Instead, specify the BMCPublicAssignIP as a service deployment parameter.

• Define the following service deployment parameters for the deployment packages during multi-tier VM provisioning:

  • BMCAssignPublicIP — Define this parameter as a Boolean data type. If the value is True, a Public IP is assigned to the VM, and if the value is False, a Private IP is assigned to the VM during provisioning.

To create requestable Savvis services and make them available to cloud users

1. Create services, service offerings in the Service Catalog, as described in Creating services.

2. Define your Savvis requestable offering as you would any other offering in the Service Catalog. For instructions, see Creating a requestable offering definition.

   Note

   For the Savvis definition, you select Savvis for the Type value. 

3. Create packages of requestable offerings that tenant users can access, as described in Creating entitlement packages.

4. Assign packages to tenants, as described in Selecting tenant entitlement packages.

To request a Savvis service

You can request Savvis cloud service offerings from the BMC Cloud Lifecycle Management – My Cloud Services Console, based on the services available to you in the service catalog. 

To manage Savvis services

From the My Cloud Services Console, you can perform the following tasks to manage your Savvis cloud services: