Continuous Delivery for DC/OS with Spinnaker Will Gorman @willgorman
Deploying software is challenging
Why continuous delivery? • Decrease risks of deployment • Decrease cost of deployment • Decrease delay between feature development and availability
Deployments should be: • Safe • Automated • Flexible
Safety features • Unit tests • Sandbox deployments • Smoke tests • Zero downtime deployments • Rolling/canary deployments
Automation • Automation is an enabler of safety • Define and test the parts of deployments that aren’t often performed • Deploy smaller changes more frequently
Deployment Strategies
Flexible • Many teams with similar needs, but some variation • Engineers naturally want to automate • Make it easy to share and reuse
How?
Introducing Spinnaker The open-source, multi-cloud, continuous delivery tool
Continuous Delivery Features • Pipelines from commit to production • CI builds • Image baking • Deployment strategies • Validation • Promotion across environments
Multi-cloud
Multi-cloud • Spinnaker is multi-cloud but not a pure abstraction
Spinnaker Concepts Applications, Clusters, Server Groups, and Instances
Applications and Clusters Application Clusters
Server Groups and Instances
Marathon applications and tasks
Create New Server Group
Create New Server Group
Multi-Region Deployments
Pipelines
Triggers
Docker Registry Trigger
DC/OS Stages Supported Pipeline Stages • Server Groups • Check preconditions • Create • Deploy • Resize • Destroy Server Group • Clone • Disable Cluster • Destroy • Find Image from Cluster • Jenkins, Manual Judgement, Pipeline, • Resize Server Group, Run Job, Scale Down Cluster, Script, Shrink Cluster, Wait
Deploy
Destroy Server Group
Run Job Execute a Metronome job as a step in a pipeline. Write JSON or property file output to the Mesos sandbox to create context for later steps
Pipeline Expressions • Spring Expression Language • Works almost anywhere • Generate attributes of pipelines at run-time • Evaluate to test for pipeline branching conditions
Pipeline Expressions
Deployment Safeguards
Execution Windows
Execution Windows
Traffic Guards
Chaos Monkey
Spinnaker Patterns for DC/OS
Deployment timeouts
Incremental Automation • Problem: Not everything in our release process is completely automated yet
Manual Judgment to Rollback
Configuration Change Triggers Problem: Spinnaker pipeline configuration isn’t the primary source for our application configuration Prefer configuration to be stored in version control or generated to reduce duplication across applications
Configuration Change Triggers
Load Balancer • Problem: Marathon-LB doesn’t support Spinnaker load balancer operations
Load Balancer marathon-lb marathon-lb marathon-lb X /demo/foo-v000 /demo/foo-v000 /demo/foo-v000 /demo/foo-v002 /demo/foo-v002 /demo/foo-v002 HAPROXY_0_VHOST: HAPROXY_0_VHOST: HAPROXY_0_VHOST: HAPROXY_0_VHOST: HAPROXY_0_VHOST: HAPROXY_0_VHOST: foo.example.com foo.example.com foo.example.com foo.example.com foo.example.com foo.example.com
Traefik Source: https://traefik.io/
Traefik Traefik /demo/foo-v000 /demo/foo-v001 HAPROXY_0_VHOST: HAPROXY_0_VHOST: foo.example.com foo.example.com traefik.backend: traefik.backend: foo foo
Load Balancer • Problem: Traefik still discovers routing rules through labels, which can’t change after an instance is started • Solution – DC/OS 1.10 programmable Edge-LB package (beta)
Enterprise and Open Source DC/OS • Only supports DC/OS Enterprise authentication methods currently • DC/OS Open Source works with authentication disabled
Thanks! • https://www.spinnaker.io/ • Slack: https://join.spinnaker.io • http://careers.cerner.com • http://engineering.cerner.com
Recommend
More recommend
