This document provides an overview of OpenStack architecture and design principles. It discusses how OpenStack was founded in 2010 by NASA and Rackspace to provide an open source cloud computing platform. It operates using a microservices architecture, with independent components communicating through well-defined APIs and without any other inter-process communication. This service-oriented architecture is modeled after Amazon's approach. The document also notes Mirantis' role as a leading OpenStack company and contributor.

1. OpenStack
Architecture
Tomasz ‚Zen’ Napierała
Development Manager @ Mirantis, Inc.

2. • HQ in Mountain View + 8 offices
• Backed by Intel Capital, Insight Venture Partners,
WestSummit Capital, August Capital, Ericsson,
Sapphire Ventures, Siguler Guff, Dell Ventures
• Delivering technology, integration, training and
support for OpenStack

3. What we actually do
• #1 Pure Play Openstack
Company
• #3 contributor to OpenStack
• Authors of Fuel
• Authors of reference HA
architecture for OSt

6. WTF is

9. Hot & sexy

11. $1.7 bilion in 2016

12. OpenStack
• Founded in 2010 by NASA + Rackspace
• Managed by OpenStack Foundation

13. OpenStack
• Free and OpenSource cloud computing software
platform
• Provides IaaS

14. How OpenStack is
designed?

15. Amazon rules
• All teams will henceforth expose their data and
functionality through service interfaces.
• Teams must communicate with each other through
these interfaces.
• There will be no other form of inter-process
communication allowed: no direct linking, no direct reads
of another team’s data store, no shared-memory model,
no back-doors whatsoever. The only communication
allowed is via service interface calls over the network.

16. Amazon rules
• It doesn’t matter what technology they use.
• All service interfaces, without exception, must be
designed from the ground up to be externalizable.
That is to say, the team must plan and design to be
able to expose the interface to developers in the
outside world. No exceptions.

17. –Jeff Bezos, Amazon Founder and CEO
„Anyone who doesn’t do this will be fired. Thank
you; have a nice day! „
2002

18. Service Oriented
Architecture

19. Components

20. Components

21. Component

22. Fundaments

23. organizations which design systems ...
are constrained to produce designs
which are copies of the communication
structures of these organizations
-M.Conway, 1968

27. Process
Code Commit Gate
Review
Merge

28. Zuul

29. Fundaments
• Only do what you do good
• focus on the core
• use existing tools
• think about the upgrades

30. We are hiring. Of course

31. Feedback or questions?
tnapierala@mirantis.com
@tzn
or
find me around