Open Stack Open Source Cloud Software Open Stack

  • Slides: 25
Download presentation
Open. Stack Open Source Cloud Software

Open. Stack Open Source Cloud Software

Open. Stack: The Mission "To produce the ubiquitous Open Source cloud computing platform that

Open. Stack: The Mission "To produce the ubiquitous Open Source cloud computing platform that will meet the needs of public and private cloud providers regardless of size, by being simple to implement and massively scalable. "

Open. Stack Founding Principles Apache 2. 0 license (OSI), open development process l. Open

Open. Stack Founding Principles Apache 2. 0 license (OSI), open development process l. Open design process, 2 x year public Design Summits l. Publicly available open source code repository l. Open community processes documented and transparent l. Commitment to drive and adopt open standards l. Modular design for deployment flexibility via APIs l

Community with Broad Commercial Support

Community with Broad Commercial Support

Software to provision virtual machines on standard hardware at massive scale Open. Stack Compute

Software to provision virtual machines on standard hardware at massive scale Open. Stack Compute creating open source software to build public and private clouds Software to reliably store billions of objects distributed across standard hardware Open. Stack Object Storage

Open. Stack Release Schedule Diablo: September 22 Cactus: April 15, 2011 Followed by conference

Open. Stack Release Schedule Diablo: September 22 Cactus: April 15, 2011 Followed by conference and design summit in Boston in early October l Bexar: February 3, 2011 Open. Stack Compute ready for large service provider scale deployments l. This is the ‘Rackspace-ready’ release; need to communicate Rackspace support and plans for deployment l Open. Stack Compute ready for enterprise private cloud deployments and mid-size service provider deployments l. Enhanced documentation l. Easier to install and deploy l

Open. Stack Cloud Architecture Compute

Open. Stack Cloud Architecture Compute

Open. Stack Compute Key Features Re. ST-based API Asynchronous eventually consistent communication Horizontally and

Open. Stack Compute Key Features Re. ST-based API Asynchronous eventually consistent communication Horizontally and massively scalable Hypervisor agnostic: support for Xen , Xen. Server, Hyper-V, KVM, UML and ESX is coming Hardware agnostic: standard hardware, RAID not required

Public Network Server Groups Dual Quad Core RAID 10 Drives 1 Gig. E Public

Public Network Server Groups Dual Quad Core RAID 10 Drives 1 Gig. E Public 1 Gig. E Private 1 Gig. E Management Example Open. Stack Compute Hardware (other models possible) Private Network (intra data center)

User Manager Cloud Controllers: Global state of system, talks to LDAP, Open. Stack Object

User Manager Cloud Controllers: Global state of system, talks to LDAP, Open. Stack Object Storage, and compute/storage/networkers through a queue ATAo. E / i. SCSI API: Receives HTTP requests, converts commands to/from API format, and sends requests to cloud controller Host Machines: workers that spawn instances Open. Stack Compute Glance: HTTP + Open. Stack Object Storage for server images

System Components API Server: Interface module for command control requests l. Designed to be

System Components API Server: Interface module for command control requests l. Designed to be modular to support multiple APIs l. In current release: Open. Stack API, EC 2 Compatibility Module l. Approved blueprint: Open Cloud Computing Interface (OCCI) l. Message Queue: Broker to handle interactions between services l. Currently based on Rabbit. MQ l. Metadata Storage: ORM Layer using SQLAlchemy for datastore abstraction l. In current release: My. SQL l. In Diablo: Postgre. SQL l. User Manager: Directory service to store user identities l. In current release: Open. LDAP, Fake. LDAP (with Redis), Database l. Scheduler: Determines the placement of a new resource requested via the API l. Modular architecture to allow for optimization l. Base schedulers included in Bexar: Round-robin, Least busy l

System Components (Cont. ) Compute Worker: Manage compute hosts through commands received on the

System Components (Cont. ) Compute Worker: Manage compute hosts through commands received on the Message Queue via the API� l. Base features: Run, Terminate, Reboot, Attach/Detach Volume, Get Console Output l. Network Controller: Manage networking resources on compute hosts through commands received on the Message Queue via the API l. Support for multiple network models l. Fixed (Static) IP addresses, VLAN with NAT, DHCP l. Volume Worker: Interact with i. SCSI Targets to manage volumes� l. Base features: Create, Delete, Establish l. Image Store: Manage and deploy VM images to host machines l

New Features in Diablo and Beyond Quantum: Networking as a Service l. Developed in

New Features in Diablo and Beyond Quantum: Networking as a Service l. Developed in the open by Cisco, Nicira, others l. Burrow: HTTP-based message queue l. Red Dwarf: Database as a Service l. Keystone: Integrated, pluggable auth for all Open. Stack components l. Lunr: Volumes as a Service l. Dashboard: Control nova and other Open. Stack components via web l

Q & A

Q & A

Open. Stack Cloud Architecture Object Storage

Open. Stack Cloud Architecture Object Storage

Object Storage Summary

Object Storage Summary

To Load Balancers Example Open. Stack Object Storage Hardware Proxies 5 Zones 2 Proxies

To Load Balancers Example Open. Stack Object Storage Hardware Proxies 5 Zones 2 Proxies per 25 Storage Nodes 10 Gig. E to Proxies 1 Gig. E to Storage Nodes 24 x 2 TB Drives per Storage Node Example Large Scale Deployment -- Many Configs Possible

Object Storage Key Features Re. ST-based API Data distributed evenly throughout system Scalable to

Object Storage Key Features Re. ST-based API Data distributed evenly throughout system Scalable to multiple petabytes, billions of objects Account/Container/Object structure (not file system, no nesting) plus Replication (N copies of accounts, containers, objects) No central database Hardware agnostic: standard hardware, RAID not required

System Components The Ring: Mapping of names to entities (accounts, containers, objects) on disk.

System Components The Ring: Mapping of names to entities (accounts, containers, objects) on disk. l Stores data based on zones, devices, partitions, and replicas l. Weights can be used to balance the distribution of partitions l. Used by the Proxy Server for many background processes l Proxy Server: Request routing, exposes the public API l. Replication: Keep the system consistent, handle failures l. Updaters: Process failed or queued updates l. Auditors: Verify integrity of objects, containers, and accounts l

System Components (Cont. ) Account Server: Handles listing of containers, stores as SQLite DB

System Components (Cont. ) Account Server: Handles listing of containers, stores as SQLite DB l. Container Server: Handles listing of objects, stores as SQLite DB l. Object Server: Blob storage server, metadata kept in xattrs, data in binary format l. Recommended to run on XFS l. Object location based on hash of name & timestamp l

Evolution of Object Storage Architecture Version 1: Central DB (Rackspace Cloud Files 2008) Version

Evolution of Object Storage Architecture Version 1: Central DB (Rackspace Cloud Files 2008) Version 2: Fully Distributed (Open. Stack Object Storage 2010)

Example Small Scale Deployment

Example Small Scale Deployment

Q & A

Q & A

Open. Stack Community IRC (freenode) l #openstack-dev l #openstack-meeting l #lunr l Docs lhttp:

Open. Stack Community IRC (freenode) l #openstack-dev l #openstack-meeting l #lunr l Docs lhttp: //wiki. openstack. org lhttp: //docs. openstack. org lhttp: //swift. openstack. org lhttp: //nova. openstack. org l Twitter l@openstack l

Thank You! Questions & Answers

Thank You! Questions & Answers