Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Deployment to the Cloud using Spinnaker - JavaDay 2017

Fbcb461e8c19ccc6727f13dbfcd58362?s=47 Andreas Evers
November 04, 2017

Continuous Deployment to the Cloud using Spinnaker - JavaDay 2017

In our quest to get to production faster, we’ve tackled culture, architecture and infrastructure: organizing ourselves in cross-functional DevOps teams, embracing microservice architectures, and deploying to the various clouds out there. Along the way we’ve learned some best practices about how to deploy software at velocity — things like automated releases, immutable infrastructure, gradual rollouts and fast rollbacks.

Back in 2014, Netflix started building Spinnaker, an open-source multi-cloud continuous delivery platform that embodied these core principles of safe, frequent and reliable releases. In June Spinnaker 1.0 was released, with core contributions from Google, Microsoft, Oracle and Pivotal to name a few.

Built on Spring Boot, its architecture is surprisingly familiar. During this session we’ll give you a tour of how Spinnaker works, how we are using it at our clients, as well as what it could do for your continuous delivery pipeline.

Fbcb461e8c19ccc6727f13dbfcd58362?s=128

Andreas Evers

November 04, 2017
Tweet

More Decks by Andreas Evers

Other Decks in Technology

Transcript

  1. Continuous Deployment to the Cloud using Spinnaker

  2. None
  3. EMBRACING DevOps CULTURE & PRACTICES

  4. ADOPTING MICROSERVICE Architectures

  5. Moving to CLOUD Infrastructure

  6. Lessons Learned

  7. Deployment Frequency Exploded

  8. Cloud Deployments are Complex Change Change Change Change SVC 1

    SVC 2 SVC 3 Provider A Zone X Provider B Zone Y Provider C Zone Z
  9. Easy Rollbacks are Important

  10. Deploy during the Right Timeframes

  11. CD Principles

  12. Immutable Infrastructure • We want the process of building, testing,

    deploying and validating to be as deterministic as possible • We want repeatability and predictability across environments • Through baking images or building containers
  13. Deployment Strategies

  14. Automation

  15. Operational Integration DEPLOY OPERATE

  16. Enter Spinnaker

  17. None
  18. None
  19. Container Engine App Engine Compute Engine

  20. Internal Structure

  21. Orca Front50 Spring Boot in the core Gate Clouddriver Rosco

    Fiat Deck Echo Igor Halyard
  22. Useful Features

  23. Planning

  24. Planning

  25. Chaos Monkeys

  26. Canary Analysis

  27. Difference with Terraform / CloudFormation Spinnaker strengths lie in it’s

    ability to orchestrate deployment workflows using infrastructure. Terraform [& CloudFormation] shine at the management of cloud primitives. -- Brandon Leach, Lookout
  28. Halyard • Configuration & deployment lifecycle management tool • Install,

    upgrade, configure, validate your Spinnaker installation • Works with Bill of Materials (BOM)
  29. Coming up • Canary strategy • Rolling blue green strategy

    • Declarative CD – config as code • Operational monitoring for Spinnaker
  30. None
  31. Demo

  32. Demo 35.195.58.178 http://bit.do/javaday

  33. T witter: twitter.com/andreasevers T ech blog: ordina-jworks.github.io spinnakerteam.slack.com tag:spinnaker spinnaker.io