In this article:
- Creating a Lumen DCC provider
- Editing Policy Boxes on Lumen DCC
- Deploying Instances from Deployment Policies
- Contacting Cloud Application Manager Support
This article is meant to assist users of Cloud Application Manager to learn how to use a Lumen DCC (Dedicated Cloud Compute) provider.
All Cloud Application Manager users who want to integrate with an existing Lumen DCC environment.
- You must have a Cloud Application Manager Account
- Your user credentials for the Lumen DCC environment.
Creating a Lumen DCC provider
Select Lumen DCC from the Provider list and enter a username and password to logon to the Lumen DCC Portal.
The user must have "customer purchase permission" and an associated billing account in Lumen DCC to operate in the Cloud Application Manager.
If this is not the case, open a ticket here to get it fixed.
Once the provider information is saved, Cloud Application Manager starts synchronizing the Provider account. After the synchronization is complete, Cloud Application Manager creates default Deployment Policies with the different deployment options available.
The user account used when creating the Provider is linked to a Company, Billing Site, Clusters, Domains, etc.
When the synchronization process finishes, the list of Linux and Windows Templates available to deploy on each cluster is available on the provider's "Configuration" tab.
Editing Policy Boxes on Lumen DCC
In addition to the services list, Cloud Application Manager creates sample Policy Boxes for Linux and Windows. These can be customized anytime.
To do this, access the details by selecting "Code", then "Edit", where the following options are available:
|Company||Select the company of your DDC provider.|
|Billing Site||Select the billing site of your DDC provider.|
|Datacenter||Clusters are grouped in Datacenters. To select a Cluster, Cloud Application Manager needs to know the Datacenter the Cluster belongs to.|
|Cluster||Select the cluster where you want to deploy.|
|Domain||Select the domain where you want to deploy.|
|Machine configuration||Select the profile of the machine.|
|OS||Select from a list of Lumen DCC Linux or Windows images.|
|Language||Select the languaje of instance.|
|Instances||Cloud Application Manager can deploy several servers at once, with the restriction that all the operations run on all the instances (start, stop, delete, and script boxes installation).|
|VCPU||Select the number of CPUs.|
|VRAM||Select the amount of memory assigned to the Virtual Machine.|
|Storage||Select the disk group to use.|
|Network||The net segment where the VM is configured. Please note that the IP address is set automatically. The user must select a segment with available IP addresses.|
|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.|
Deploying Instances from Deployment Policies
Virtual machines get deployed on clusters. If Cloud Application Manager doesn't have enough information to deploy a cluster, the cluster will not be available as a deployment option for the Policy Boxes. In that case, Cloud Application Manager displays an alert in the provider activity logs as follows.
Once the Box deploys, Cloud Application Manager shows the traces of what is happening with the provider. At the end of the process it displays a script that has to be executed manually on the newly created Virtual Machine to complete the ALM agent installation.
Credentials for the Virtual Machine are sent via email which contains the necessary privileges to install the Cloud Application Manager agent using the script shown above.
To run this script, the user needs access to the new Virtual Machines. This task, as in the creation of the account, needs to be done by Lumen DCC.
Once this is done, the deployment process is complete.
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 error registering an instance, share the instance to a workspace that your organization and Cloud Application Manager support group can access and attach the logs.
- Linux: SSH into the instance 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