1. “Open Source in the Cloud”
November 12th, 2012
5:30 – 7:30pm
“Open Source in the Cloud”
Sponsored by

2. Sonian, Open Source and Sensu
November 12, 2012

3. Sonian’s Contributions
Fog -
Elasticsearch -
Openstack Swift -
Opscode Chef –
Various Chef Tools:

4. Home Built and Released
SCLI (Smart Cloud Command Line interface)
(MIT)
Amazon-Pricing (Pricing Gem)
(Ruby)
ElasticSearch Jetty Plugin
(Apache 2)
Sensu – Monitoring Framework
(MIT)

5. Sensu – “The Monitoring Router”
Monitoring Framework – Built for the cloud (Dynamic Environments)
Ruby (EventMachine, Sinatra, AMQP), RabbitMQ, Redis
Messaging oriented architecture. Messages are JSON objects. (Pub/Sub)
Ability to re-use existing Nagios plugins
Plugins and handlers (think notifications) can be written in any language
Designed with modern configuration management systems such as Chef or Puppet in mind
Lightweight, less than 1200 lines of code

6. Why We Built It Highly Elastic Infrastructure
Nodes are created (Spot Nodes)
Bootstrapped (With Chef)
Take and process work
Terminated (when prices increase)
All before they are discovered and monitored by Nagios
Nagios is:
Difficult to Extend
Can not discover new services on its own
Generally Unpleasant

7. Keep It Simple™ The Idea: Schedule the execution of remote checks
Collect their Results
“Checks” are:
Is the server up?
How hard is it working?
Tied into Modern CM
Chef
Puppet
Message Oriented Middleware
RabbitMQ
Securely Routing Checks/Results
Redis: Fast In-Mem K/V Store

8. Open Source = Community
Early Development – Recruit Community Experts
Help Test – Drive Early Roadmap
Develop Puppet and Chef modules
Release Day (Nov 1st 2011)
Make Sensu Github Repo Public
Open IRC channel on Freenode (#sensu)
Blog posting and Twitter for marketing
Community, Community, Community
Adoption – Documentation
“Omnibus” Style Packaging for Quick Deployments

10. Contact
Pete Cheslock
Director of Technical & Cloud Sonian
@petecheslock
We’re Hiring!
Please contact Sonian’s VP of Product Development Glenn Snyder

11. Level Set on Current Cloud Trends, pain points, and markets
Outline
Level Set on Current Cloud Trends, pain points, and markets
Open Source Trends
OpenStack Introduction
What it is
Historical Evolution
Use Cases
Conceptual Architecture
Customer Adoption
Cloud Taxonomy

12. Level Set On Cloud trends

13. Cloud is about Services, Not Systems: Consumer Market Driving Trends
Interconnected mobile devices
24/7 CLOUD SERVICES
Anywhere, Anytime, Internet Access

14. Enterprises: Same Cloud Services Goals But Different Market Segments and Pain Points
Mega Datacenter
Burdened by “legacy” infrastructure and applications
Too complex to manage
Expensive to implement and maintain
Takes too long to realize value
Not easy to innovate
Security, compliance, and privacy concerns
Mega Datacenters
Homogeneous
Dense/Low Cost
Small Site (SMB/Branch)
Low Cost
Ease of deployment
Ease of management
Enterprise Datacenter
Heterogeneous
Legacy / Complex
Consolidating Quickly
Small Site (SMB/Branch)
Enterprise Datacenter
Source: IDC

15. Virtual Machines Already Outstripping Physical Machines
“2012: RATE(of VMs launched per sec 6/sec) > RATE (at which babies are born in the US per sec 8/sec) (from #VMW) #cloud”

16. But what about storage and networks?
Extensive Use of SAN
>$2000 / VM
Specialized Skillset
Fixed Capacity
Complex Networks
Everyone talks about cloud as compute, but what about storage and networking.
Wholesale change in IT...the way we consume IT
Cloud doesn’t work if the SYSTEM isn’t solid
Solid State Disks (SSDs) allow high performance with IOPs increases up to 10x
the enterprise can deploy and launch applications significantly faster
This configuration makes SAN-speed durable storage affordable to all IT organizations
The mCloud DCU provides all of the advantages of SSD without the penalties of SSD (durable data)
Additionally, the SSD-implementation affords a significantly lower power footprint
With a share-nothing architecture, SSDs completely eliminate boot storms
Dense Blades

17. Virtualization 1.0: Not up to the challenge
HOST 1
HOST 2
HOST 3
HOST 4, ETC. VM
Hypervisor
(VMWare ESX, Citrix XEN Server, KVM, Etc.)
KVM
Hardware abstraction for each server
Better resource utilization for each server
1. Server Virtualization
2. Cloud Data Center
3. Cloud Federation
Automation & Efficiency

18. But questions arise as the environment grows...
“VM SPRAWL” CAN MAKE THINGS UNMANAGEABLE VERY QUICKLY
APPS
USERS
ADMINS
How do you make your apps cloud aware?
How do you empower people to self-service?
Where should you provision new VMs?
How do you keep track of it all? +
1. Server Virtualization
Server Virtualization
2. Cloud Data Center
3. Cloud Federation
Automation & Efficiency

19. But questions arise as the environment grows...
“VM SPRAWL” CAN MAKE THINGS UNMANAGEABLE VERY QUICKLY
APPS
USERS
ADMINS
A Cloud Management Layer Is Missing
1. Server Virtualization
Server Virtualization
2. Cloud Data Center
3. Cloud Federation
Automation & Efficiency

20. What is needed is a cloud Operating System that adds automation and control at scale
USERS
ADMINS
APPS
Connects to apps via APIs
Self-service for users
CLOUD OPERATING SYSTEM
Creates Pools of Resources
Automates The Network
1. Server Virtualization
Server Virtualization
2. Cloud Data Center
3. Cloud Federation
Automation & Efficiency

21. Types of pools managed by the Cloud O.S.
COMPUTE, NETWORK, & STORAGE
Compute Pool
Network Pool
Load Balancing Pool
Compute, Network and Storage are the 3 key pillars of the Cloud Operations Systems.
Image/Catalog Service, API and Dashboard are peripheral services
Storage Pool
Image Service Pool
1. Server Virtualization
Server Virtualization
2. Cloud Data Center
3. Cloud Federation
Automation & Efficiency

22. Assembly Line IT - people doing what people are NOT good at
- everything is a silo: people, processes, & technology

23. Robotics Factory IT - people doing what people ARE good at
- credit suisse story: ticket-wall

24. Open Source, OpenStack Evolution and Trends

25. Innovation + Open Source = Virtuous Cycle
Open source is leading, not following, in important areas including cloud, big data, mobile apps and enterprise mobility.
More than 50 percent of software acquired in the next five years will be open source software.
Innovation, flexibility, cost, quality of open source are some of the top reasons that make it attractive for use
Companies most likely to be impacted by OSS have these characteristics: Business drivers to invest in IT, software development is an essential strategic process, technology centric
When asked about revenue generating strategies likely to create value for vendors, 52 percent of respondents said an annual, repeatable support and service agreement was the most likely value strategy
Open Source Innovation
600,000+ OSS projects
100+ billion lines of code
10 million person-years of work
Source: Blackduck

26. OpenStack is the Open Source Software Powering Public and Private Clouds
Run OpenStack software
in your own
data centers
Public Cloud:
OpenStack powers some
of the worlds largest public
cloud deployments.
Diagram has connecting lines labeled as “common software platform makes federation possible” (or some such wording)
1. Server Virtualization
2. Cloud Data Center
3. Cloud Federation
Automation & Efficiency

27. What is it: An open source cloud operating system
30,000 lines of code to 600,000 in under 18 months
Who’s building it: A worldwide community of developers
600+ developers, 250+ contributed in the last 12 months
6000+ individual members in 87 countries
Who is govering it: The OpenStack Foundation, backed by AT&T, Canonical, Cisco, ClearPath, Cloudscaling, Dell, DreamHost, HP, IBM, ITRI, Mirantis, Morphlabs, Nebula, NetApp, Piston, Rackspace, Red Hat, SUSE, and Yahoo! (so far)

28. Wide-Ranging Community Support….
Confidential
6/5/2018

29. OpenStack Timeline Bexar First Public Code Austin Formation Sep 2011:
Folsom
“Platform for Innovation”
Core Platform for Innovation
Network as a Service
Block Storage
Public Adoptoin
Multiple Scale Deployments
Essex
“Production Ready”
Stable Foundation
Included in Ubuntu 12.04
Incubated: Network & Block Storage
Diablo
Workable Foundation
Exposes Gaps
Solidify Community
Loses VMware & HyperV
Cactus
Community Development
Forming
Working
Prototypes
Bexar
First Public Code
Austin
Formation
2011
2012
Nov 2010
Dec
Feb
Apr
Jun
Aug
Oct
Dec
Feb
Apr
Jun
Aug
Sep 2011:
Diablo
Release
Mar 2012:
Essex
Release
Oct 2012:
Folsom
Release
Nov 2010: Austin
Release
Feb 2011: Bexar
Release
Apr 2011:
Cactus
Release
Oct 2010: Design
Summit
Apr 2011: Design
Summit
Oct 2011: Design
Summit
Apr 2012: Design
Summit

30. OpenStack Value Proposition
Lock-in &
Licenses
Open APIs
& Support
Provides
Reduces
Addresses Real Market Pains
Limits costly software licenses
Limits lock-in by vendors (VMware) & by providers (Amazon)
Allows for massive scalability
Extensible hypervisor support (Xen, KVM, Hyper-V, etc.)
Offers standard APIs enabling growing cloud ecosystem
OpenStack is commoditizing the IaaS market from single provider (Amazon) to many small copy cats (startups).

31. Popular OpenStack Use Cases
Service providers offering an IaaS compute platform
IT departments provisioning compute resources to teams and projects
Processing big data with tools like Hadoop
Scaling compute up and down to meet demand for web resources and applications

32. OpenStack Conceptual Architecture
Confidential
6/5/2018

33. There is a broad adoption of OpenStack across many markets
There is a broad adoption of OpenStack across many markets. The most common markets we have seen so far have been: Universities Healthcare CDN providers Hosting providers Start-ups SaaS companies Government 33
Confidential

34. Vision for Complete OpenStack Solution

35. Complete Cloud Taxonomy
Software as a Service
IT as a Service
Platform as a Service
Infrastructure as a Service
Everything as a Service
Information Service Management
Legacy Management
Firewall
Reporting
Analytics
IPS
Security
LDAP/AD
SSO
Admin Software
Web Services & APIs
Self Service Portal
Customer Management
Entitlement, rights
Billing
Metering
Infrastructure Software
Monitoring
Intelligent Resource Manager
Workload Lifecycle Management
Platform Provisioning
Ser Gov/Workflow Automation
Orchestration
Abstraction Software OS
Hardware Virtualization
Operating System Virtualization
Application Run-Time Virtualization
Data Store
Physical
HVAC
Power
Facility
Network
Environmentals
Compute
Switch
Storage
Overarching Systems

36. Disruption

37. Discussion