Federation of OpenStack clouds
•Download as PPSX, PDF•
1 like•3,768 views
The document discusses federation of OpenStack clouds, which allows different cloud services from various providers to be accessed under a single platform. It describes different approaches to cloud federation including provider/enterprise hybrid clouds and marketplace-based models. It then discusses how OpenStack enables cloud federation through features like identity federation using Keystone, federated orchestration using Heat, and cascading OpenStack installations. Specific use cases presented include a federated marketplace bringing together multiple providers.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (9)
Similar to Federation of OpenStack clouds
Similar to Federation of OpenStack clouds (20)
More from CoreStack
More from CoreStack (12)
Recently uploaded
Recently uploaded (20)
Federation of OpenStack clouds
- 1. Federation of OpenStack Clouds Satyabrata Chowdhury, 19/05/2015
- 2. About Myself Satyabrata Chowdhury Solutions Architect, Cloudenablers Satya.c@cloudenablers.com I work with the CTO organization on Technology evangelization, defining strategy and roadmap for Cloud products and programs.
- 3. Agenda • Cloud Federation • Different Approaches to Cloud Federation • OpenStack-Enabling Cloud Federation • Use Cases: Federated Marketplaces • Q & A
- 5. Cloud Federation Cloud Federation is the concept of bringing different services offered by various Providers under a single platform . 5 CSP 1 CSP 2 CSP 3End User • Capacity Utilization • Inter-operability • Catalog of Services • Insight about providers and SLA’s
- 6. Driving factors for cloud federation 6 Choice of Providers Mix and Match of Services Going local Heterogeneity of Platforms Ability to scale Movement and Migration of Workloads
- 7. Different Approaches to Cloud Federation 7
- 8. Provider/Enterprise Centric-Hybrid Clouds 8 Self Service Portals User • Hybrid Approach- (Public+Private) • Helps in scaling and migrating gradually to different clouds or locations • Suitable for specific enterprises and Cloud service providers >> Cloud 1 Cloud 3 Cloud 2
- 9. Marketplace based Federation Model 9 User Provider A Provider B Cloud Federation Cloud Marketplace Federation Engine Cloud Service Cloud Service • Search , selects and compare the offers/services. • Create and Provision workloads across providers. • Consolidated usage data and billing across providers. • Platform agnostic model. • Flexible – Workload movement and migration across providers. • Choice of providers and offers. • Creates competitive environment that leads to innovation.
- 11. Use Case 1-Identity Federation 11
- 12. 12 Identity Federation Mechanism to establish trust between identity providers and multiple OpenStack clouds enabling users to access resources across multiple cloud endpoints with a single credential without having to provision additional identities for each providers. Service Provider Service Provider Identity Provider Identity Provider
- 13. Federated Identity using Keystone 13 User Identity Provider KeyStone (Service Provider) OpenStack 1 Request Initiation SAMLAuthRequest 23 4 Validated Service Consumption 5
- 14. Keystone to Keystone Federation 14 User KeyStone1 OpenStack1 KeyStone2 OpenStack2 IDP1 IDP2 SAML Assertion Request SAML Assertion Response
- 15. Use Case 2-Federated Orchestration 15
- 16. Federated Cloud Orchestrator 16 Ability to Provision and migrate workloads across providers seamlessly to achieve portability and inter-operability User VM Load Balancer Monitoring/ Management Backup/DR Federation Engine Marketplace/Self-service portal Provider 1 Provider 2 Provider 3 Queue
- 17. Multi Cloud Orchestration using Heat 17 User Marketplace/ Self-Service Portal OpenStack2 OpenStack1 HeatWorkload Templates • Standalone Heat engine serving as a Orchestration layer in Federation engine. • Service Catalogs stored as HOT templates. • Portability can be achieved through TOSCA compliant templates. TOSCA: Topology and Orchestration Specification for Cloud Applications
- 18. Use Case 3-Usage tracking and Image Management 18
- 20. Use Cases: Federated Marketplaces 20
- 23. 23 Computenext(Global Cloud Marketplace) • 60+ Providers • 28+ Countries • 40+ Cities
- 24. 24 Services from different providers grouped together as a single workload Add-on managed services offered in a marketplace. Computenext(Global Cloud Marketplace)..contd
- 25. References • https://wiki.openstack.org/wiki/OpenStack_cascading_solution • https://aws.amazon.com/marketplace/ • http://www.ibm.com/marketplace/cloud/us/en-us/ • http://allthingsfederated.com/ --- Dr. Munirathnam Srikanth, CTO ,Computenext Inc • http://marketplac.computenext.com • https://github.com/stackforge/tricircle • https://blueprints.launchpad.net/keystone/+spec/keystone-to-keystone-federation • Introduction to openstack cascading solution by Chaoyi Huang & Hongning Wu at Huwei 25
- 26. Q & A 26
- 27. Other Interesting sessions 27 Session Date Time Speaker Location Extending Horizon for Multi-cloud Management 19/05/2015 4:40PM Krishna Kumar N. 121/122 CoreStack – Orchestration Simplified 19/05/2015 05:15 PM Venkatesh Perumal / RathinaSabapathy A Demo Theatre Orchestration Across multi cloud platforms using Heat 20/05/2015 3:30PM Rathina Sabapathy A. 121/122
- 28. Thank You 28 Connect with me@ Email: Satya.C@cloudenablers.com LinkedIn: http://in.linkedin.com/in/satyachowdhury For the next three days visit me at Booth # T-19
Editor's Notes
- Paret OpenStack exposed externally. All other OpenStack set-ups works like different Availability zones. Glance: Replicate images across all OpenStacks while image is uploaded using “repli-manager”. Ceilometer: Usage data is stored in individual OpenStack set-ups. The data is collected on-demand through “Ceilometer-proxy” when the user requests.