On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
A collection of open sourcetechnologies delivering a scalable cloud operating system.
OpenStack is a global collaboration of developers andcloud computing technologists producing the open standardcloud computing platform for both public and privateclouds. The project aims to deliver solutions for all types ofclouds by being simple to implement, massively scalable,and feature rich. The technology consists of a series ofinterrelated projects delivering various components for acloud infrastructure solution.
Cloud is commodity
Cloud is not portable
Open source clouds are not service provider ready
We need the LAMPstack of the cloud
Open Source Is Where“Standard” Cloud Infrastructure Will Be Defined
OpenStack Philosophy: Open
Open Source – the Apache License, 2.0.Open Community – Most decisions will be made using a lazy consensus model. All processes will be documented, open and transparent.Open Development – A publicly available source code repository through the entire development process.Open Design – The summits are open to the public.
Design TenetsScalability & elasticityEverything should be asynchronousShared-nothing architecturesAccept eventual consistencyTest everything
Design Tenets Scalability and elasticity are our main goals Any feature that limits our main goals must be optional Everything should be asynchronous If you cant do something asynchronously, see #2 All required components must be horizontally scalable Always use shared nothing architecture (SN) or sharding If you cant Share nothing/shard, see #2 Distribute everything Especially logic. Move logic to where state naturally exists. Accept eventual consistency and use it where it isappropriate. Test everything. We require tests with submitted code. (We will help you if you need it)
OpenStack PrinciplesOpen development model: – All of the code for OpenStack is freely available under the Apache 2.0 license.Open design process: – Every six months the development community will hold a design summit to gather requirements and write specifications for the upcoming release. The summits are open to the public and attendees include users, developers, and upstream projects.Open community: – OpenStack is dedicated to producing a healthy, vibrant, and active developer and user community. Most decisions will be made using a lazy consensus model. All processes will be documented, open and transparent.
Nova OverviewWritten in PythonHTTP/ReST API (multiple)Instances, Networking, VolumesWorking on service provider scale nowMore at: http://nova.openstack.org/
Glance OverviewWritten in PythonHTTP/ReST APIImage service for NovaMore at: http://glance.openstack.org/
Swift OverviewWritten in PythonHTTP/ReST APIAccounts, containers, and objectsCDN IntegrationNo single point of failureLast write winsMore at: http://swift.openstack.org/
Open Platform ServicesAuth Service (KeyStone)Dashboard http://wiki.openstack.org/OpenStackDashboardBlock Storage Service (lunr)Message Queue (http://burrow.openstack.org/)Database Service (Red Dwarf)Load Balancer Service (Atlas)
Release ProcessOpenStack is currently on a 6-month release cycle,which consists of four stages.Planning The Planning stage usually lasts 3 weeks and consists of discussion and feedback on what the next release will focus on. After deciding on the features, we write the corresponding specs on how to make them happen. The Design Summit usually takes place during the second week of the planning stage.
Release ProcessImplementation – The Implementation stage is split into a number of milestone iterations. The work in progress is published in a branch, which should then be proposed for merging when ready. Code is proposed several weeks before each milestone release date so that it can be reviewed in a timely manner.QA – This is the testing phase. Testing, prioritizing bugs, and documentation are key parts of the QA phase. Only branches that fix bugs and do not introduce new features are allowed to enter the release branch.Release – Release Candidate Freeze (RCF) happens two days before the actual Release Day.
Essex Release schedule2011 October 6th Design Summit November 10th essex-1 December 15th essex-22012 January 26th essex-3 March 1st essex-4 8th~29th Release Candidates April 5th Essex Release
COSUG Goal and MissionGoal : – Promoting OpenStack to bring open and standardization in Cloud methodology and strategyMission : – Promote OpenStack’s BEST to China Industry • B – Business opportunity • E – Experience sharing • S – Social network • T – Technical communication
User Group (on Google Group)
Question & Comment Join COSUG Google Grouphttp://groups.google.com/group/china-openstack-user-group