3rd birthday of OpenStack and the first meetup of the Nairobi OpenStack user group. We talked about what

1. #openstack3bday

2. OpenStack Mission
To produce the
ubiquitous open source cloud computing platform
that will meet the needs of public and private clouds
regardless of size, by being simple to implement and
massively scalable.
In other words,
to provide Infrastructure as a Service (IaaS) to
consumers whether they are business units within an
enterprise or customers of a public cloud.

3. Infrastructure as a Service?
• Software as a Service (SaaS) – Software
that requires no specific host-based
software (Dropbox, Gmail)
• Platform as a Service (PaaS) –
Programmable environment (Google App
Engine, If This Then That, iCloud)
• Infrastructure as a Service (IaaS) –
Consumer installs OS (Amazon Web
Services, Rackspace Cloud, Hetzner VPS)

4. GoDaddy is not IaaS
• Tenants share the same operating
system, over which they have no admin
control
• Network access control is not possible
(consumer cannot setup VPN)
• API access is not available so control of
the system cannot be made programmatic

5. Cloud?
• Cloud services include SaaS, PaaS, and
IaaS
• They can be deployed privately in a
corporate data center
• Or they can be publicly available
• They can even be deployed within a
community like a school or research
center

6. On-Demand Self Service
A consumer can unilaterally provision computing
capabilities, such as server time and network storage, as
needed automatically without requiring human interaction
with each service provider.
* Next 6 slides from http://csrc.nist.gov/publications/nistpubs/800-145/SP800-
145.pdf

7. Broad Network Access
Capabilities are available over the network and accessed
through standard mechanisms that promote use by
heterogeneous thin or thick client platforms (e.g., mobile
phones, tablets, laptops, and workstations).

8. Resource Pooling
The provider‟s computing resources are pooled to serve
multiple consumers using a multi-tenant model, with
different physical and virtual resources dynamically
assigned and reassigned according to consumer demand.
There is a sense of location independence in that the
customer generally has no control or knowledge over the
exact location of the provided resources but may be able to
specify location at a higher level of abstraction (e.g.,
country, state, or datacenter). Examples of resources
include storage, processing, memory, and network
bandwidth.

9. Rapid Elasticity
Capabilities can be elastically provisioned and released, in
some cases automatically, to scale rapidly outward and
inward commensurate with demand. To the consumer, the
capabilities available for provisioning often appear to be
unlimited and can be appropriated in any quantity at any
time.

10. Measured Service
Cloud systems automatically control and optimize resource
use by leveraging a metering capability at some level of
abstraction appropriate to the type of service
(e.g., storage, processing, bandwidth, and active user
accounts). Resource usage can be
monitored, controlled, and reported, providing transparency
for both the provider and consumer of the utilized service.

11. What Exactly Is OpenStack?
• OpenStack is a set of scripts and software
packages which facilitate launching
compute power and storage on simple
servers
• These services can be isolated between
tenants (i.e. customers) for data security
• OpenStack allows organizations to deploy
their own Infrastructure as a Service (Iaas)

12. What‟s the Point?
• Can‟t I just install a server in a rack for my
application?
• Won‟t I lose performance if my apps aren‟t
running directly on the hardware?
• Security seems like a big issue, no?

13. Server in Rack
• Limited capacity to move OS and services
to other server when hardware is failing
• Can‟t „add‟ more memory or CPU capacity
without an extended outage
• You have to worry about parts and
physical security (including environmental
issues like cooling)

14. Won‟t I lose performance?
• Hypervisors have overhead (some say 1-5%)
• Compute power can even be enabled to bare
metal
• A multi-tenant cluster benefits from
economies of scale (faster RAM, more cores,
more spinning drives)
• Economies of scale extend to management
where engineers can focus just on low-level
performance

15. Security
• Economies of scale extend to security as
well where Ops people can focus on lower
level security
• Ops people can more easily manage
networking ACLs, etc… via Software
Defined Networking (SDN)
• OS-level and logical security under the
purview of the consumer as was the case
before

16. OpenStack is now 3 years old
‣ Expanded scope from Compute and Object Storage
to Compute, Storage, Networking and Shared
Services, with rich ecosystem of Integrated projects
emerging
‣ OpenStack has public clouds in more cities than
Amazon has regions
‣ Major private cloud users at Best Buy, Bloomberg,
Comcast, Fidelity, PayPal and more
‣ OpenStack has become the center of cloud
innovation – more than 1,000 developers, supported
by major IT companies

17. Why are we succeeding?
‣ Successful platforms have three forces:
‣ Technology
‣ Ecosystem
‣ Users
GLOBAL USER
FOOTPRINT

18. Fastest Growing Global
Open Source Community
COMPANIES
TOTAL CONTRIBUTORS
AVERAGE MONTHLY
CONTRIBUTORS
CODE CONTRIBUTIONS
1,036 238 70,137
231
10,149
INDIVIDUAL MEMBERS
COUNTRIES
121
As of July 2013

19. Global Community
Countries with members

20. Developer Growth
Contributors per month (ohloh)

21. 1 Million+ Lines of Code
Lines of code (ohloh)

22. Ecosystem Growth
Participating Companies
0
50
100
150
200
250
Launch Austin Bexar Cactus Diablo Essex 2-year
anniversary
Grizzly

23. Major Users
See these videos and more at
http://www.openstack.org/summit/portland-2013/session-videos/
Add your organization at openstack.org/user-survey

24. Summit Attendee Growth
0
500
1000
1500
2000
2500
3000
Austin San Antonio Santa Clara Boston San Francisco San Diego Portland

25. Core Values Remain
• We‟re keeping sacred what has made
OpenStack so successful
• Open source is essential to unlock the
value of cloud computing
• Four opens:
– Open Design
– Open Development
– Open Community
– Open Source

26. On the horizon
• New projects & functionality, but also focus
on stability and maturity
– Orchestration and Metering become integrated in
Havana
– DBaaS and Bare Metal currently Incubated
projects
• Focus on education and talent development
– New Operations and Security Guides
– Ecosystem and community discussions to
accelerate training and certification
• Reaching application developers

27. Important Dates
September 19, 2013
Foundation One Year
October 17, 2013
Havana Release
**Orchestration &
Metering become
integrated
November 5, 2013
Hong Kong Summit
**First International Summit
outside the US
**(Icehouse Design Summit)
April, 2014
Icehouse Release
May, 2014
“J” Design Summit
January, 2014
**Board of Directors
elections for 8
individual directors
openstack.org/join

28. How you can help
Infrastructure Team
• Want to help run systems powering OpenStack development?
• Read the documentation at http://ci.openstack.org/
Documentation
• Contact Anne Gentle <anne.gentle@rackspace.com>
• or visit http://wiki.openstack.org/Documentation/HowTo
Translations
• Do you speak multiple languages?
• Join the Internationalisation team: https://wiki.openstack.org/wiki/I18nTeam
• Or contact Ying Chun “Daisy” Guo <guoyingc@cn.ibm.com>
Ask.OpenStack.org
• Please participate and help answer questions
User Profile
• If you are an OpenStack user, please create a profile (public or private) at
openstack.org/user-survey

29. Hong Kong Summit
• November 5-8, 2013 – Hong Kong!
• Registration and sponsorships now open
– New: Two tiers of registration, please read carefully
• Call for speakers deadline July 31
• Book your travel early, room blocks are filling up!
• Travel Assistance Program – applications in July
• More details at openstack.org/summit