1 / 13

INTRODUCTION

BEST PRACTICES FOR INTEGRATING A THIRD PARTY PORTAL WITH OPENSTACK Campbell McNeill – Lead Architect @ campbellmcneill 16 th April 2013 @ Havana Design Summit. INTRODUCTION. We have Horizon, why would we need anything else? What does it take to build a platform for a service provider?

analu
Download Presentation

INTRODUCTION

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BEST PRACTICES FOR INTEGRATING A THIRD PARTY PORTAL WITH OPENSTACKCampbell McNeill – Lead Architect@campbellmcneill16th April 2013 @ Havana Design Summit Confidential

  2. INTRODUCTION • We have Horizon, why would we need anything else? • What does it take to build a platform for a service provider? • How do we focus on user experience around OpenStack? • OpenStack blueprint opportunities

  3. WE HAVE HORIZON, WHY DO WE NEED SOMETHING ELSE? • Horizon is a consumption Portal • It allows the consumption of resources but in terms of being an IT infrastructure it doesn’t provide the integration required for enterprise management • Leaves OpenStack as an island in the enterprise • Gapped in terms of service provider requirements • Management of consumption is gapped • Operational tooling is missing

  4. NIST CLOUD REFERENCE ARCHITECTURE

  5. NIST CLOUD REFERENCE ARCHITECTURE (Cont.)

  6. EXAMPLE OPENSTACK SERVICE PROVIDER ARCHITECTURE

  7. EXAMPLE OPENSTACK SERVICE PROVIDER ARCHITECTURE

  8. SERVICES DECOMPOSED

  9. EXAMPLE OPENSTACK ENTERPRISE ARCHITECTURE

  10. EXAMPLE OPENSTACK ENTERPRISE ARCHITECTURE

  11. SERVICES DECOMPOSED

  12. USER EXPERIENCE CONSIDERATIONS • Consumption Operations • OpenStack (and RESTful) APIs can be chatty • Build extensions to provide shortcuts for common operations • Leverage caching under shortcuts for performance increase • Supporting consumption • Provided as transparent cost management as possible • Leverage automation for customer facing tasks such as onboarding and service modification • Simplify user experience around common interactions

  13. DISCUSSION / LINKS • Campbell McNeill • me@campbellmcneill.com • @campbellmcneill • Federation and oAuth • http://bit.ly/17w63jH • http://bit.ly/154h8sy • NIST Cloud Reference Architecture • http://1.usa.gov/10W097V • Dell • http://www.dell.com/OpenStack • https://cloudconsole.dell.com/Online/Signup/Products

More Related