Orchestration? You Don't Need Orchestration. What You Want Is Choreography by Julian Dunn, Chef
Download as PPTX, PDF1 like716 views
The document discusses the concepts of orchestration and choreography in systems management, emphasizing the differences between ordered operations across machines and autonomous actors making promises about behavior. It introduces Habitat as a tool for application automation that features portable packages and built-in configuration, and advocates for building systems that prioritize choreography. The conclusion encourages the development of management systems that are fleet-aware rather than node-aware.
Orchestration? You Don't Need Orchestration. What You Want Is Choreography by Julian Dunn, Chef
- 1. Don’t Orchestrate, Choreograph! Julian Dunn Product Manager, Chef
- 3. An ordered set of operations Across a set of independent machines Connected to an orchestrator only via a network.
- 5. Humans acting on Visio acting on machines Humans acting on code acting on machines
- 6. An ordered set of operations Defined in code Across a set of independent machines Connected to an orchestrator only via a network.
- 8. tasks: - name: remove host from LB shell: /usr/local/bin/remove_host {{ ansible_hostname }} delegate_to: loadbalancer.example.com - name: deploy code git: repo=http://github.com/foo/bar.git dest=/var/www/html/ notify: - restart apache - name: add host to LB shell: /usr/local/bin/add_host {{ ansible_hostname }} delegate_to: loadbalancer.example.com
- 12. Failure: Hard to Recover From
- 13. Orchestrator is a SPOF
- 15. Mark Burgess: Promise Theory
- 17. “You Will Feed My Cat”
- 18. “Do You Promise To Feed My Cat?”
- 19. “Obligations are far from being a reliable tool for ensuring compliance. If a law- giver wanted to ensure the compliance of an agent, a better strategy would be to obtain a promise from the agent and to convince it to view the intention as a commitment since the law-giver could never know whether the agent had indeed committed to the body of the obligation.” - Bergstra & Burgess, “A Static Theory of Promises”
- 20. Trying to make promises about the behavior of the other nodes
- 21. Autonomous Actors that: • Make progress towards promised desired state • Expose interfaces to allow others to verify promises • Can promise to take certain behaviors in the face of failure of others What is Choreography?
- 23. Introducing Habitat • Application automation with the app • Portable, immutable packages • Masterless architecture • Built-in runtime configuration • Built-in service discovery • Built-in security • Exports to Docker containers • Fully open-source https://www.habitat.sh/
- 24. Conclusions Don’t build or choose things requiring orchestration Build choreography into systems Make management systems fleet-aware, not node-aware
- 25. Thank you!
Editor's Notes
- #9: LOL the Chef guy shows some Ansible