Containerization—A Journey

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

© 2015 Mesosphere, Inc. meBay.com 4 • enabling people to sell and buy stuﬀ online • supports holding auctions as well as special sales events for selected retailers • allows buying and selling via online chat rooms

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

© 2016 Mesosphere, Inc. All Rights Reserved. ARCHITECTURE 7 • frontend hosts (Web servers and load balancers) • middleware host, running the RoR app server is • backend hosts are the database servers (MySQL) • two environments (prod, as above and dev with one host per tier and smaller sized machines)

Slide 8

Slide 8 text

© 2016 Mesosphere, Inc. All Rights Reserved. AGILITY & CHALLENGES 8 • rolling out a new version of the monolith • sustain load/scaling • local/dev/test reproducibility • getting paged at 3am when things go belly-up

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

© 2016 Mesosphere, Inc. All Rights Reserved. ARCHITECTURE 11 • containerized each component (CI/CD pipeline that generates Docker images) • manually sshing into hosts, using docker run to (re)launch containers • manual, static mapping of containers-to-IP:port

Slide 12

Slide 12 text

© 2016 Mesosphere, Inc. All Rights Reserved. AGILITY & CHALLENGES 12 • effectively using pets approach • better reproducibility • faster roll-outs • still many operational issues (failures, scaling, etc.)

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

© 2016 Mesosphere, Inc. All Rights Reserved. ARCHITECTURE 15 • turned the monolith into microservices • only cattle • automatic handling of failures • auto-scaling depending on trafﬁc • canary and blue-green deployments

Slide 16

Slide 16 text

Slide 17

Slide 17 text

© 2016 Mesosphere, Inc. All Rights Reserved. CONTAINERS  17 • don't apply 'VM patterns' • they come and go (implications for monitoring, etc.) • fully automated CI/CD pipeline is essential • usually higher utilization but requires a fair part of automation • needs appops (later more)

Slide 18

Slide 18 text

© 2016 Mesosphere, Inc. All Rights Reserved. REGISTRIES 18 • Docker Hub  https://hub.docker.com/ • Google Cloud  https://cloud.google.com/tools/container-registry/ • AWS  https://aws.amazon.com/ecr/ • CoreOS  https://quay.io/ • SUSE Portus  http://port.us.org/ • JFrog Artifactory  https://www.jfrog.com/artifactory/ • Run your own  https://docs.docker.com/registry/deploying/

Slide 19

Slide 19 text

© 2016 Mesosphere, Inc. All Rights Reserved. SECRETS 19 Don't bake credentials into images but rather do: $ docker run -d -e API_TOKEN=SECRET somedatabase $ docker run -d -v $(pwd):/fsecret:/fsecret:ro somedatabase Even better: use key-value in-memory stores such as Square's KeyWhiz, HashiCorp's Vault, or Crypt or native solutions