Taking OpenStack into Production: Code Readiness - Mil-OSS

January 5, 2018 | Author: Anonymous | Category: Engineering & Technology, Computer Science, Information Security
Share Embed Donate


Short Description

Download Taking OpenStack into Production: Code Readiness - Mil-OSS...

Description

OpenStack Update Infrastructure as a Service May 23nd 2012 Rob Hirschfeld, Dell

& • Dell has been a part of OpenStack since inception • We have had an OpenStack-powered Cloud solution in market for nearly a year. • We are seeing substantial field interest with installed OpenStack clouds in the teens with a backlog of orders. • Our solution includes: – hardware, software, consulting, – operations best practice (DevOps), – and ecosystem partners.

What is Cloud Infrastructure Software (like Amazon Cloud) • Apache 2 Open source – Community developed: International, Multi-Vertical – Dedicated Foundation overseeing governance • Delivers software, control panels, and APIs required to securely orchestrate a massive-scale cloud – Virtual workloads (like “EC2”) – Object Storage (like “S3”) – Coming: Block & Networks • Multiple Integrated Components

?

Use Cases • Markets – – – –

Hosting & Telco Financial Academic & Government (NASA was a founder) Web & SaaS

• All Geographies • Reasons for Adoption – – – –

License Avoidance (open source) Scale Architecture (no SANs, no clusters) Pace of innovation Market Buzz – expectation of ecosystem

Investment Risk & Return • Risks – Fast Development Cycle (drives upgrade treadmill) – Security (due to lack of maturity) – Evolving/Missing Components (e.g.: network, block store)

• Safest Path – Private Cloud with Static Networks – KVM & Ubuntu getting heaviest developer focus – Object Store (Swift) is most stable & scalable

• Return on Investment – License costs (offset by needed expertise) – Uses “cloud optimized hardware” – Leverage growing ecosystem (hybrid cloud, tools portability, etc)

Community Health OpenStack’s community is remarkably vibrant, well funded and rapidly expanding. It is no longer lead by any single vendor. • Prominent Adopters – Private Cloud Solutions (Dell, Nebula, Piston) – Large public clouds & hosting companies (Rackspace, ATT, NTT, Dreamhost, HP, Deutsche Telecom) – Web & SaaS Providers (eBay, Wikimedia, ) – Government (NASA) – Major Linux Distributions (Ubuntu, Suse, RedHat) – Hardware Vendors (Dell, HP, IBM, Cisco)

• Substantial Contributors – Dev: Rackspace, HP, RedHat, Citrix, Nebula, Cisco, Canonical, Piston … – Ops: Dell has lead here with Opscode. Puppet joining.

Graphical Roadmap Folsom

Cactus

Austin Formation

Bexar

Community Forming

First Shared Code

Working Prototypes

Essex

Platform for Innovation

Diablo

Production Ready

Core Platform for Innovation

Workable Foundation

Stable Foundation

Network aaService Block Storage API

Included in Ubuntu 12.04

Solidify Community Loses VMware & HyperV

Incubated/Partial: Network & Block Storage 2012

2011 Nov 2010

Nov 2010: Austin Release

Dec

Public Adoption Multiple Scale Deployments

Feb

Feb 2011: Bexar Release

Apr

Apr 2011: Cactus Release

Jun

Oct

Aug

Sep 2011: Diablo Release

Dec

Feb

Mar 2012: Essex Release

Apr

Jun

Aug

Oct 2012: Folsom Release

Readiness Today • Current Release: Essex – April 2012

• Strengths • Stability • Integrated Authentication (Keystone) • User Interface Dashboard (Horizon)

• Cutting Edge Opportunities – Networking Service Incubation (Quantum)

• Risks – Block Storage

Futures / Roadmap • Next Release: Folsom – October 2012

• Major Trends – Networking Innovation – Block Storage – Deployment Standardization

• Areas to Watch – Ecosystem Growth – Distributions from New Operating Systems

& • Dell mission for OpenStack – Shorten customers time-to-value on OpenStack – Contributed open source “DevOps” installer

• What is Crowbar? – Dell lead Open Source Cloud Deployer Project – Not limited to Dell Hardware – Brings in “operations as code” approach – Supports multiple Operating Systems – Supports multiple Hadoop, OpenStack & others

View more...

Comments

Copyright � 2017 NANOPDF Inc.
SUPPORT NANOPDF