Conceptual - Cross-cloud management

Transcription

1 1 Conceptual - Cross-cloud management Dell Cloud Manager (DCM) uses a powerful, open source abstraction layer called Dasein Cloud. Dasein abstracts the different behaviors and capabilities of each cloud. This allows DCM to discover and control each cloud in a consistent way. It allows you to manage your cloud resources from a single dashboard and API, without needing to know many of the technical and conceptual differences between clouds. Each cloud supports different features and behaves in a different way. Through Dasein, DCM discovers these differences. Suppose Cloud A supports load balancers but Cloud B does not. DCM will automatically discover this, and will then show you load balancer management actions for Cloud A but not Cloud B. Likewise, Cloud A may require several steps and several pieces of information in order to launch a server, while Cloud B requires something different. Dasein and DCM abstract this process and present you with a single launching point, along with fields to allow you to select and provide required information for the cloud you have chosen. Adding a Configuration Manager Account Cloud differences Compare clouds Configuring Configuration Management Accounts Managing a cloud account Managing a cloud network Managing a cloud server Requirements for the Dell Cloud Manager Installing the Dell Cloud Manager agent The Dell Cloud Manager Agent enhances the capabilities of Dell Cloud Manager (DCM) by expanding the ability to manage virtual machines (VMs). The agent must be installed on a virtual machine in order to access these expanded capabilities. Conceptual - Agent Installing the Linux Agent Installing the Windows Agent Linux/Windows Java Legacy Agent Migration Supported Clouds 1

2 Amazon (AWS) Azure DigitalOcean Google (GCE) Joyent Supported operating systems and versions CentOS 7.0 (x86_64) CentOS 6.5 (x86_64, i386) CentOS 6.4 (i386) Debian 7.8 (amd64, i386) Debian 6.0 (amd64, i386) RHEL 7.1 (x86_64) RHEL 7.0 (x86_64) RHEL 6.5 (x86_64) RHEL 6.4 (x86_64) Ubuntu (amd64, i386) Ubuntu (amd64, i386) Ubuntu (amd64, i386) Additional details on adding specific clouds Your Amazon cloud Your Azure cloud Your DigitalOcean cloud Your Google Compute Engine cloud Your Joyent Cloud Installing the Linux Agent Two methods are available for installing the Linux agent. METHOD 1 The Agent can be installed on server launch using the User Data section of the server launch screen. 2

3 Copy and paste the following code into the User Data field to install either the Python-based Agent or the legacy Java Agent: Python Agent (current) #!/bin/bash # CHANGE BELOW DCM_HOST=dcm.enstratius.com # CHANGE ABOVE export AGENT_BASE_URL= # we need to be sure that the network is ready before running the script BOOT_LOG=/tmp/boot.log touch $BOOT_LOG cd /tmp curl -kr 10 $AGENT_BASE_URL/installer.sh > installer.sh echo "got the installer" >> $BOOT_LOG bash installer.sh --loglevel DEBUG --base-path /dcm -B --url wss://$dcm_host/agentmanager >> $BOOT_LOG 2> /tmp/error.log echo $? >> $BOOT_LOG echo "ran installer" >> $BOOT_LOG /etc/init.d/dcm-agent start >> $BOOT_LOG 3

4 Java Agent (legacy) curl -L bash -s - -c Amazon -e production -p dcm.enstratius.com:3302 && service tomcat-enstratus start NOTE: Please note that this method of agent installation is only available in the following supported clouds: OpenStack, Azure, CloudStack, Google, Amazon and Joyent. METHOD 2 Follow these steps to install the agent: 1. Log into the server where you want to install the agent. 2. Download the installation script to the server 3. > installer.sh 4. Make sure you have the appropriate permissions to run the installer 5. chmod 755 installer.sh 6. Finally, run the installer and follow the prompts ubuntu@localhost:~$ sudo./installer.sh determining architecture... done ubuntu amd64 Starting the installation process... Downloading DCM Agent from amd64.deb This may take a few minutes. Downloading Installing DCM Agent.... Get instance ID called Instance ID is i-fe3335f2 0) Amazon 1) Azure 2) Bluelock 3) CloudStack 4) CloudStack3 5) Eucalyptus 6) Google 4

5 7) Joyent 8) Konami 9) OpenStack 10) Other 11) UNKNOWN Select your cloud (Amazon): 0 Please enter the contact string of the agent manager (wss://dcm.enstratius.com/agentmanager) wss://dcm.enstratius.com/agentmanager... Would you like to start the agent on boot? (Y/n) Y Adding system startup for /etc/init.d/dcm-agent... /etc/rc0.d/k20dcm-agent ->../init.d/dcm-agent /etc/rc1.d/k20dcm-agent ->../init.d/dcm-agent /etc/rc6.d/k20dcm-agent ->../init.d/dcm-agent /etc/rc2.d/s20dcm-agent ->../init.d/dcm-agent /etc/rc3.d/s20dcm-agent ->../init.d/dcm-agent /etc/rc4.d/s20dcm-agent ->../init.d/dcm-agent /etc/rc5.d/s20dcm-agent ->../init.d/dcm-agent (Optional) Would you like to install chef client? (Y/N) N To start the agent now please run: /etc/init.d/dcm-agent start Conceptual - Agent Installing the Windows Agent Linux/Windows Java Legacy Agent Migration Advanced Documentation Dell Cloud Manager Agent Installing the Windows Agent OPERATING SYSTEM REQUIREMENTS The agent is designed to run on Windows Server 2008 R2 and above. TO INSTALL A MANAGEMENT AGENT ON A WINDOWS SERVER 5

6 1. Log in on the Dell Cloud Manager (DCM) dashboard, click the Cloud Resources menu item and select Servers from the list. Select the Server row on which you want to install the agent and make sure the agent column is blank. 2. Retrieve the Windows server IP address and password. In the console, expand the row for the Windows server, and click View More. Select the Public IP value as server IP address. The password is displayed in the Root Password section. Click the Reveal button. Note: Depending upon the cloud provider, it may take up to 20 minutes for DCM to poll and retrieve the password. 3. Once you have the Windows server public IP address and password, Remote desktop to the Windows Server. Log in to the Windows server using the Administrator account. Note: On Microsoft Azure, in order to connect to the Server, the port has to be added to the IP address as follows: ip_ address:58633 and the Remote Desktop user name is desktop\dasein. 6

7 4. Run Windows Update and install all of the latest Windows updates. 5. Download the latest Dell Cloud Manager Windows Agent installation file and save it on the Windows Server. The URL is 6. Double click on the DCM.Agent.Setup msi that you previously downloaded. NOTE: Be sure you have Administrator rights to install the agent. 7. Configure the options to connect the Dell Cloud Manager Agent to the Dell Cloud Manager Server. a. If the agent is connecting to the Dell Cloud Manager SaaS Server: Select the Production (SaaS) radio button. Select the cloud provider where the server is deployed on. Specify provisioning.enstratius.com for the server address (that should be the default value). b. If the agent is connecting to an On-Premise Dell Cloud Manager Server: Select the Staging (OnPremise) radio button. Select the cloud provider where the server is deployed on. Specify the FQDN or IP address of the On-Premise Dell Cloud Manager server for the server address 8. Click Install to continue the Dell Cloud Manager Agent installation. 9. Finish the installation by checking the "Start the DCM Agent" box and click Finish. 7

8 VERIFYING THE AGENT IS INSTALLED ON WINDOWS Open the Services Control Manager on the server and verify DCM Agent is started and set to Automatic startup. 8

9 You may also want to check the windows server logs under C:\Enstratius\logs. VERIFYING THE AGENT IS CONNECTED TO DCM To test your connection using the DCM Console, follow these steps: 1. From the DCM Console, click the Cloud Resources tab, then select Servers. 2. Locate the server that you installed the DCM agent on. 3. Look at the Agent column. There should be a grey status icon. When you hover over it, you will see contact information for that server. You have successfully confirmed that the agent is connected to DCM. If the agent is installed successfully, server logs will be available in DCM by clicking the View logs button on the server column. 9

10 If you do not see a grey status icon, recheck your installation procedure, and verify the logs on the windows server located under C:\Enstratius\logs. Conceptual - Agent Installing the Linux Agent Linux/Windows Java Legacy Agent Migration Linux/Windows Java Legacy Agent Migration The Dell Cloud Manager Legacy Java Agent v17 and earlier will no longer be compatible as of October 31, Use the following instructions to remove the Linux or Windows Java Legacy Agent and install the new agent. LINUX To determine if the Linux Java Legacy Agent is installed on your virtual machine 10

11 1. ssh in as root. 2. Issue the following command: dpkg -s enstratius-agent (for debian based VMs) or rpm -q enstratius-agent (for CENTOS) To uninstall the Linux Java Legacy Agent from your virtual machine 1. ssh in as root. 2. If the agent is running, stop the service by issuing the following command: /etc/init.d/tomcatenstratus stop 3. Then, issue the following command: dpkg --purge enstratius-agent (for debian based VMs) or rpm -e enstratius-agent (for CENTOS) To install the new Linux Agent Follow the detailed instructions located at WINDOWS To determine if the Windows Java Legacy Agent is installed on your virtual machine 1. Bring up a windows powershell command prompt on your virtual machine. 2. Issue the following command: net start findstr /c:"enstratus" If the response returns: Apache Tomcat enstratus the Dell Cloud Manager Windows JAVA Legacy Agent is installed on your virtual machine and needs to be removed. 3. Stop the service by issuing the following command: net stop Apache Tomcat enstratus NOTE: If you have coded any custom Windows Agent scripts in the c:\enstratus\custom\bin directory, then you will need to back them up in a directory outside of c:\enstratus before you uninstall the Dell Cloud Manager Windows JAVA Legacy Agent. To uninstall the Dell Cloud Manager Windows JAVA Legacy Agent 1. Bring up the Windows control panel and click Programs > Uninstall a program. 2. Right click the Enstratius Agent and click Uninstall. 3. Click Yes to confirm the uninstall of the Enstratius Agent. To install the Dell Cloud Manager Windows.NET Agent Follow the detailed instructions located at - Installing the Windows Agent.htm Launching a stack 11

12 A catalog contains blueprints that can be launched as stacks. You may have access to either your own company catalog or the Dell Cloud Marketplace catalog, or both. To launch a stack 1. From the Dell Cloud Dashboard, select Catalog, then select either your company s catalog or Marketplace (if applicable). 2. Choose a blueprint based on your project needs. Options in different blueprints may include: Number and type of virtual machines Firewall options Variations in supported clouds 3. Give your stack a unique name, fill in required fields, and modify any available options that may be built into the blueprint, including automation. 4. Click Launch. NOTE: If you require different components such as number of virtual machines, firewalls, scaling options, cloud providers, regions, or size options, browse the blueprints in your catalog or contact your administrator. Adding a blueprint Editing a blueprint Managing a stack post-launch Managing stack automation Managing an impaired server Conceptual - Catalog Conceptual - Stacks and blueprints Conceptual - Marketplace Managing a stack post-launch Manage a stack after launching it from a blueprint. Find an existing stack 1. From the Dell Cloud Manager Dashboard, select Stacks from the main navigation. 2. You will see the full list of stacks you currently have deployed. 3. Click the name of the stack you want to open. 12

13 NOTE: The View Stack Details button will allow you to view the Stack Overview page, where you can further drill down to view Resources, Automation, and History. View stack details and progress 1. From the Dell Cloud Manager Dashboard, select Stacks from the main navigation. 2. From the stacks list, click the name of the stack you want to open. 3. Click the View Stack Details button. 4. Click the Stack Overview tab to view stack details. NOTE: From the Stack Overview page, you can also view stack Resources, Automation, or History by selecting tabs in the left navigation. Manage stack automation If your stack allows automation editing, you can set parameters for autoscaling and autohealing during the origial setup, or adjust after the stack is running. 1. From the Dell Cloud Manager Dashboard, select Stacks from the main navigation. 2. From the stacks list, click the name of the stack you want to open. 3. Click the View Stack Details button. 4. Click the Automation tab in the left navigation to view or edit settings. NOTE: From the Automation page, you can also view stack Resources and History, or return to Stack Overview by selecting tabs in the left navigation. Review stack history 1. From the Dell Cloud Manager Dashboard, select Stacks from the main navigation. 2. From the stacks list, click the name of the stack you want to open. 3. Click the View Stack Details button. 4. Click the History tab in the left navigation to view the list of events relating to the stack. NOTE: From the History page, you can filter based on event name, resource type, event initiator, start/end time, or status. Managing stack automation Managing stacks using commands Managing an impaired server Launching a stack Adding a blueprint Editing a blueprint 13

14 Managing a cloud server Conceptual - Catalog Conceptual - Stacks and blueprints Managing an impaired server If an impaired server is detected during a health check, autohealing will be triggered. Settings may include the choice to restart, replace, or log the affected server. Restart: When you restart a server, you reboot the resource. Replace: When you replace a server, you delete and recreate the resource. Log: When you log a server, no action is taken on the impaired server. The health check failure i.e., the repair event, is logged to help with stack troubleshooting efforts. For additional information on autohealing actions, please see the Blueprint Designer Guide. Managing a stack post-launch Managing stack automation Launching a stack Managing stack automation If your stack allows automation editing, you can set parameters for autoscaling and autohealing during the original configuration, or adjust after launching a stack. View or edit stack automation 1. From the Dell Cloud Manager Dashboard, select Stacks from the main navigation. 2. From the stacks list, click the name of the stack you want to open. 3. Click the View Stack Details button. 4. Click the Automation tab in the left navigation to view or edit settings. NOTE: From the Automation page, you can also view stack Resources and History, or return to Stacks Overview by selecting tabs in the left navigation. Addressing an impaired server Within automation settings, a health check will trigger autohealing if an impaired server is detected. Settings may include the choice to restart, replace, or log the affected server. Restart - When you restart a server, you reboot the resource (only applies to servers). Replace When you replace a server, you delete and recreate the resource. 14

15 Log - When you log a server, it takes no action on the impaired server and logs the health check failure i.e., repair event, to help with stack troubleshooting efforts. For additional information on autohealing actions, please see the Blueprint Designer Guide. Launching a stack Managing a stack post-launch Managing an impaired server Conceptual - Catalog Conceptual - Autoscaling Conceptual - Autohealing Conceptual - Scaling Step Managing stacks using commands If you have permission to create or add a new blueprint to a catalog, you will need to use the Dell Cloud Manager Blueprint Designer Guide. The blueprint designer guide is intended for administrators or application architects responsible for performing the following tasks: Designing service or application blueprints Creating, maintaining, testing and debugging service or application blueprints Once created, these blueprints can be loaded into Dell Cloud Manager, then launched from the Catalog or from commands to provision the infrastructure needed to run your service or application. Some of the command-line functions available in the Blueprint Designer Guide include: Launching stacks Displaying stacks Terminating stacks Managing a cloud server Conceptual - Catalog Conceptual - Stacks and blueprints 15

16 Using Dell Cloud Manager with Microsoft Windows images Dell Cloud Manager can be used to administer both Microsoft Windows and Linux systems. The Windows systems have a longer response time to polling, but otherwise can be managed similarly. Each cloud's behavior with Windows is described below. IMPORTANT: You must first create a firewall that allows inbound RDP connection requests, and use that firewall when launching a Windows virtual machine you want to administer. To configure a Windows virtual machine on Amazon Web Services 1. Log in to Dell Cloud Manager. 2. From Amazon Web Services, select a public Windows image, or use a Windows image from your organization. 3. Launch a server using the Windows image you selected and the RDP firewall you created before launch. Because of the polling and reporting time, it may take up to 20 minutes for the Windows server information to appear in Dell Cloud Manager. 4. Select the newly created server and click View more then the Reveal option to view the administrator password, if available. 5. On your computer, open a Remote Desktop Connection to the server, using username: administrator password: <returned password> To configure a Windows virtual machine on Azure 1. Log in to Dell Cloud Manager. 2. From Azure, select a public Windows image, or use a Windows image from your organization. 3. Launch a server using the Windows image you selected. Dell Cloud Manager automatically opens port for RDP. You cannot use the standard port 3389 on an Azure cloud. NOTE: Because of the polling and reporting time, it may take up to 20 minutes for the Windows server information to appear in Dell Cloud Manager. 4. Select the newly created server and click View more, then the Reveal option to view the administrator password, if available. 5. On your computer, open a Remote Desktop Connection to the server, using the following: username: dasein password: <returned password> port:

17 To configure a Windows virtual machine on Joyent 1. Log in to Dell Cloud Manager. 2. From Joyent, select a public Windows image, or use a Windows image from your organization. 3. Launch a server using the Windows image you selected and the RDP firewall you created before launch. 4. Log in to your external Joyent console to retrieve the username and password of the running instance. In the Joyent console, the username and password will appear under Compute > Instances > <instance name> > Credentials. 5. On your computer, open a Remote Desktop Connection to the server, using: username: <returned username> (typically "administrator") password: <returned password> TIP: To skip the requirement to log in to the Joyent console to retrieve the password, you can create a Windows image that has a preset administrator password. To configure a Windows virtual machine on ScaleMatrix 1. Log in to Dell Cloud Manager. 2. From ScaleMatrix, select a public Windows image, or use a Windows image from your organization. 3. Launch a server using the Windows image you selected. Because of the polling and reporting time, it may take up to 20 minutes for the Windows server information to appear in Dell Cloud Manager. 4. Select the Show Password option from the server if it is available. 5. On your computer, open a Remote Desktop Connection to the server, using username: administrator password: <returned password> Your Amazon cloud There are several parts to optimizing Dell Cloud Manager (DCM) for each of your cloud accounts. Learn more about the different command sets for each cloud in Conceptual - Cross-cloud management. To add an AWS account you already have Collect the following account information: Account number Access key Secret access key AWS certificate AWS private key 17

18 1. To collect the account information: a. Navigate to Security Credentials under your AWS account name. b. Click on Account Identifiers at the bottom to find your AWS Account ID. c. Copy it to a notepad. d. Click on Create New Access Key. Note that AWS allows only two active keypairs. e. Copy the Access Key ID and Secret Access Key. f. Click on X-509 Certificates. g. Download the Private Key File and X.509 Certificate. 2. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 3. Click Connect a Cloud Account. 4. Select Amazon Web Services and click Next: Credentials. 5. Enter the information you gathered from the AWS web console. 6. Click Verify and Finish. To create a new AWS account 1. From the Dell Cloud Manager Home menu, select Connect to a new cloud account from the right side. 2. Select Amazon Web Services. 3. Read and agree to the terms of service. 18

19 4. Click Next: Billing. If you click Do this later, your information will not be saved. 5. Enter your billing information. This information is not passed through to your cloud provider, it is retained in the Dell Cloud Manager system. 6. Click Finish. 7. The account is created on AWS and available when you select Cloud Accounts from the Dell Cloud Manager Administration menu. To configure your AWS account 1. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 2. Select the new cloud account. It will have a blue Dell icon indicating that it is managed by Dell. 3. Select Edit Account Details. Name - Give your new cloud account a more descriptive name. Description - Enter a description for the new cloud account. This is optional. Default Budget - Select a default budget. All cloud accounts must have at least one budget associated with them. More budgets can be added in addition to the default budget. For more information, see Configuring budgeting. 4. Click Update Cloud Account and confirm your changes. 5. Click Edit Account Credentials. NOTE: If you just created this account, you won't see this option since you don't need to change anything. 6. Click Update Credentials. To configure access to your AWS account Currently, the only users with access to this cloud account are those already designated as administrators in the DCM system. To give access to more users, assign the groups that they are in to roles, then assign the roles to particular cloud accounts. Learn more about access control in Conceptual - Users, groups, roles, and access rights. The following is a short overview of the steps to take when setting up one group, role, and user. From the Administration menu, select User Access. To assign roles 1. Select the Roles tab near the top of the page. a. Click Add Role. Name and describe the new role. b. Click Create Role. 2. To change the access permissions, click Edit Access Rights. To assign groups a. Select the access type and whether these users will have full or partial access. b. Click Save Changes. 19

20 1. Select the Groups tab near the top of the page. To assign users a. Click Add Group. Name and describe the new group. b. Click Next: Console Access Settings. These settings allow members of this group to control the console, including reports, budgeting, and access settings. c. Click Next: Role Assignments. For each cloud, select one role for this group. In this example, select your new account. d. Click Next: Budget Assignments. There must be at least one budget assigned to each group. e. Click Create Group. 1. Select the Users tab near the top of the page. a. Click Add User. b. Enter a valid address and password for the user. These values will apply across all clouds. The user will be able to reset their password after their account is created. c. Click Next: Credentials. These settings are optional. You can enter credentials for a user to access virtual machines created from a corporate-controlled image. d. Click Next: User Groups. e. Select the new group that was created and click Add Selected. The user will be added to this group. f. Click Create User. NOTE: Please be aware that AWS has strict naming conventions for snapshots. Amazon's naming conventions for snapshots require extra validation. If your name is rejected, it is probably in use by another resource, or is in the process of being released. For more information, see Amazon's Bucket Restrictions and Limitations documentation. You are now ready to start creating servers, firewalls, snapshots, and all the other resources available on AWS. Adding a cloud network Adding a firewall Adding a load balancer Attaching a cloud server volume Configuring alerts Configuring budgeting Creating a snapshot Deploying a server Launching a stack Managing a cloud account 20

21 Managing storage and backup Using Dell Cloud Manager with Microsoft Windows images Your Azure cloud There are several parts to optimizing Dell Cloud Manager (DCM) for each of your cloud accounts. Learn more about the different command sets for each cloud in Conceptual - Cross-cloud management. To add an Azure account you already have From your command line: 1. Generate an RSA 2048-bit private key. openssl genrsa -out myprivatekey.key Create a new self-signed certificate using the RSA 2048-bit private key. openssl req -x509 -new -key myprivatekey.key -nodes -days 365 -out mycert.pem 3. Export the public certificate in DER format as a.cer file for the Microsoft Azure Management Console openssl x509 -outform der -in mycert.pem -out mycert.cer Now that you have created the Azure credentials, log in to the Microsoft Azure Management Console and upload the certificate (.cer) file you just created. 1. Log in to the Azure Management Console. 2. Select Settings and then Management Certificates. 3. Click Upload a Management Certificate. 4. Browse to your newly-created.cer file. 5. Click OK. Your certificate is now linked to your Azure subscription and account. The next step is to link it to Dell Cloud Manager. NOTE: Currently, you cannot use Dell Cloud Manager to create a new Microsoft Azure account. To connect your Azure account 1. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 2. Click Connect a Cloud Account. 3. Select Azure and click Next: Credentials. 4. Enter the certificate information you created and obtained from the Azure Management Console. 5. Click Verify and Finish. To configure your Azure account 1. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 2. Select your cloud account. 3. Select Edit Account Details. Give your new cloud account a more descriptive name. 21

22 4. Select a default budget. All cloud accounts must have at least one budget associated with them. You can add additional budgets on top of the default budget. For more information, see Configuring budgeting. 5. Click Update Cloud Account and confirm your changes. 6. Click Edit Account Credentials. If you just created this account, you won't see this option since you don't need to change anything. 7. Click Update Cloud Credentials and confirm your changes. To configure access to your Azure account Currently, the only users with access to this cloud account are those already designated as administrators in the DCM system. To give access to more users, assign the groups that they are in to roles, then assign the roles to particular cloud accounts. Learn more about access control in Conceptual - Users, groups, roles, and access rights. The following is a short overview of the steps to take when setting up one group, role, and user. From the Administration menu, select User Access. To assign roles 1. Select the Roles tab near the top of the page. a. Click Add Role. Name and describe the new role. b. Click Create Role. 2. To change the access permissions, click Edit Access Rights. To assign groups a. Select the access type and whether these users will have full or partial access. b. Click Save Changes. 1. Select the Groups tab near the top of the page. To assign users a. Click Add Group. Name and describe the new group. b. Click Next: Console Access Settings. These settings allow members of this group to control the console, including reports, budgeting, and access settings. c. Click Next: Role Assignments. For each cloud, select one role for this group. In this example, select your new account. d. Click Next: Budget Assignments. There must be at least one budget assigned to each group. e. Click Create Group. 1. Select the Users tab near the top of the page. a. Click Add User. b. Enter a valid address and password for the user. These values will apply across all clouds. The user will be able to reset their password after their account is created. c. Click Next: Credentials. 22

23 These settings are optional. You can enter credentials for a user to access virtual machines created from a corporate-controlled image. d. Click Next: User Groups. e. Select the new group that was created and click Add Selected. The user will be added to this group. f. Click Create User. You are now ready to start creating servers, firewalls, snapshots, and all the other resources available on Azure. Azure Requirements Be aware of the following requirements for working with the Azure cloud: Ports Port is automatically opened for RDP on every Windows -based server from Dell Cloud Manager. Port 22 is opened on every Linux -based server launched from Dell Cloud Manager. Usernames The default username for all Azure servers launched from Dell Cloud Manager is "dcmuser." Image preparation To prepare a Linux-based server for imaging, run this command: /usr/sbin/waagent -deprovision+user This removes the username and password to allow the new machine image to have a fresh user. Adding a cloud network Adding a firewall Adding a load balancer Attaching a cloud server volume Configuring alerts Configuring budgeting Creating a snapshot Deploying a server Launching a stack Managing a cloud account Managing storage and backup Using Dell Cloud Manager with Microsoft Windows images 23

24 Your DigitalOcean cloud There are several parts to optimizing Dell Cloud Manager (DCM) for each of your cloud accounts. Learn more about the different command sets for each cloud in Conceptual - Cross-cloud management. To add a DigitalOcean account You will need the following information: Account address OAuth token If you don t have the OAuth token, you can use the following instructions use an existing token or generate a new one. The authentication tokens can be found in the Apps & Auth section of the DigitalOcean control panel for your account ( To connect a DigitalOcean account From the Administration menu, select Cloud Accounts. Click Connect a Cloud Account. Select DigitalOcean and click Next: Credentials. Enter the information you gathered from the Apps & Auth section of the DigitalOcean control panel of your account. Click Verify and Finish. Adding a cloud network Adding a firewall Adding a load balancer Attaching a cloud server volume Configuring alerts Configuring budgeting Creating a snapshot Deploying a server Differences: Digital Ocean Launching a stack Managing a cloud account Managing storage and backup Using Dell Cloud Manager with Microsoft Windows images Your Google Compute Engine cloud 24

25 There are several parts to optimizing Dell Cloud Manager (DCM) for each of your cloud accounts. Learn more about the different command sets for each cloud in Conceptual - Cross-cloud management. To add a GCE account you already have Collect the following account information. Project ID Service account address. Your service account is the long gserviceaccount.com address found on the GCE credentials page. P12 Key Password P12 Key Certificate If you don't have that information, follow these instructions to set up a Google cloud account. You will be enabling GCE to generate an OAuth Account and enable Public API access within the Google Developers Console. 1. To collect account information: a. Navigate to Log in or create an account. b. Navigate to Projects within the Google Developers Console to create a new project. Create a project for use with Dell Cloud Manager (DCM). The name of the project can be anything you choose. c. Once the project is available, navigate to Billing & Settings in your new project and enter a billing method. d. Navigate to APIs & Auth. Select APIs. e. Enable the GCE API. f. After GCE is enabled, navigate to APIs & Auth. Select Credentials. 25

26 g. Select CREATE NEW CLIENT ID. h. Select Service Account and click Create Client ID. i. Your P12 Key Password will be shown to you, and you will need to accept the download to acquire your P12 Key Certificate. 2. From the DCM Administration menu, select Cloud Accounts. 3. Click Connect a Cloud Account. 4. Select Google, then click Next: Credentials. 5. Enter the information you gathered from the Google Developers Console. 6. Click Verify and Finish. To create a new Google account 1. From the DCM Dashboard, click Connect a new cloud account in the right-side section under Shortcuts. 2. Select Google. 3. Read and agree to the terms of service. 4. Click Next: Billing. If you click Do this later, your information will not be saved. 5. Enter your billing information. This information is not passed through to your cloud provider, it is retained by the DCM system. 6. Click Finish. 7. The account is created on Google and will be available when you select Cloud Accounts from the DCM Administration menu. To configure your Google account 1. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 2. Select the new cloud account. It will have a blue Dell icon indicating that it is managed by Dell. 3. Select Edit Account Details. Name - Give your new cloud account a more descriptive name. Description - Enter a description for the new cloud account. This is optional. Default Budget - Select a default budget. All cloud accounts must have at least one budget associated with them. More budgets can be added in addition to the default budget. For more information, see Configuring budgeting. 4. Click Update Cloud Account and confirm your changes. 5. Click Edit Account Credentials. NOTE: If you just created this account, you won't see this option since you don't need to change anything. 6. Click Update Credentials. To configure access to your Google account Currently, the only users with access to this cloud account are those already designated as 26

27 administrators in the DCM system. To give access to more users, assign the groups that they are in to roles, then assign the roles to particular cloud accounts. Learn more about access control in Conceptual - Users, groups, roles, and access rights. The following is a short overview of the steps to take when setting up one group, role, and user. From the Administration menu, select User Access. To assign roles 1. Select the Roles tab near the top of the page. a. Click Add Role. Name and describe the new role. b. Click Create Role. 2. To change the access permissions, click Edit Access Rights. To assign groups a. Select the access type and whether these users will have full or partial access. b. Click Save Changes. 1. Select the Groups tab near the top of the page. To assign users a. Click Add Group. Name and describe the new group. b. Click Next: Console Access Settings. These settings allow members of this group to control the console, including reports, budgeting, and access settings. c. Click Next: Role Assignments. For each cloud, select one role for this group. In this example, select your new account. d. Click Next: Budget Assignments. There must be at least one budget assigned to each group. e. Click Create Group. 1. Select the Users tab near the top of the page. a. Click Add User. b. Enter a valid address and password for the user. These values will apply across all clouds. The user will be able to reset their password after their account is created. c. Click Next: Credentials. These settings are optional. You can enter credentials for a user to access virtual machines created from a corporate-controlled image. d. Click Next: User Groups. e. Select the new group that was created and click Add Selected. The user will be added to this group. f. Click Create User. You are now ready to start creating servers, firewalls, snapshots, and all the other resources available on Google Compute Engine. Google Compute Engine requirements 27

28 Be aware of the following requirements for working with the GCE cloud: Naming conventions GCE has unusually tight naming conventions for resources e.g., servers, volumes, and networks. DCM notifies a user in the event of an invalid name and will provide inline guidance. GCE resource names must comply with the following naming conventions: Must be 64 characters or less consisting only of: lowercase letters numbers hyphens The first character must be a letter. No uppercase letters, spaces, or other special characters. Instance SSH access When you launch a server from Dell Cloud Manager, you can specify an SSH key. Before you can use SSH access, you must open the SSH port (22) on the network you selected at server launch. You may open the port in the Firewalls management panel. Find the firewall for your GCE network and add a rule for TCP port 22 (if one does not already exist). Once you add the rule, you do not need to add it again for servers launched in the same network. Automatic server volume deletion In the GCE console and API, servers have a parameter to control whether their root volume is automatically deleted when the server is terminated. This can be set at launch time, or at any time while a server is running. DCM does NOT expose or respect this flag. All GCE servers will have their root device deleted when terminated through DCM. This is consistent with the behavior of most other clouds. To preserve a server's disk, create a snapshot before terminating the server. Adding a cloud network Adding a firewall Adding a load balancer Deploying a server Launching a stack Attaching a cloud server volume Configuring alerts Configuring budgeting Creating a snapshot Managing storage and backup Using Dell Cloud Manager with Microsoft Windows images 28

29 Your Joyent Cloud There are several parts to optimizing Dell Cloud Manager (DCM) for each of your cloud accounts. Learn more about the different command sets for each cloud in Conceptual - Cross-cloud management. To add a Joyent account you already have Collect the following account information: Account username Account password SSH Key ID (or Key Name) SSH Private Key (contents of the id_rsa file) 1. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 2. Click Connect a Cloud Account. 3. Select Joyent Cloud and click Next: Credentials. 4. Enter the Joyent information you gathered. 5. Click Verify and Finish. To create a new Joyent Cloud account 1. From the Dell Cloud Manager Home menu, select Connect to a new cloud account from the right side. 2. Select Joyent Cloud. 3. Read and agree to the terms of service. 4. Click Next: Billing. If you click Do this later, your information will not be saved. 5. Enter your billing information. This information is not passed through to your cloud provider, it is retained by the Dell Cloud Manager system. 6. Click Finish. 7. The account is created and is available when you select Cloud Accounts from the Dell Cloud Manager Administration menu. To configure your Joyent account 1. From the Dell Cloud Manager Administration menu, select Cloud Accounts. 2. Select the new cloud account. It will have a blue Dell icon indicating that it is managed by Dell. 3. Select Edit Account Details. Name - Give your new cloud account a more descriptive name. Description - Enter a description for the new cloud account. This is optional. Default Budget - Select a default budget. All cloud accounts must have at least one budget associated with them. More budgets can be added in addition to the default budget. For more information, see Configuring budgeting. 4. Click Update Cloud Account and confirm your changes. 29

30 5. Click Edit Account Credentials. NOTE: If you just created this account, you won't see this option since you don't need to change anything. 6. Click Update Credentials. To configure access to your Joyent account Currently, the only users with access to this cloud account are those already designated as administrators in the DCM system. To give access to more users, assign the groups that they are in to roles, then assign the roles to particular cloud accounts. Learn more about access control in Conceptual - Users, groups, roles, and access rights. The following is a short overview of the steps to take when setting up one group, role, and user. From the Administration menu, select User Access. To assign roles 1. Select the Roles tab near the top of the page. a. Click Add Role. Name and describe the new role. b. Click Create Role. 2. To change the access permissions, click Edit Access Rights. To assign groups a. Select the access type and whether these users will have full or partial access. b. Click Save Changes. 1. Select the Groups tab near the top of the page. To assign users a. Click Add Group. Name and describe the new group. b. Click Next: Console Access Settings. These settings allow members of this group to control the console, including reports, budgeting, and access settings. c. Click Next: Role Assignments. For each cloud, select one role for this group. In this example, select your new account. d. Click Next: Budget Assignments. There must be at least one budget assigned to each group. e. Click Create Group. 1. Select the Users tab near the top of the page. a. Click Add User. b. Enter a valid address and password for the user. These values will apply across all clouds. The user will be able to reset their password after their account is created. c. Click Next: Credentials. These settings are optional. You can enter credentials for a user to access virtual machines created from a corporate-controlled image. d. Click Next: User Groups. 30

31 e. Select the new group that was created and click Add Selected. The user will be added to this group. f. Click Create User. You are now ready to start creating servers, firewalls, snapshots, and all the other resources available on AWS. Joyent requirements Be aware of the following differences in configuring and using a Joyent account with Dell Cloud Manager. Passwords Joyent does not return passwords in their API. Because of this, Dell Cloud Manager cannot display the password in the console. To log into a Windows virtual machine hosted on Joyent 1. Launch the server from Dell Cloud Manager as usual. 2. Log into your Joyent account to retrieve the password to the server. SSH keys You cannot add SSH keys from Dell Cloud Manager because the API does not allow that. To add an SSH key to Joyent 1. Log in to the Joyent console. 2. Upload your SSH key. 3. Wait for Dell Cloud Manager to discover the key. The length of this wait can vary. 4. Launch the Linux virtual machine from Dell Cloud Manager using the newly-discovered SSH key. The virtual machine can then be managed with Dell Cloud Manager as usual. Firewalls Firewalls are not currently supported on Joyent clouds. Pricing Joyent has a complicated pricing system that depends on the size of your servers and the license they are operating on. Joyent server pricing/hour: Joyent machineimage pricing/hour: Because Joyent does not pass through information on which combination is being used,dell Cloud Manager assumes the highest price point in the available range for calculating reports and estimated charges. Adding a cloud network 31

32 Adding a firewall Adding a load balancer Deploying a server Launching a stack Attaching a cloud server volume Configuring alerts Configuring budgeting Creating a snapshot Managing storage and backup Using Dell Cloud Manager with Microsoft Windows images Adding a ScaleMatrix cloud account To add your ScaleMatrix account, you need the following information: Account name User name Password To connect a ScaleMatrix account 1. Log in to the Dell Cloud Manager. 2. From the Administration menu, select Cloud Accounts. 3. Click Connect a Cloud Account. 4. Select ScaleMatrix, then click Next: Credentials. 5. Enter the required information and click Verify and Finish. Your credentials are now linked to Dell Cloud Manager (DCM). IMPORTANT: DCM does not support launching servers with a DHCP-based network. Adding a cloud account Managing a cloud account Concepts To make working with Dell Cloud Manager easier, get to know the following terms and topics. Conceptual - Agent Conceptual - API keys 32

33 Conceptual - Autohealing Conceptual - Autoscaling Conceptual - Budgets Conceptual - Catalog Conceptual - Cooldown Period Conceptual - Cross-cloud management Conceptual - Dasein Conceptual - Docker Conceptual - Evaluation Period Conceptual - Filtering users, groups, roles, or clouds Conceptual - LDAP Conceptual - Marketplace Conceptual - Public API Conceptual - Resources Conceptual - Scaling Step Conceptual - Stacks and blueprints Conceptual - Threshold Conceptual - Users, groups, roles, and access rights Conceptual - Agent The Dell Cloud Manager Agent (DCM Agent) expands the capabilities of Dell Cloud Manager (DCM) by empowering virtual machines (VMs) to do all of the following and more: Mount and format volumes Add and remove users at any time Install and configure custom services Centralize logging Server health monitoring The DCM Agent is a lightweight service that runs inside of a VM. When the VM is booted and the DCM Agent starts, it forms a secure communication channel back to DCM. Commands are sent to the DCM Agent along this channel. From simple tasks like adding and removing users on a single VM, to the coordination of multiple VMs in a distributed cloud application, the DCM Agent adds to the power of DCM. 33

34 In this architecture, DCM becomes the conductor and every VM with a configured DCM Agent provides power for whatever needs to be orchestrated. With infrastructure cloud computing, each VM can be quite powerful and the total number of VMs is practically limitless. The challenge is coordinating all of these pieces to perform in unison. DCM and the DCM Agent provide the instrument to make this possible. Installing the Linux Agent Installing the Windows Agent Conceptual - API keys An application programming interface (API) key is an identifier that allows applications to identify themselves to an API so that the API responds with only the set of information and data that the key is authorized to access. The data is then used by the application. The API Secret key is used to authenticate each API request via special API request signature that is computed for each request. For full information on configuring your application to communicate with the Dell Cloud Manager API, see Dell Cloud Manager API Documentation. 34

35 Creating API keys Managing API keys Conceptual - Autohealing If an impaired server is detected during a health check, autohealing will be triggered. Settings may include the choice to restart, replace, or log the affected server. Restart: When you restart a server, you reboot the resource (only applies to servers). Replace: When you replace a server, you delete and recreate the resource. Log: When you log a server, it takes no action on the impaired server and logs the health check failure i.e., repair event, to help with stack troubleshooting efforts. For additional information on autohealing actions, please see the Blueprint Designer Guide. Managing stack automation Launching a stack Conceptual - Autoscaling Conceptual - Autoscaling Autoscaling helps maintain application availability by adding and removing servers according to CPU load, evaluation period, and scaling step. NOTE: To disable autoscaling, a user can set minimum and maximum instances to the same number. Managing stack automation Launching a stack Conceptual - Autohealing Conceptual - Budgets Budgets are an important part of monitoring your cloud usage. Dell Cloud Manager provides you with estimates about your usage and fees. We also allow you to configure notifications to alert you when you are approaching or exceeding your spending thresholds. NOTE: The cloud usage features in Dell Cloud Manager are estimates based on information we gather from the cloud provider. This is not a legally binding amount, and you should always use your own judgment to avoid spending excesses. 35

36 Soft quota A soft quota is a limit that you configure so that you are aware that you are approaching your spending threshold. It gives you an opportunity to modify your spending pattern or your quota based on the amount you have already used. Hard quota A hard quota is the upper limit of your spending threshold. After you reach hard quota, you will not be able to add any resources to the account, because doing so would mean that you were spending even more money. However, to prevent data loss and business disruption, Dell Cloud Manager does NOT terminate any resources you already have running, even after you reach your hard budget limit. You will not incur any new fees, but you will be notified that you have exceeded your set budget threshold and no new resources can be added. Run-time budgets A run-time budget is a feature that allows you to see what your spending rate is for a month. Even before you reach your soft quota, a run-time budget can allow you to see that you are on track to exceed it and allow you to take corrective measures. You can view your month-to-date spending in the Current Usage column of your budget. Budget access Budgets are set at the group/account access level. Each group in an account can have one or more budget codes. One budget code can be used by many groups, and group-account pairs can have multiple budget codes. For more information on access, see Configuring budget access. Configuring alerts Configuring budgeting Configuring budget access Conceptual - Catalog A catalog is a collection of blueprints. You may have access to either your own company catalog or the Dell Cloud Marketplace catalog, or both. The Catalog section is located in the main navigation of the Dell Cloud Manager Dashboard. Launching a stack Managing a stack post-launch Adding a blueprint Conceptual - Marketplace 36

37 Conceptual - Cooldown Period After a scale up or scale down scenario, a Cooldown Period ensures that the system will wait a set period of time before performing another autoscaling action. Managing stack automation Launching a stack Conceptual - Cross-cloud management Dell Cloud Manager (DCM) uses a powerful, open source abstraction layer called Dasein Cloud. Dasein abstracts the different behaviors and capabilities of each cloud. This allows DCM to discover and control each cloud in a consistent way. It allows you to manage your cloud resources from a single dashboard and API, without needing to know many of the technical and conceptual differences between clouds. Each cloud supports different features and behaves in a different way. Through Dasein, DCM discovers these differences. Suppose Cloud A supports load balancers but Cloud B does not. DCM will automatically discover this, and will then show you load balancer management actions for Cloud A but not Cloud B. Likewise, Cloud A may require several steps and several pieces of information in order to launch a server, while Cloud B requires something different. Dasein and DCM abstract this process and present you with a single launching point, along with fields to allow you to select and provide required information for the cloud you have chosen. Adding a Configuration Manager Account Cloud differences Compare clouds Configuring Configuration Management Accounts Managing a cloud account Managing a cloud network Managing a cloud server Requirements for the Dell Cloud Manager Conceptual - Dasein Dasein (pronounced "da z-eye-n") is a Java-based cloud abstraction layer that enables programmers to build applications under a "write-once, run against any cloud" philosophy. It provides an abstract model under which most IaaS and some PaaS services can be modeled. Developers write applications to the Dasein Cloud model and it is then translated into the underlying cloud provider model. For example, applications that need to communicate with Amazon Web Services and Google Compute Engine need to utilize two completely different Application Programming Interfaces (APIs). Using Dasein, an 37

38 application would only need to communicate with a single API. More information about Dasein can be found at: Dasein Open Source Software. Conceptual - Cross-cloud management Compare clouds Cloud differences Conceptual - Docker Docker is a system that organizes an application into a standard container with standard inputs and outputs. There are official Docker repositories such as Wordpress, MongoDB, MySQL, Ubuntu and Node.js. There are also thousands of dockerized applications created by organizations to meet their specific needs. Because Docker deployments are so easy to standardize, it's a useful way for companies to create their own base images. Launching a Docker container Launching a stack Conceptual - Stacks and blueprints Configuring Configuration Management Accounts Managing a cloud network Managing a stack post-launch Conceptual - Evaluation Period Within automation settings, an evaluation period specifies a number of consecutive measurement periods where threshold has to be breached. Note: The duration needs to be measured as an average within a specific time period as loads could temporarily spike, while overall utilization could still be low. Managing stack automation Launching a stack Conceptual - Filtering users, groups, roles, or clouds The filtering system in Dell Cloud Manager is responsive. As you enter text in the box, the resources returned will change. This saves you from having to page through dozens of resources looking for just the right one. Enter the unique part of the resource name, even if it is not the beginning of the resource name. For example, if you have a resource named AWS23, you don't need to enter AWS, just 23, and because it is 38

39 more unique, you will see a very limited list of returned resources. If there are no resources that fit your parameters, the return area will remain empty. Use the filter options to further refine your return results or to get a list of all the resources that meet a certain set of parameters. For example, if you cannot remember the name of a particular cloud account, but you remember that it was on Joyent and it had been running a month, you could use the Running for... and In this cloud... filters to narrow down the list until you recognize the name. This filtering system works similarly for all types of items, but the filter options for each type of resource will be different. Adding a user Adding a blueprint Conceptual - Users, groups, roles, and access rights Conceptual - LDAP DCM (DCM) can leverage Lightweight Directory Access Protocol (LDAP) or Active Directory (AD) as an authoritative source of user data for an organization. DCM can synchronize its internal directory with a subset of groups and users within LDAP or AD. For example, when an organization adds a user to its LDAP-based directory and that user is in one of the synchronized groups, DCM will discover the user and add that user and the user's group memberships to DCM. The LDAP accounts are synchronized with DCM on a daily basis by default. If a user is removed from the LDAP directory, DCM will remove the user access and group membership in the DCM directory as well. Users can be categorized into two different groups for the directory synchronization process: Admin Group: Only one group in LDAP/AD is allowed per customer for granting DCM users administrator access. Users belonging to this group will have administrator access to all the accounts in DCM for a particular organization. Standard/Non-Admin Groups: Multiple groups of this type in LDAP/AD are allowed per customer. Users belonging to these standard groups can be granted limited/controlled access to selective accounts in DCM for a particular organization. Managing users and accounts Conceptual - Public API Dell Cloud Manager provides a public-facing API that allows you to programmatically manage your cloud or multi-cloud environments. The features exposed in the API are almost all replicated in the dashboard, but when you are dealing with high volumes of servers and application stacks, or many instances, it may be faster to use the API. Conceptual - API keys Launching a stack 39

40 Adding a blueprint Conceptual - Marketplace Dell Cloud Marketplace provides a catalog of curated blueprints. Once you launch a blueprint, it runs as a stack. You will be responsible for all security updates and ongoing management. New blueprints are added to Marketplace as they are created and certified. If your organization has access to Marketplace, you can currently choose from two types of blueprints: Server blueprints that launch a base operating system into your cloud of choice. Application blueprints that launch Docker-based applications into your cloud of choice. Dell Cloud Marketplace provides some verified containers from the Marketplace Docker selection. You can also select any container from the Docker hub. However, the containers from Docker hub have not been validated by Dell and may contain malicious or unwanted applications. NOTE Before you launch a blueprint, you must have an existing cloud account. Adding a cloud account Launching a stack Adding a blueprint Conceptual - Catalog Conceptual - Stacks and blueprints Conceptual - Docker Conceptual - Resources Resources is a way to refer to all the things that can be administered with Dell Cloud Manager (DCM). A resource is anything that has its own control settings. So a server or a firewall would be referred to as a resource, but an application that is installed on a server is not controlled by DCM and therefore, will not be referred to as a resource. Attaching a volume to a server Deploying a server Managing a cloud network Managing a cloud server Managing firewalls Managing load balancers Managing machine images Managing snapshots Managing volumes 40

41 Conceptual - Scaling Step Within automation settings, a scaling step allows you to choose how many instances to increase or decrease each member of the scaling group in combination with threshold and evaluation period parameters. Managing stack automation Launching a stack Managing a stack post-launch Conceptual - Stacks and blueprints A stack is a collection of software, platform, and infrastructure components that work together to support a process. You can create a stack by launching a blueprint from a catalog. For example, to serve a Wordpress site, you need a Wordpress installation, PHP, MySQL, and a web server. You may also want other customized options to build and deploy. Instead of assembling and installing each of those requirements on each server, you can create or use a blueprint that already has all the requirements, with the suggested patches, in one place. NOTE: Thoroughly check any images you plan to use for production purposes. Not all publicly-distributed blueprints are free of malicious software. If you have permissions to create or add a new blueprint to a catalog, you will need to use the Dell Cloud Manager Blueprint Designer Guide. Launching a stack Adding a blueprint Managing stack automation Managing a stack post-launch Conceptual - Threshold Within automation settings, the threshold can be set to meet cost or performance preferences. To manage costs A user might set the scale-down threshold higher than the original setting in the blueprint so the stack will scale down sooner. To boost performance A user might set the scale-up threshold lower than the original setting in the blueprint so the stack will scale up sooner. Managing stack automation 41

42 Launching a stack Conceptual - Users, groups, roles, and access rights User access is controlled by the group to which a user belongs and the roles assigned to that group. 42

43 Figure 1: Relationship between users, groups, roles, and access rights 43