Skip to content

Latest commit

 

History

History
336 lines (274 loc) · 12 KB

slides.md

File metadata and controls

336 lines (274 loc) · 12 KB
Raw

**To Start** - Create a DC/OS test cluster at https://portal.azure.com/ **get $250 ** - mail to [email protected]

!SLIDE


**Slides**[http://nauts.io/workshop-azure-container-services](http://nauts.io/workshop-azure-container-services)

!SLIDE

Azure Container Service DC/OS

![ACS](img/acs.png)

!SUB

Mesos

creates a single Operating System Kernel spanning all machines.

![Mesos](img/mesos.png)

!SUB

Marathon

the init system of Mesos. It will make sure that you will keep your applications running.

![Mesos](img/marathon.png)

!SUB

mesos-dns

provides DNS based service discovery of deployed applications.

![Mesos](img/marathon-dns.png)

!SUB

marathon-lb

provides routing and load balancing functionality to deployed applications.

![Mesos](img/marathon-lb.png)

!SUB

Chronos

the cron subsystem of Mesos. It will allow you to periodically execute jobs.

![Mesos](img/chronos.jpeg)

!SLIDE

Hands-on

  • generic instruction, try to solve it yourself
  • are you stuck? press 's' and check the presenter notes for typing instructions

Prerequisites

  • Microsoft Azure trial account > 20 cores quote
  • Docker Machine installed
  • putty / ssh-agent installed

!SLIDE

The hands-on scene

This is your end result today!

![DC/OS on ACS](img/dcos-test-deployment-apps.png)

!SUB

paas monitor application

A web application that continuously calls a backend service. Each instance of the deployed service that responds results in an new row. instances that have been killed, will remain in the table until a refresh. The environment variables 'RELEASE' and 'MESSAGE' can be set to mimick new application releases.

![paas-monitor on DC/OS](img/paas-monitor-full.png)

!SUB

shellinabox application

A web application that gives access to an interactive shell. the environment variables 'SIAB_USER' and 'SIAB_PASSWORD' allow you to set the username and password with which you can log in. network utilities have been installed so that you can do DNS lookups.

![paas-monitor on DC/OS](img/shellinabox.png)

!SUB

xip.io

xip.io is a magic domain name that provides wildcard DNS for any IP address. Say your agents public IP address is 52.123.12.45 than you can use the names 'paas-monitor.52.123.12.45.xip.io' and 'shell.42.123.12.45.xip.io' to point to your IP address. These names can be used to direct the HTTP traffic to the correct application through the marathon-lb.

!SLIDE

Hands-on

  • local applications
    • paas-monitor
    • shellinabox
  • Setup a Azure Container Service
    • Install marathon-lb package
    • Deploy paas-monitor
    • Rolling upgrade paas-monitor
    • Service discovery
    • Deploy ASP.net Core application
    • Scaling

!SLIDE

Local paas-monitor application

paas-monitor is a small docker application that allows you to see the effect of rolling upgrades, scaling, failures etc. the environment variables 'RELEASE' and 'MESSAGE' can be used to mimick new application releases.

** Assignment : ** run the docker image mvanholsteijn/paas-monitor:latest on your local machine and point your browser to it. what do you see? what happens if you stop the paas-monitor?

![DC/OS on ACS](img/paas-monitor.png)

!NOTE

  • docker-machine create -d virtualbox dev
  • eval $(docker-machine env dev)
  • docker run -d --publish :1337:1337 --env "RELEASE=v1" --env "MESSAGE=hello from docker machine." mvanholsteijn/paas-monitor:latest
  • open http:$(echo $DOCKER_HOST |cut -d: -f2):1337
  • docker stop $(docker ps -ql)

!SLIDE

Local shellinabox application

shellinabox provides a shell with a web interface so you can safely snoop around on a machine. The environment variables 'SIAB_USER' and 'SIAB_PASSWORD' allow you to set the username and password with which you can log in. The environment variable 'SIAB_SSL' controls encrytion by the shell.

** Assignment : ** run the docker image [mvanholsteijn/shellinabox:latest](https://github.com/mvanholsteijn/shellinabox-container) on your local machine and point your browser to it. disable SSL and specify a username and password. Login through the web interface and look around.

!NOTE

  • docker run -d --publish :4200:4200 -e SIAB_SSL=false -e SIAB_USER=guest -e SIAB_PASSWORD=password -e SIAB_SUDO=true mvanholsteijn/shellinabox:latest
  • open http:$(echo $DOCKER_HOST |cut -d: -f2):4200
  • docker stop $(docker ps -ql)

!SLIDE

Deploy ACS - DC/OS

** Assignment : ** goto the [Azure Portal](https://portal.azure.com/) and create a DC/OS test cluster

![DC/OS on ACS](img/azure-create.png)

!NOTE

  • goto Azure Portal,
  • Click New
  • Search 'Azure Container Service (test cluster with DC/OS)'
  • Click Create
  • Do a basic configuration in West Europe See Deploy an ACS Cluster for full details.

!SUB

Connect to ACS - DC/OS

** Assignment: ** Point your browser to the DC/OS console via an SSH tunnel to your mesos master machine at <username>@<dns-prefix>mgmt.westeurope.cloudapp.azure.com. the diagram below shows you the deployment diagram of your cluster. The public DNS names is your configured prefix postfixed with mgmt.westeurope.cloudapp.azure.com and agents.westeurope.cloudapp.azure.com for the management and agent machines respectively.

![DC/OS on ACS](img/dcos-test-deployment.png)

!NOTE

  • sudo ssh -p 2200 -i $HOME/.ssh/id_rsa -N -L 80:localhost:80 <cuser>@<dns-prefix>mgmt.westeurope.cloudapp.azure.com -
  • on windows with putty: plink.exe -P 2200 -N -L 80:localhost:80 <cuser>@<dns-prefix>mgmt.westeurope.cloudapp.azure.com -
  • open http://localhost

See Connect to ACS cluster for full details.

!SUB

Explore the Console

** Assignment: ** Explore the DC/OS consoles: http://localhost, http://localhost/marathon and http://localhost/mesos. How many machines can you find in the cluster? How much resources does Mesos have available in total?

![DC/OS Console](img/dcos-console.png)

!SLIDE

Install the marathon loadbalancer

** Assignment: ** On the console, goto the DC/OS Universe and install the marathon-lb with 0.5 cpu and 256Mb memory.

![DC/OS Console](img/marathon-lb-install.png)

!NOTE

  • Click on Universe
  • Search marathon-lb
  • Click 'Advanced Installation'
  • Set cpus to 0.5
  • Set memory to 256
  • Click review and install.

!SLIDE

Deploy the paas-monitor

** Assignment: ** Deploy the paas-monitor docker application using [marathon UI](http://localhost/marathon) configured to handle requests for http://paas-monitor.<public-ip-agent-lb>.xip.io. with 0.25 cpu, 128 mb memory. Add a health check on /status with reasonable timeout for a fast application. point your browser at the deployed application and scale up and scale down using the console.

![DC/OS Console](img/marathon-ui.png)

!NOTE

  • goto http://localhost/marathon
  • set Id to 'paas-monitor'
  • set CPUs, Memory, Disk and Instances to 0.24, 128, 0 and 1 respectively
  • set Docker Container to 'mvanholsteijn/paas-monitor:latest'
  • set Network to 'BRIDGE'
  • set Container Port to 1337
  • set Environment variables RELEASE=v2 and MESSAGE=hello azure
  • set label HAPROXY_GROUP to external
  • set label HAPROXY_0_VHOST to paas-monitor.<public-ip-agent>.xip.io
  • set Health Check Path to /health with a grace = 30s, interval = 10s and timeout = 2s
  • Your json should look something like this marathon task definition definition

to scale up use the console

  • goto http://localhost/marathon
  • select 'paas-monitor'
  • Click 'Scale Application'
  • Increase / decrease and watch the effect in your browser

!SUB

Upgrading the application

** Assignment: ** Change the paas-monitor configuration environment variable RELEASE to v2.1. Redeploy this version and watch the behaviour of the application in the browser and in the marathon ui. What strategy does marathon take?

![DC/OS Console](img/marathon-ui.png)

!SUB

Rolling upgrade

Marathon provides different [upgradeStrategies](https://mesosphere.github.io/marathon/docs/rest-api.html).

** Assignment: ** Configure the application to do a rolling upgrade of instances to RELEASE=v3. Watch the behaviour of the application in the browser and in the marathon ui. How does this compare to the previous upgrade?

!NOTE Editing upgrade strategies is no part of the UI yet. Use JSON mode to insert the definition.

  • goto http://localhost/marathon
  • select 'paas-monitor'
  • Click 'Edit' dcos-agent-private-4D3DE637-vmss0
  • Click 'JSON Mode'
  • Change "RELEASE" value to "v3"
  • Paste the following text into the definition:
  ,"upgradeStrategy": { "minimumHealthCapacity": 1.0, "maximumOverCapacity": 0.0 }

!SLIDE

Service Discovery - mesos-dns

marathon-dns has registered A and SRV DNS records for paas-monitor. See [marathon-dns service naming](https://mesosphere.github.io/mesos-dns/docs/naming.html) for dtetails.

** Assignment: ** Deploy the shellinabox and use dig to find the DNS A and SRV records for paas-monitor.

!NOTE

  • goto http://localhost/marathon
  • Add application
  • set Id to 'shell'
  • set CPUs, Memory, Disk and Instances to 0.25, 128, 0 and 1 respectively
  • set Docker Container to 'mvanholsteijn/shellinabox:latest'
  • set Network to 'BRIDGE'
  • set Container Port to 4200
  • set env SIAB_SSL to false
  • set env SIAB_USER
  • set env SIAB_PASSWORD
  • set label HAPROXY_GROUP to external
  • set label HAPROXY_0_VHOST shell.<public-ip-agent>.xip.io
  • set Health Check Path to / with a grace = 30s, interval = 10s and timeout = 2s
  • Your json should look something like this marathon task definition definition
  • point your browser at http://shell.&lt;public-ip-agent>.xip.io and login with $SIAB_USER and $SIAB_PASSWORD
  • type: dig paas-monitor.marathon.mesos
  • type: dig _paas-monitor._tcp.marathon.mesos SRV

!SLIDE

Scaling machines

Marathon will automatically reschedule applications when machines go down.

** Assignment: ** Scale the public virtual machine scaling set to 2 and the private to 5. How many resources does Mesos now report? scale the number of marathon-lb instances to 2. Scale the number of paas-monitor instances to 10. Perform a shutdown of a machine in the private scaling set. How fast does it recover?

Advanced topic: We did not get to this either :-)

!NOTE Scaling the VMSS is pretty difficult..

  • goto https://github.com/.../201-vmss-scale-existing
  • Click on 'Deploy to Azure'
  • Fill in the name of the private scaling set 'dcos-agent-private-<magic-number>-vmss0' and scale to 5
  • Repeat the procedure for the public scaling set 'dcos-agent-public-<magic-number>-vmss0' and scale to 2
  • scale the paas-monitor to 10 instances
  • reduce the private scaling set 'dcos-agent-private-<magic-number>-vmss0' to 2 instances
  • reduce the public scaling set 'dcos-agent-private-<magic-number>-vmss0' to 1 instance

!SLIDE