In this article:
- Connect CenturyLink DEC3 environment in Cloud Application Manager
- Deploy to CenturyLink DEC3 from Cloud Application Manager
- Discovering and Registering Existing instances
- Accessing the DEC3 native console
- Contacting Cloud Application Manager Support
This article is meant to assist users of Cloud Application Manager to learn how to deploy a CenturyLink DEC 3 Provider, available only in Latin America region.
All Cloud Application Manager users who want to deploy workloads into a CenturyLink DEC 3 Provider.
- You must have a Cloud Application Manager Account
- Your base URL, and user credentials for your CenturyLink DEC 3 subscription
Connect CenturyLink DEC3 environment in Cloud Application Manager
Follow these steps to add a provider in Cloud Application Manager that integrates with your CenturyLink DEC 3 environment. Each provider connects to the virtual data center in that specific location.
Add a provider in CenturyLink DEC3
In Cloud Application Manager, on the Providers page, click New Provider.
Select CenturyLink DEC3 and fill in the required fields:
- URL. Enter the URL to access the CenturyLink DEC3 portal
- Tenant. Select the tenant your environment is hosted into.
- Domain. Enter the domain of your environment
- Username. Enter the username to log in to your CenturyLink DEC3 account.
- Password. Enter the password for your CenturyLink DEC3 account.
Deploy to CenturyLink DEC3 from Cloud Application Manager
Create a deployment policy to encapsulate parameters required to deploy Linux or Windows instances through the CenturyLink DEC3 provider
At deploy time, Cloud Application Manager auto provisions a vRealize instance and orchestrates workload automation on them.
Note: Auto provisioning may fail if you specify virtual CPUs, memory, and virtual disk capacity that exceeds the limit in your virtual data center.
Edit the deployment policy to set the following parameters for deploying to CenturyLink DEC3.
|Catalog Item||Select the template from the catalog to be used for deployment.|
|Instances||Specify the number of instances to spawn from the same template.|
|CPUs||Specify the number of CPUs.|
|Memory||Specify the virtual RAM in MB.|
|Network||Specify the network to deploy to.|
|Host||The hostname or domain of the proxy that the agent will use to connect back to Cloud Application Manager, once it has been installed in the deployed instance.|
|Port||The port of the proxy that the agent will use to connect back to Cloud Application Manager, once it has been installed in the deployed instance.|
|Disk||Specify the storage capacity in GB. Adding disk storage capacity is supported.|
Discovering and Registering Existing instances
When you configure your CenturyLink DEC3 provider in Cloud Application Manager, the synchronization process will discover the existing instances in your account. You will see these instances in the Unregistered Instances tab in the provider details page or in the Unregistered resources in the instances page.
For more information about the registration process, also known as import instance process, refer to how to Register an Existing Instance
Accessing the DEC3 native console
Once your provider is synchronized, you will be able to access the DEC3 native console through the button available in the provider details page:
When you click on the button, a new window or tab will open in your browser with the access page of your DEC3 console:
Contacting Cloud Application Manager Support
For issues related to API calls, send the request body along with details related to the issue.
In the case of a box error, share the box in the workspace that your organization and Cloud Application Manager can access and attach the logs.
- Linux: SSH and locate the log at /var/log/elasticbox/elasticbox-agent.log
- Windows: RDP into the instance to locate the log at \ProgramData\ElasticBox\Logs\elasticbox-agent.log