Skip to content

Latest commit

 

History

History
53 lines (45 loc) · 5.77 KB

README.md

File metadata and controls

53 lines (45 loc) · 5.77 KB
Raw

Microsoft Azure

This section walks you through step-by-step on how to provision compute resources on Azure that will be used to form a DC/OS environment. A DC/OS environment consists of 'master' nodes that administer the DC/OS environment and schedule work to run on agents, 'private agent' nodes that have perform work and 'public agent' nodes that are accessable via the public internet. The # of masters, # of private & public agents will vary depending on your performance & scalability requirements. The diagram below and used throughout this documentation illustrates DC/OS environment that has 3 master, 30 private agent & 3 public agent nodes. Microsoft Azure has the ability to provision a set compute resources using an 'Azure Template'. This repo provides an 'Azure Template' that is used to provision master & agent compute resources.

Compute resources provisioned for a 3 master, 30 private agent & 3 public agent DC/OS environnment:

Pre-requisites:

Pre-requisite 1: Establish an Azure Account. If you are new or don't have credentials you can sign-up for Azure here and try it out.

Pre-requisite 2: Establish a SSH Key Pair to securely communicate with compute resources.

Provision compute resources on Microsoft Azure

Step 1: The easiest way to provision compute resources on Microsoft Azure is to make use of an 'Azure Template'. Opening the DC/OS Azure Template will prompt you to login to your Azure Portal using your credentials. note: In case you are interested, the configuration of the Azure Template can be found here.


Step 2: With the 'dcos' Azure template open, click the 'Deploy' button and fill in the parameters as follows:

  • Subscription: Choose the Azure subscription you want to use for your compute resources, PS GEOEVENT DEV AZ.
  • Resource Group: Choose 'Create new' and give your resource group a name, e.g. adamdcos4.
  • Location: choose the Azure region you wish to deploy your compute resources to, e.g. West US.
  • Username & Public Key: to get the username & public key view the contents of your SSH Key Pair public file:     
  • Username: the username can be found towards the end of the public key file in front of the @ character, e.g. cory6458.
  • Public Key: copy and past the contents of the .pub file paying close attention not to include any leading or trailing whitespace.
  • Num Masters: the number of Mesos master compute resources you wish to provision, e.g. 1.
  • Master Size: the Linux Virtual Machine size you wish to provision for master nodes, e.g. Standard_DS3_V2 (4 vCPU, 14 GiB memory).
  • Num Agents: the number of Mesos private agent compute resources you wish to provision, e.g. 5.
  • Agent Size: the Linux Virtual Machine size you wish to provision for private agent nodes, e.g. Standard_DS4_V2 (8 vCPU, 28 GiB memory).
  • Agent Disk Size GB: the additional disk to add to each agent in GB (10 to 1023), e.g. 1023.
  • Num Public Agents: the number of Mesos public agent compute resources you wish to provision, e.g. 1.
  • Public Agent Size: the Linux Virtual Machine size you wish to provision for public agent nodes, e.g. Standard_DS3_V2 (4 vCPU, 14 GiB memory).
  • Scroll Down and review the 'Terms and Conditions' and if you agree check the 'I agree' checkbox.


Step 3: Click the 'Purchase' button to start provisioning your compute resources on Azure. You will be returned back to main portal dashboard screen where you can see in the notification area one deployment occurring.


Step 4: Click on the 'Resource Groups' icon on the left hand menu (second item down) and click on the name of the resource group you are deploying.


Step 5: Your 'Resource Group' will likely still be in a status of 'Deploying' for around 3-4 minutes.


Step 6: Wait until another notification appears saying 'Deployment succeeded' and then hit the 'Refresh' button.


Step 7: Click on the 'Type' column to sort by type of resource. We can see each of the virtual machines created, e.g. m1 = master1, a1/a2/a3 = agent1/2/3, p1 = public agent 1


Step 8: Click on the 'Public IP address' of the boot node to get information on how to connect to it. Take note of the 'IP address', e.g. 40.78.18.217. We will connect to the boot node via ssh to orchestrate the installation of DC/OS in a subsequent step.


Step 9: Click on the 'Public IP address' of the public master node to get information on how to connect to it. Take note of the 'DNA name', adamdcos04dcos.westus.cloudapp.azure.com and 'IP address', e.g. 40.78.23.14. We will connect to the master agent node via a web browser to access the DC/OS administrative and Mesos dashboards once we've successfully completed the installation in a subsequent step.



Congratulations: You now have compute resources in place on Microsoft Azure that can be used to Install DC/OS.