Young Rackspace

8/2/2019 Young Rackspace

1/27

Public and Private Clouds:

Working Together

Principal Architect, Rackspace Cloud BuildersAnthony Young

[email protected]
mailto:[email protected]:[email protected]


2/27

Principal Architect, Rackspace

Cloud Builders

Responsible for dev effortsrelated to Rackspace PrivateEdition

Previously software engineer atAnso Labs, acquired by RAX Jan2011

[email protected]

About Me
mailto:[email protected]:[email protected]:[email protected]


3/27

About Rackspace Cloud Builders

Available to help service providers and enterprisesbuild and support OpenStack clouds

Training, deployment and ongoing support

Key engineering resources driving OpenStack

Operational expertise from Rackspace Cloud

3


4/27

About OpenStack

4


5/27

The Pieces of OpenStack

OpenStack Compute (Nova)

OpenStack Object Storage (Swift)

OpenStack Image Service (Glance)


6/27

The Pieces of OpenStack

Dashboard

Identity Management

Networking

Load balancers

Database

Queueing


7/27

Some Stats

1,500+ active participants

17 countries represented at Design Summit

60,000+ downloads

Worldwide network of user groups (North America, SouthAmerica, Europe, Asia and Africa)


8/27

OpenStack Community Today


9/27

OpenStack, the Cloud Operating System

9

Management Layer That Adds Automation & Control


10/27

OpenStack in a nutshell

A cloud operating system that turns datacenters into pools ofresources the next evolution from server virtualization

Provides a management layer for controlling, automating, andefficiently allocating these resources

Empowers operators, sys admins and end users via self-service portals (I want AWS-type service!)

Gives developers the capability to build cloud-aware

applications via standard APIs

10


11/27

Why Service Providers Are Adopting

Originated by Rackspace and NASA

Designed to scale cost effectively

Emerging standard backed by large ecosystem

Open source with no lock-in or license

No desire to build proprietary clouds

11


12/27

Challenges of Cloud Interoperability

12


13/27

OpenStack Goes Beyond A Single

Datacenter

13

Enterprise Private CloudsRun Cloud Operating

Systems

Public Clouds Run Cloud

Operating Systems


14/27

OpenStack Goes Beyond A Single

Datacenter

14

Imagine Having an Open,Common Platform Across

Clouds

Seamlessly transportingworkloads

This is true Cloud Federation!


15/27

An Open, Common Platform is Here

15

Private CloudsRun OpenStack

Software In YourOwn Corporate

DC or ColocationFacility

Public CloudsRun Highly

Scalable CloudSoftware Provenby Some of theWorlds Largest

Cloud Providers


16/27

Well almost

Today, there are still technical challenges that have tobe addressed before users of OpenStack clouds canreliably create cross-cloud compatible applications.

16


17/27

Key Use Case

Anne is running an application on a Private Cloud.She is now experiencing higher than averageworkload, so she launches several dozen applicationinstances on a Public Cloud.

17


18/27

Challenges

Even if we assume the same API amongst cloudproviders, there are a variety of challenges that wehave identified that need to be addressed if we want toenable Annes use case.

18


19/27

Challenges

If the implementation of all clouds were the same,accomplishing federation would be easy.

However, public and various private clouds are likely tohave different requirements that will dictate different

internal technology choices, even if they share theexact same external API.

19

Hypervisor: KVM

Image Format: qcow2Networking: FlatDHCPInstance Auth: Public Key

Hypervisor: XenServer

Image Format: VHDNetworking: Flat + multi-nicInstance Auth: Password

Private OpenStack Cloud Public OpenStack Cloud


20/27

Challenges

Thus, in order to achieve interoperability betweenOpenStack clouds, points of compatibility must bedefined for: Image Format

A variety of disk formats are used in different clouds (qcow2,vhd, raw) which must be supported by all? How can they beconstructed such that they work on multiple hypervisors?

Instance Networking

Specific deployments may use different networking modelsinternally, may have different numbers of nics, etc

Instance Configuration

How should instances configure authentication, handle userspecific data, installation of paravirtualization drivers, etc?

20


21/27

Image Format

Depending on choice of hypervisor, and specificdesired operational characteristics, deployers are likelyto prefer the use of non standard internal imageformats.

For interoperability, the community needs to agree ona common Golden format that all clouds must be ableto support. All clouds must be able to import/export the Golden format.

Internally, clouds will likely decide to use a format that is optimal fortheir own configuration.

Idea: use RAW as a golden image format

21


22/27

Instance Networking

At present, there are a few techniques that are

available to configure networks in OS DHCP

What about multi-nic?

Flat injection

Cloud configuration drive? We need to define a standard method for instance

networking that will work in a wide variety ofdeployment scenarios

What happens when a cloud instance with one DHCP configurednic gets migrated to a public cloud with 2 nics?

Idea: Use DHCP for basic networking. Use a guestagent + metadata service for multi-nic and otheradvanced networking functions

22


23/27

Instance Configuration

At present, there are a variety of techniques that areavailable in OS for instance configuration EC2 Metadata

File injection

Cloud configuration drive

Idea: OS Metadata service + OS guest agent

23


24/27

Putting it all together example flow

Anne exports an image from Private cloud in RAW

format Anne imports her image into the Public Cloud

Internally, this instance is converted to an optimized format

Anne boots her image

Her instance gets an ip address for the primaryinterface

OS guest agent launches, and connects to a metadataservice to get additional information

Configures a secondary interface Installs Paravirtualization drivers (like xenserver tools)

Executes user data

Anne accesses her instance and launches her app

24


25/27

Still lots to do

Need to vet proposed strategy with community,partners, and other deployers

Once key compatibility points are agreed upon,implement feature gaps

Integrated testing for Golden Flows

25


26/27

How You Can Participate

Website: www.openstack.org

Mailing Lists: http://lists.openstack.org

Wiki: http://wiki.openstack.org

Twitter: @openstack
http://www.openstack.org/http://lists.openstack.org/http://lists.openstack.org/http://lists.openstack.org/http://www.openstack.org/


27/27

Thank You!

Principal Architect, Rackspace Cloud BuildersAnthony Young

[email protected]
mailto:[email protected]:[email protected]

Date post:	06-Apr-2018
Category:	Documents
Upload:	nadia-metoui
View:	225 times
Download:	0 times

Young Rackspace

Documents