Mastering OpenStack - Episode 02 - Simple Architectures

Presentation By:
Roozbeh Shafiee
Spring 2015
IRAN OpenStack Users Group
MASTERING
OPENSTACK
(Episode 02)
Simple Architectures

|
Agenda:
●
OpenStack Networking
●
Reasons of Choosing the Tools
●
Node Types
●
Network Connections
●
Iran OpenStack Community
IRAN Community OpenStack.ir
OpenStack Simple Architectures

|
OpenStack Networking
(Neutron)

|
OpenStack Networking:
A highly-available environment can be put into place if you require an
Environment that can scale horizontally, or want your cloud to continue to be
operational in case of node failure.
This example architecture has been selected based on the current default feature
set of OpenStack Havana, with an emphasis on high availability. This architecture
is currently being deployed in an internal Red Hat OpenStack cloud and used to
run hosted and shared services, which by their nature must be highly available.

|
Tools and Components:
●
OpenStack Release: Kilo
●
Host Operating System: RHEL 7.1
●
OpenStack Package Repository: Redhat Distributed OpenStack (RDO)
●
Hypervisor: KVM
●
Database: MariaDB
●
Message Queue: Qpid
●
Networking Service: OpenStack Networking - Neutron
●
Tenant Network Separation: VLAN
●
Image Service (Glance) Backend: GlusterFS

|
●
Identity Service (Keystone) Driver: SQL
●
Block Storage Service (Cinder) Backend: GlusterFS

|
Reasons of Choosing the Tools

|
Redhat Enterprise Linux – RHEL:
●
An operating system that can run on all of the physical nodes
●
Reliability
●
Long-term support
●
Certified testing
●
Hardened

|
Redhat Distributed OpenStack – RDO:
●
Easy way to download, install and deploy
●
Most current OpenStack release in repository
●
Packaged for RHEL as host operating system

|
Kernel-based Virtual Machine – KVM:
●
Supported hypervisor of choice for Red Hat Enterprise Linux
●
Most compatible hypervisor with RHEL and its kernel
●
Feature complete
●
Open source
●
Free from licensing charges and restrictions

|
MariaDB:
●
Supported database of choice for Red Hat Enterprise Linux
●
As the database backend for all databases in the OpenStack environment
●
Open source
●
Scalable
●
Well memory handling

|
Neutron:
●
Sophisticated networking functionality
●
Layer 2 (L2) network segregation
●
Provider networks

|
Virtual Local Area Network - VLAN:
●
Broadcast control
●
Security control
●
Physical layer transparency

|
GlusterFS – GFS:
●
Scalability
●
Add more storage nodes easily
●
Cost effective
●
An alternative to an expensive storage array

|
Node Types

|
Node Types:
A node is a physical machine that is provisioned with an operating system, and
running a defined software stack on top of it.
●
Controller
●
Compute
●
Storage
●
Network
●
Management

|
Controller Node:
Controller nodes are responsible for running the management software services
needed for the OpenStack environment to function. These nodes:
●
Provide the front door that people access as well as the API services that all other
components in the environment talk to.
●
Run a number of services in a highly available fashion, utilizing Pacemaker and
HAProxy to provide a virtual IP and load-balancing Disks functions so all controller
nodes are being used.

|
●
Supply highly available “infrastructure” services, such as MySQL and Qpid, that
underpin all the services.
●
Provide what is known as “persistent storage” through services run on the host
as well. This persistent storage is backed onto the storage nodes for reliability.

|
Compute Node:
Compute nodes run the virtual machine instances in OpenStack. They:
●
Run the bare minimum of services needed to facilitate these instances.
●
Use local storage on the node for the virtual machines so that no VM migration
or instance recovery at node failure is possible.

|
Storage Node:
Storage nodes store all the data required for the environment, including disk images
in the Image Service library, and the persistent storage volumes created by the Block
Storage service. Storage nodes use GlusterFS technology to keep the data highly
available and scalable.

|
Network Node:
Network nodes are responsible for doing all the virtual networking needed for
people to create public or private networks and uplink their virtual machines into
external networks. Network nodes:
●
Form the only ingress and egress point for instances running on top of OpenStack.
●
Run all of the environment’s networking services, with the exception of the
networking API service (which runs on the controller node).

|
Management Node (Optional):
Management nodes are used by internal administration staff only to provide a
number of basic system administration functions needed to get the environment up
and running and to maintain the hardware, OS, and software on which it runs.
These nodes run services such as provisioning, configuration management,
monitoring, or GlusterFS management software. They are not required to scale,
although these machines are usually backed up.

|
Network Connections

|
OpenStack Internal Network:
●
OpenStack management functions and traffic
●
Including services needed for the provisioning of nodes ( pxe , tftp , kickstart )
●
Traffic between various OpenStack node types using OpenStack APIs and messages
●
Traffic for storage data to the storage layer underneath by the Gluster protocol
●
Physical nodes have at least one network interface in this network
●
Accessible from other VLANs on port 22

|
OpenStack Public Network:
●
IP addresses for public-facing interfaces on the controller nodes (which end users
will access the OpenStack services)
●
A range of publicly routable, IPv4 network addresses to be used by OpenStack
Networking for floating IPs. You may be restricted in your access to IPv4
addresses; a large range of IPv4 addresses is not necessary.
●
Routers for private networks created within OpenStack

|
OpenStack Public Network Connected To:
●
Controller nodes so users can access the OpenStack interfaces
●
Network nodes to provide VMs with publicly routable traffic functionality
●
Management machines node so that any management services that need to be
made public (such as system monitoring) can be accessed.

|
VM Traffic Network:
●
A closed network that is not publicly routable
●
Use as a private and internal network for traffic between VMs (Floating IPs - using a
different address space to the others to clearly define the separation)
●
Between the VMs and the network nodes that provide L3 routes out to the
public network
●
Only Compute and OpenStack Networking nodes need to beconnected to
this network.

|
Basic Node Deployment:

|
Performance Node Deployment:

|
Iran OpenStack Community

|
Stay in Touch and Join Us:
●
Home Page: OpenStack.ir
●
Meetup Page: Meetup.com/Iran-OpenStack
●
Mailing List: OpenStack-ir@Lists.OpenStack.org
●
Twitter: @OpenStackIR , #OpenStackIRAN
●
IRC Channel on FreeNode#OpenStack-ir

Roozbeh Shafiee
Iran OpenStack Community Manager
Roozbeh@OpenStack.ir
OpenStack.ir
Thank You
We need to work together to build a better community

Mastering OpenStack - Episode 02 - Simple Architectures

More Related Content

What's hot (20)

Viewers also liked (16)

Similar to Mastering OpenStack - Episode 02 - Simple Architectures (20)

Recently uploaded (20)

Mastering OpenStack - Episode 02 - Simple Architectures