Getting started on OpenstackArchitecture, Installation and Containers

Marco Berubesr. Cloud Solutions ArchitectMay 2016

Openstack is designed to scale

3

Red Hat Openstack 8 - Core Components

openstack reference architecture

4

COMPUTE NODEFrom 1 node to xxxxx

nic1

nic2

nic3 bond

CONTROLLER NODEMinimum 3 nodes for HA

nic1

nic2

nic3 bond

CEPH NODEFrom 3 nodes to xxxxx

nic1

nic2

nic3 bond

DIRECTOR NODE1 node per region

nic1

nic2

provisioning network / P

XE

tenant netw

ork

Internal AP

I and cluster managem

ent netw

ork

storage network (front-

end)

storage managem

ent network (back-

end)

public AP

I floating IP

s

DEPLOYMENT

LIFECYCLE

5

PLANNING OPERATIONS

OpenStack directorProject’s Mission

Updates and upgradesScaling up and downChange management

Deployment orchestrationService configuration

Sanity checks

Network topologyService parametersResource capacity

UPSTREAMOPENSTACK

TripleO RDO-Manager

MIDSTREAMCOMMUNITY

RHEL OpenStack Platform director

DOWNSTREAMPRODUCT

6

UPSTREAMOPENSTACK

TripleO RDO-Manager

MIDSTREAMCOMMUNITY

RHEL OpenStack Platform director

DOWNSTREAMPRODUCT

From Upstream to Product

7

RHEL OpenStack Platform director is providing a solution which is:

● solving for complete OpenStack lifecycle,● part of upstream OpenStack community,● rich on partner ecosystem,● solving for deployments in scale,● strong in community & product support.

OpenStack directorKey values

How can I get started without all this equipment?

Disclaimer :

The following network architecturesare not best practices

* but very common to get started with Openstack :-)

openstack reference architecture

10

COMPUTE NODEFrom 1 node to xxxxx

nic1

nic2

nic3 bond

CONTROLLER NODEMinimum 3 nodes for HA

nic1

nic2

nic3 bond

CEPH NODEFrom 3 nodes to xxxxx

nic1

nic2

nic3 bond

UNDERCLOUD NODE1 node per region

nic1

nic2

provisioning network / P

XE

tenant netw

ork

Internal AP

I and cluster managem

ent netw

ork

storage network (front-

end)

storage managem

ent network (back-

end)

public AP

I floating IP

s

Great for production but

complex for a laptop, lab or

a few test nodes!

openstack Lab architectureScenario 1: basic tenant networking

11

COMPUTE NODEFrom 1 node to xxxxx

nic1

CONTROLLER NODE1 node

nic1

Tenant & storage netw

ork

Floating IPs and public A

PI

Nic2 (br-ex)

NFS or CEPH STORAGENOVA / GLANCE / CINDER storage

nic1

openstack Lab architectureScenario 2: provider networks

12

COMPUTE NODEFrom 1 node to xxxxx

nic1

CONTROLLER NODE1 node

nic1

provider & storage netw

ork

NFS STORAGENOVA / GLANCE / CINDER storage

nic1

# /etc/neutron/dhcp_agent.ini

enable_isolated_metadata=trueenable_metadata_network=true

openstack Lab architectureScenario 3: All-in-one + tenant network

13

CONTROLLER + COMPUTE +STORAGE (NFS or LVM)

nic1nic2 (br-ex)

provider & tenant netw

ork

Floating IPs and public A

PI

Packstack installation{ instructions at www.marcoberube.com }

Orchestrating containers

Openshift high-level architecture

16

Red Hat Open Hybrid Cloud

17

Traditional Virtualization Private Cloud Public Cloud

or

Leveraging Openstack IaaS capabilities

18

Network and Storage orchestration

IaaS

PaaS

Cloud Instance Cloud Instance Cloud Instance

nova cinder LBaaS

THANK YOU

plus.google.com/+RedHat

linkedin.com/company/red-hat

youtube.com/user/RedHatVideos

facebook.com/redhatinc

twitter.com/RedHatNews