Open stack heat for RAs
1 like1,195 views
This document discusses establishing common reference architectures and operational practices for OpenStack deployments to promote interoperability, prevent vendor lock-in, and facilitate collaboration. It proposes creating standardized reference architectures ("flavors") that define hardware and software configurations. It also suggests upstreaming common operational scripts and using OpenStack Heat for orchestration to help ensure different OpenStack clouds can work together. The document advocates for these approaches to make it easier to deploy, manage, and test multiple compatible OpenStack clouds.
Open stack heat for RAs
- 1. Sharing OpenStack Reference Architectures Using OpenStack Orchestration (aka Heat) as a RA baseline Discussion by OpenStack Board Members: Monty Taylor Rob Hirschfeld
- 2. OpenStack + Common Ops... Multiple Interoperable OpenStack Clouds ● Prevents vendor lock-in ● Establishes best practices ● Provides basis for sharing ● Scales OpenStack Ecosystem Panel Today @ 5:20 Room A107-A109
- 3. What is the problem? Everyone does OpenStack differently! We share code, but it takes a lot more to run a cloud. Small differences in hardware, versioning, and implementation ● breaks portability ● limits collaboration ● hampers support Software Hardware Ops
- 4. Why solve it? OpenStack sites as fault zones Interoperability is valuable If we can't deploy OpenStack consistently, we can't test OpenStack If we can't compare deployments, we cannot help or validate OpenStack http://www.vibrant.com/
- 5. Open Operations Collaborating directly on operations code Extends Reference Architectures ● Sharing the "what" ● Enabling environment-specific config ● Your deploy isn't that different ○ Cows and Cats - cows are still snowflakes! ● Helps new users know what works ● Streamlines addressing vulnerabilities http://www.fitchicago.com/heart%20surgery%203.jpg
- 6. Upstreaming Ops If we can agree on a physical configuration AND on the code to install then... Shouldn't we also be able to collaborate on the installation scripts? That would make it easier to interoperate!
- 7. What is an RA? Resident Advisor? :) Rich Aunt? B) Reference Architecture :P Reference Implementation? ● Generally hardware focused ● Physical layout and wiring ● Defines logical operations and interconnections ● Recommends components ● May include configuration guidance ● May also discuss performance Not likely to include HA config, upgrades or operation http://jeffjonas.typepad.com/RubeGoldberg.bmp
- 8. RefStack Https://github.com/openstack-ops/refstack (currently empty) ● One or More RA's ● Defined in OpenStack terms ● Mechanism for testing against an RA ● Vendor neutral & vendor accessible ● Intended as best practices (not only way)
- 9. Flavors of RA We don't know all of them, but need to limit number! What matters in a favor? ● networking? ● hypervisor? ● scale? ● workload? http://blogs.laweekly. com/squidink/2011/11/5_best_ice_cream_sh ops_los_angeles.php
- 10. Flavors Requirement Two OpenStack clouds of the same flavor should be able to interoperate! Operators using similar favors should be able to share scripts and processes There should be as few flavors as possible. Flavor should be cited in bugs
- 11. Flavor Table ??? Function Hypervisor Networking Scale Mixed Use ? ? ? Compute ? ? ? Storage ? ? ? ? Mix and discuss....
- 12. What is Heat? ● Makefile for a Cloud Application ● OpenStack Orchestration ● Coordinates OpenStack API calls ● Provides Metadata to Resources Express a multi-node application ○ Nodes + Relationships + Personas + Order http://www.piratemerch. com/assets/images/images/jolly_roger_hotsa uce.jpg
- 13. Heat Orchestration ● In service dependency order, heat: ○ Provisions node ○ Provides JSON config metadata ○ Runs config-change trigger ○ Reports success/collected node information chef/ohai/puppet can read JSON config ... Write recipes/modules to expect standard input parameters
- 14. Interoperability = Nirvana Interop is a Major Focus for Foundation Panel on Tuesday @ 5:20 Room A107-A109 Interoperability is a sustaining process it is not an release feature ● shared reference architectures -> refstack ● open operations -> upstreamed DevOps ● comprehensive test -> CI & API tests ● community participation -> you!