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.
11. 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/building images
22. Halyard
• Configuration & deployment lifecycle management tool
• Install, upgrade, configure, validate your Spinnaker installation
• Works with Bill of Materials (BOM)
27. Difference with
Terraform / CloudFormation
Spinnaker’s strengths lay in its ability to orchestrate
deployment workflows with infrastructure.
Terraform [& CloudFormation] shine at the management of
cloud primitives.
-- Brandon Leach, Lookout
28. Coming up
• Canary strategy
• Rolling blue green strategy
• Declarative CD – config as code
• Operational monitoring for Spinnaker
