Overview of the Terremark Provider

This topic provides an overview of the Terremark Provider. It includes the following sections:

• • High-level tasks for setting up the Terremark Provider
  • Cloud administrator tasks
  • Cloud end-user tasks
  • Terremark Provider release content and features
  • Product compatibility
  • Limitations and known issues for Terremark
    • Limitations
    • Known issues
  • Troubleshooting the Terremark Provider

High-level tasks for setting up the Terremark Provider

Adding the Terremark Provider is a process that consists of multiple procedures. The following list outlines the high-level steps to add the Terremark Provider to BMC Cloud Lifecycle Management as a provider type:

1. Perform Terremark Provider installation
2. Register the Terremark Provider instance
3. Add multiple Terremark accounts
4. Onboard Terremark Logical Data Centers

Cloud administrator tasks

The cloud administrator is an IT professional responsible for the full lifecycle of the cloud environment, including initial planning, deployment, and configuration, and continued administration, operation, and maintenance. Listed here are the primary Terremark Provider tasks for cloud administrators of BMC Cloud Lifecycle Management.

• Setting up the Terremark Provider
• Creating-memory-CPU-options-and-option-choices-in-the-Terremark-Provider
• Uploading-custom-templates-in-the-Terremark-Provider
• Configuring-multi-tier-Terremark-Provider-resources-in-BMC-Cloud-Lifecycle-Management
• Creating-tag-groups-and-tags
• Managing service offerings for Terremark end-users

Cloud end-user tasks

Cloud end-users rely on cloud resources to complete their work. Cloud end-users request services, such as the deployment of virtual machines (VMs), by using the BMC My Cloud Services Console. Listed here are the primary Terremark Provider tasks for cloud end-users of BMC Cloud Lifecycle Management.

• Requesting Terremark cloud services

  Note

  You can specify the user name and password from BMC Cloud Lifecycle Management during VM provisioning.You should specify the password according to the password policy of the VM templates. If you have problems accessing the VMs after provisioning, see Terremark-provider-issues.

• Starting-stopping-and-shutting-down-cloud-services
• Modifying-memory-and-CPU-option-choices-in-the-Terremark-Provider
• Decommissioning-cloud-services

• Extending-the-commission-length-of-cloud-services

  Note

  • When you decommission a Terremark Enterprise Cloud service, the associated nodes and internet services are automatically deleted from the Terremark Enterprise Cloud.
  • When you extend the life of a Terremark Enterprise Cloud service, a new decommission date is defined in BMC Cloud Lifecycle Management.

Terremark Provider release content and features

This release contains the contains the Terremark installer and provides the following new features and enhancements:

• Onboarding and offboarding a Logical Data Center
• Registering a Terremark Provider instance
• Provisioning of new virtual machines (VMs) based on Terremark templates or on a customized template
• Starting and stopping the provisioned VMs
• Modifying the memory and CPUs of a provisioned VMs
• Decommissioning provisioned VMs
• Extending the commission length of provisioned VMs
• Installing software while provisioning VMs
• User provisioning on provisioned VMs
   User credentials for accessing the VM can be provided when a user requests a service offering. These credentials can be used to access the VM after provisioning is completed.
• Supporting multiple Terremark accounts

Product compatibility

This release integrates with:

• BMC Cloud Lifecycle Management 3.1.00
• Enterprise Cloud Application Programming Interface Version 2012-12-01

Limitations and known issues for Terremark

When you create a virtual machine (VM) in the Terremark Provider, consider the following limitations and known issues:

Limitations

• BMC Cloud Lifecycle Management does not synchronize modified or deleted Terremark Enterprise Cloud templates.
• BMC Cloud Lifecycle Management does not synchronize any changes made to Terremark VMs by using Terremark portal . For example, if you stop a VM in the Terremark Enterprise Cloud, this action is not synchronized in BMC Cloud Lifecycle Management.
• A single IP is assigned to every provisioned VM in the Terremark Enterprise Cloud.  The Terremark Provider enables assigning of multiple IPs.
• When you provision VMs with internal IPs, you should have access to a Terremark Virtual Private Network (VPN) to access the provisioned VMs.
• When you provision VMs from BMC Cloud Lifecycle Management, you cannot configure firewalls and load balancers in Terremark Enterprise Cloud by using BMC Cloud Lifecycle Management consoles.
• You cannot modify the disk size of a provisioned VM.
• When you deregister a Terremark Provider instance, the Terremark blueprints are not removed automatically.
• You do not receive an error if you register a Terremark Provider instance with an incorrect Terremark user name and password.

Known issues

The following table lists the known issues for the Terremark Provider:

Troubleshooting the Terremark Provider

You can diagnose issues related to the Terremark Provider as described in Terremark-provider-issues.