China OpenStack User Group(COSUG)

Introduction

： ben_ 杜玉杰Dec 2011 for JiangSu LUG

What is OpenStack?

A collection of open source technologies delivering a scalable

cloud operating system.

OpenStack is a global collaboration of developers and cloud computing technologists producing the open standard cloud computing platform for both public and private clouds. The project aims to deliver solutions for all types of clouds by being simple to implement, massively scalable, and feature rich. The technology consists of a series of interrelated projects delivering various components for a cloud infrastructure solution.

Why OpenStack?

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

How?

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 Tenets

Scalability & elasticity

Everything should be asynchronous

Shared-nothing architectures

Accept eventual consistency

Test everything

Design TenetsScalability and elasticity are our main goals Any feature that limits our main goals must be optionalEverything should be asynchronous

If you can't do something asynchronously, see #2All required components must be horizontally scalable Always use shared nothing architecture (SN) or sharding

If you can't Share nothing/shard, see #2Distribute everything

Especially logic. Move logic to where state naturally exists.

Accept eventual consistency and use it where it is appropriate.Test everything.

We require tests with submitted code. (We will help you if you need it)

OpenStack Principles

Open 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.

OpenStack Today

Nova Overview

Written in Python

HTTP/ReST API (multiple)

Instances, Networking, Volumes

Working on service provider scale now

More at: http://nova.openstack.org/

Glance Overview

Written in Python

HTTP/ReST API

Image service for Nova

More at: http://glance.openstack.org/

Swift Overview

Written in Python

HTTP/ReST API

Accounts, containers, and objects

CDN Integration

No single point of failure

Last write wins

More at: http://swift.openstack.org/

Open Platform Services

Auth Service (KeyStone)

Dashboardhttp://wiki.openstack.org/OpenStackDashboard

Block Storage Service (lunr)

Message Queue (http://burrow.openstack.org/)

Database Service (Red Dwarf)

Load Balancer Service (Atlas)

Release Process

OpenStack 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-2

2012 January 26th essex-3

March 1st essex-4

8th~29th Release Candidates

April 5th Essex Release

19th Design Summit

OpenStack in China

slides:

http://www.slideshare.net/ben_duyujie/presentations

photos ：

http://www.flickr.com/photos/ben_duyujie/sets/72157627499319861/

maillist ：

http://groups.google.com/group/china-openstack-user-group

COSUG Goal and Mission

Goal : – Promoting OpenStack to bring open and

standardization in Cloud methodology and strategy

Mission : – 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