orchestration across multiple cloud platforms using heat
TRANSCRIPT
- 1. Orchestration across multiple Cloud platforms using HEAT Saba, 20/05/2015
- 2. About Myself Rathinasabapathy (Saba) Co-founder, Solutions Architect, Cloudenablers [email protected] Has over 17+ years of experience in Software Industry. Heads Cloud lab and defines technology direction and Strategy in Cloudenablers.
- 3. Agenda HEAT Introduction Multi Cloud Orchestration Workflow TOSCA Heat Features Supporting Multi Cloud Orchestration Heat Architecture Resource Plugin Structure Standalone Heat deployment Context Centralized template repository with indexing and search New features in Kilo Release
- 4. Heat Introduction 4 Heat provides a mechanism for Orchestrating Openstack resources through the use of modular templates It provides advanced functionality such as instance high availability, instance auto scaling, Software deployment and nested stacks
- 5. Evolution of Heat 5 Havana Native template language (HOT) Concurrent resource operations Improved support to Networking, Ceilometer, Keystone trust Update/Suspend/resume Stack Icehouse Support for all native Openstack resources Software Configurations Autoscaling resources Notifications and File inclusions Stack abandon/adopt/preview Juno Recovery from failures during stack updates API to cancel and roll back an in -progress stack update Remember the previously-supplied parameters when updating a stack Improved scalability Improved visibility into trees of nested stacks Kilo Improved scaling using nested stacks oslo versioned objects Multi region stacks Stack lifecycle scheduler hints Software-config improvements
- 6. Heat Stack Creation 6 HOT Openstack End User Heat-Engine Heat-API Heat-API- CFN Stack VM VM CFN VS Keystone Authentication
- 7. Multi Cloud Orchestration using Heat 7 HOT End User Heat-Engine Heat-API Heat-API- CFN CFN TOSCA HEAT Translator AWS Stack VM VS VPS Cloud Brokerage Gogrid Cloudsig ma Openstack Stack VM VS Cloudcen tral Internap Interoute KS
- 8. TOSCA - Topology and Orchestration Specification for Cloud Applications 8 TOSCA specification provides a language to describe service components and their relationships using a service topology TOSCA enhances the portability and management of cloud applications and services across their lifecycle Enables Smoother migration of existing applications to the cloud Enables dynamic, multi-cloud provider applications Flexible bursting (consumer choice) TOSCA is OASIS Standard
- 9. TOSCA - Topology and Orchestration Specification for Cloud Applications 9
- 10. Multi Cloud Orchestration using Heat - Demo 10 Centralized Template Library with meta data Indexing and Search of Templates Scope and Access definition for Templates Support for multiple cloud platforms (AWS, vCenter, Cloud Brokerage) HEAT is used as Orchestration Engine
- 11. Heat features supporting Multi Cloud Orchestration 11 Heat Architecture Heat Resource Plugin Structure Standalone Heat Deployment Context in Template
- 12. HEAT - Architecture 12 Heat Engine HEAT APIHEAT CLI HORIZON Heat Engine Keystone Nova Glance Neutron Cinder Trove Ceilometer Swift Sahara Resources Functions Parameters Templates Parser Sahara Contrib Stack/ Template VM VM DB CFN/Signal AMQP Watcher Task Scaling
- 13. HEAT Resource Plugin Architecture 13 Heat-Engine Resource BaseClass Create Properties Attributes Update Properties Attributes Delete Properties Attributes Suspend Properties Attributes Resume Properties Attributes Life cycle of a resource Heat Engine Contrib Keystone Docker Gnochii Mistral Zaqar Rackspace Server DNS Network LB Resources
- 14. HEAT Resource Plugin Mapping 14 Example Resource Mapping: def resource_mapping(): 'Computenext::Workload::Instance': Instance, 'Computenext::Workload::Workload': Workload 'Computenext::Workload::Volume': Volume, Computenext::Workload::VolumeAttachment': VolumeAttachment, Computenext::Workload::SecurityGroup': SecurityGroup, 'CAWS::EC2::Instance': Instance, 'CAWS::EC2::Instance': Volume, 'CAWS::EC2::SecurityGroup': SecurityGroup,
- 15. Stand Alone Heat 15 Executing HOT templates to remote/public install of OpenStack through local install of heat Setup environment
- 16. Stand Alone Heat 16 Change Heat.Conf to support multi Cloud
- 17. Stand Alone Heat 17
- 18. Stand Alone Heat 18
- 19. Context in Heat 19 OS::Heat::Stack A Resource representing a stack which can be created using specified context
- 20. Demo 20
- 21. Centralized template repository with indexing and search 21 Templates Meta Data Content HEAT MySQL Solr HEAT API Indexing Bridge Create, List Solr API Stack Meta Data Content Event Template Library Execute
- 22. Advantages of Centralized Template Library 22 Ease of access with scope for Templates Advanced Full Text Search Search based on substring Faceted Search Search both raw template and stack output parameters Search stack across multiple Openstack
- 23. References 23 https://wiki.openstack.org/wiki/Heat/Blueprints/Multi_Regi on_Support_for_Heat https://github.com/openstack/heat-translator https://wiki.openstack.org/wiki/Heat/htr
- 24. Q & A 24
- 25. Thank You 25 Connect with me@ Email: [email protected] LinkedIn: http://in.linkedin.com/in/arsabapathy Twitter: https://twitter.com/arsabapathy For details visit our booth # T-19
- 26. Annexure 26
- 27. HEAT Key New features in KILO Release 27 Functions : Digest Repeat Contributed Resources : Mistral Gnocchi Alarms Keystone Features: Multi Region Stacks Oslo Versioned Objects Improved scaling using nested stacks
- 28. Digest 28
- 29. Repeat 29