Download to read offline
![Clint Byrum < [email_address] >](https://image.slidesharecdn.com/ensembleoscon2011-110728195232-phpapp01/85/Ensemble-oscon-2011-2-320.jpg)
Uploaded byOSCON Byrum
Ensemble oscon 2011
Ensemble is a service orchestration tool that couples provisioning and configuration to deploy and manage distributed applications and services. It uses "formulas" written in YAML to define relationships between components. Formulas are simple to write and review. Ensemble makes assumptions explicit rather than burying them in code or configuration. It provides a way to declaratively model and manage complex, interdependent systems.
More Related Content
![[Container X mas Party with flexy] Machine Learning Lifecycle with Kubeflow o...](https://cdn.slidesharecdn.com/ss_thumbnails/20181218kubeflowazurepublic-181218060359-thumbnail.jpg?width=640&height=640&fit=bounds)
![Cloud init and cloud provisioning [openstack summit vancouver]](https://cdn.slidesharecdn.com/ss_thumbnails/cloud-initandcloudprovisioningopenstacksummitvancouverwip-160517225244-thumbnail.jpg?width=640&height=640&fit=bounds)
![Chef in the cloud [dbccg]](https://cdn.slidesharecdn.com/ss_thumbnails/chefinthecloud-dbccg-100927223008-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Ensemble oscon 2011
- 1. Ensemble – Welcometo Service Orchestration OSCON 2011
- 2. Clint Byrum <[email_address] >
- 3.
- 4.
- 5. DevOps Distilled ™- Isn't that config management? Config Management Machine Centric
- 6.
- 7. Knowledge Sharing InvolvesCustomization and assumptions.
- 8. Analog: ./configure &&make && sudo make install Service Orchestration Service Centric
- 9.
- 10. Designed for KnowledgeSharing
- 11. Complimentary to configmanagement
- 12.
- 13. The Cloud http://www.flickr.com/photos/gsbrown99/2706179635/sizes/o/in/photostream/http://www.flickr.com/photos/kaptainkobold/5892507537/sizes/z/in/photostream/ http://www.flickr.com/photos/stevendepolo/4226949238/sizes/l/in/photostream/ http://www.flickr.com/photos/emsl/4929154481/sizes/l/in/photostream/
- 14.
Editor's Notes
- #3 * Developers write their code thinking of services, not machines. * De-coupled meaning that w/ config management, you say ”give me a machine, and then configure it this way”, where as with coupling you say ”Give me a service configured this way, and put it on these machines” * Loose coupling with a two way comm channel lets us write formulas without having to assume anything about related services.. we can learn the answers from the other service's configuration. * ./configure && make && make install is more powerful for custom work, but packaging gives you the benefits of repeatability and portability
- #4 * Ensemble is mostly about using IaaS * EC2 only right now – This includes Eucalyptus and OpenStack * Deploy fast, add new infrastructure fast, and repeat over and over. * Pay for what you use * Invest in infrastructure only when it makes sense for YOU
- #5 * Open source makes it easy to solve your problems without having to appropriate and get locked in to software with a purchase. * Utility computing is similar.. running things on computers doesn't necessarily mean you need to own computers. * Currently marrying the two, opensource and ”the cloud”, is a fairly manual or custom operation.
- #6 * Deploys existing open source solutions fast - ”apt-get for the cloud” * Also deploys YOUR app fast. * Makes it easy to define how your application relates to existing opensource services. * Helps you manage those relationships in ”The cloud” * Tightly integrated with Ubuntu – A leader in the cloud space.
- #7 Some yaml metadata – lists relationships that it understands and config options A few scripts that run at the right time – configure service based on relationships and config settings Well encapsulated – MySQL formula is generic, and usable by any application that can speak to MySQL
- #8 * Wikipedia's architecture has a lot of relationships * Adding 100 of each type isn't hard anymore – thank you config management. * Getting them to work together is still a challenge.
- #9 * demo-wiki PHP layer and memcached both scale out with 'add-unit' (can scale back with remove-unit). * Eventually this will be presentable not as commands in serial, but a ”stack” which will be loaded into the environment, and dumpable from a running system
- #10 * These commands add a slave instance, and relate it to the master * They also tell the demo-wiki service to use it as a slave * add-unit wiki-slave-db would provide even more read scale out * Write scaling is a bit more tricky * Adding slaves gets us to the subset of the wikipedia graph above.. still lots of relationships to define
- #11 Generated by ensemble's ”dot” output format
- #12 * There are some options that are unknowable, like the wiki's name * config-changed hook is executed every time a config is actually changed, not every time 'ensemble set' is called.