Overview of the Savvis Provider
This topic provides an overivew of the Savvis Provider. It includes the following sections:
Key features
This release contains the following new features and enhancements:
- Onboarding and offboarding a Network Container (Essential, Premier, and Balanced)
- Registering a Savvis Provider instance
- Provisioning of new virtual machines (VMs) based on Savvis templates or on a customized template
- Specifying additional disks in blueprints
- Starting, stopping, fencing and unfencing of provisioned VMs
- Modifying the memory and CPUs of a provisioned VM
- Decommissioning provisioned VMs
- Extending the commission length of provisioned VMs
- Installing software on provisioned VMs
- User provisioning on provisioned VMs
Credentials for accessing the VM can be provided when a user requests a Service Offering. - Supporting multiple Savvis accounts
Product compatibility
This release integrates with:
- BMC Cloud Lifecycle Management 4.0.00
- Savvis Application Programming Interface Version V1.5
- Savvis vCloud Application Programming Interface V1.5
Limitations
This section discusses the limitations of the Savvis Provider.
When provisioning from a custom image
A Virtual Private Data Center (VPDC) should be created in the same location where the custom image template has been created or uploaded.
When provisioning in an Essential VPDC
Software cannot be installed because the ports are not open. Therefore, the BMC Server Automation RSCD agent cannot be installed.
Only the same pod resources can be assigned to a pod
You can assign a resource of the same pod only, but cannot assign a resource of a different pod. For example, you can onboard only an Asia resource in an Asia pod, not another pod resource in an Asia pod.
Savvis construct mappings
The following table lists BMC Cloud Lifecycle Management objects and describes how they correspond to Savvis constructs.
BMC Cloud Lifecycle Management object mappings for Savvis