openstack as an infrastructure

OpenStack as an Infrastructure(Episode 1)

Personal Profile:

● Roozbeh Shafiee

● Cloud and Virtualization Architect

● Technical Manager at innfinision Cloud Solutions

● [email protected]

● Innfinision.net

innfinision Cloud Solutions:

● Providing Cloud, Virtualization and Data Center Solutions

● Developing Software for Cloud Environments

● Providing Services to Telecom, Education, Broadcasting & Health Fields

● Supporting OpenStack Foundation as the First Iranian Company

● First Supporter of IRAN OpenStack Community

OpenStack as an Infrastructure innfinision.net

● Cloud Computing Compared to Virtualization

● What is OpenStack?

● Why OpenStack?

● Requirements Before Beginning

● OpenStack Components

● OpenStack Architectures

Agenda:

Cloud Computing Compared to

Virtualization

innfinision.netOpenStack as an Infrastructure

Cloud Computing Compared to Virtualization


● On-Demand Self-Service

● Broad Network Access

● Resource Pooling

● Rapid Elasticity or Expansion

● Measured Service

● Virtualized Infrastructure

● Shared Computing Resources

● On-Demand Service Delivery

● Scalability

● Automation

● Variety of Service Models

What is OpenStack?


What is OpenStack


● Founded by Rackspace and NASA in 2009

● The most favorite open source project after Linux kernel

● More than 1400 developer and contributor from 80 country

● More than 140 user community around the world

● OpenStack foundation established in 2010 to support this project

● HP, Red Hat and Mirantis are top company contributors in Juno release

● More than 80% of source code is based on Python

● Released Under Apache 2.0 license

● Designed for Public, Private and Hybrid Clouds

Why OpenStack?


Why OpenStack?


● Scale out architecture

● Designed for failure

● Off-the-shelf hardware

● Free from licensing fees

● Wide range of certified hardware

● No vendor lock-in

● Open API

● Open Formats

● Open Source

● Optional support available

● Predictable release cycle

Requirements Before Beginning


Before everything you should know Linux, Virtualization, Network and

Hardware concepts

● Dominance on Red Hat RHCVA or LPIC-3 Virtulization and HA Topics

● Linux Administration Skills

● Database Concepts

● Basic Network Knowledge

● Hardware Maintenance Experience


OpenStack Components


In lastest release of OpenStack, Juno There are 11 components to build

and manage an OpenStack as an infrastructure.

● Compute (Nova)

● Object Storage (Swift)

● Block Storage (Cinder)

● Networking (Neutron)

● Dashboard (Horizon)

● Identity Service (Keystone)


● Orchestration (Heat)

● Telemetry (Ceilometer)

● Database Service (Trove)

● Image Service (Glance)

● Data Processing (Sahara)

Compute (Nova):


● Conceptually similar to Amazon EC2

● Can leverage multiple hypervisors (Xen, KVM, vSphere/ESXi, Hyper-V)

● Made up of several sub-components (nova-api, nova-compute,

● nova-schedule)

Object Storage (Swift):


● Think of it as similar to Amazon S3

● Provides distributed object storage

● Supports the OpenStack Object API as well as raw HTTP

● Authentication is handled via OpenStack Identity (typically)

Block Storage (Cinder):


● Can be compared in concept to Amazon EBS

● Provides block storage functionality to instances running on Compute

● Recall that instances are stateless

● Block Storage provides persistent storage for instances

● Similar to Compute, it has several sub-components (cinder-api, cinder-

volume, cinder-scheduler)

● Leverages storage drivers to interact with underlying storage

platforms

Networking (Neutron):


● Provides “network as a service” functionality

● Allows for the programmatic creation of (potentially complex) per-

tenant networks

● Uses a plug-in architecture; plugins exist for a number of different

back-end implementations, including Nicira NVP, Open vSwitch (OVS),

Linux bridge, Cisco, and others

● Has essentially replaced nova-network

Dashboard (Horizon):


● A web application that runs on Apache

● Provides a graphical user interface (GUI) for other OpenStack services

● Leverages the APIs of the other OpenStack services

Identity Service (Keystone):


● Provides policy and authentication services for other OpenStack

services

● Leverages a pluggable architecture that can support LDAP, SQL, and

other backend services

Orchestration (Heat):


● It is easier to roll back a failed deployment and ensure thorough

cleanup

● Administrators can delegate resource creation privileges to non-

administrative users

● Improvements included implementation of new resource types and

improved scalability

Telemetry (Ceilometer):


● Reporting increases in performance this cycle as well as efficiency

improvements including metering of some types of networking

services such as load balancers, firewalls and VPNs as a service.

Database Service (Trove):


● The database service went through its second release cycle in Juno

● MySQL replication

● Mongo clustering, Postgres, and Couchbase.

Image Service (Glance):


● This can be compared to Amazon’s AMI catalog

● Provides image storage, image retrieval, and image discovery services

● These images are leveraged to launch instances (VMs)

● Can leverage the Object Store (“Swift”) or other storage platforms,

including Amazon S3, filesystems, and HTTP

Data Processing (Sahara):


● Automates provisioning and management of big data clusters using

Hadoop and Spark

● Big data analytics are a priority for many organizations and a popular

use case for OpenStack

● This service lets OpenStack users provision needed resources more

quickly

OpenStack Architectures


Different architectures for different purposes! In total there are 8

architectures to design a cloud infrastructure based on OpenStack.


● General purpose: A cloud built with common components that

should address 80% of common use cases.

● Compute focused: A cloud designed to address compute intensive

workloads such as high performance computing (HPC).


● Storage focused: A cloud focused on storage intensive workloads

such as data analytics with parallel file systems.

● Network focused: A cloud depending on high performance and

reliable networking, such as a content delivery network (CDN).

● Multi-site: A cloud built with multiple sites available for application

deployments for geographical, reliability or data locality reasons.


● Hybrid cloud: An architecture where multiple disparate clouds are

connected either for failover, hybrid cloud bursting, or availability.

● Massively Scalable: An architecture that is intended for cloud

service providers or other extremely largeinstallations.

● Specialized Cases

General Purpose:


● Most common

● Base for all other specialized Architectures

● No predefined use, so need to support all potential cases

● Balanced loads across all Cloud components

Compute Focused:


● High performance computing (HPC)

● Big data analytics using Hadoop or other distributed data stores

● Continuous integration/continuous deployment (CI/CD)

● Platform-as-a-Service (PaaS)

● Signal processing for network function virtualization (NFV)

Storage Focused:


● Active archive, backups and hierarchical storage management

● General content storage and synchronization

● Data analytics with parallel filesystems

● Persistent block storage

● Operating system and application image store

● Media streaming

● Databases

● Content distribution

● Cloud storage peering

Network Focused:


● Content delivery network

● Network service offerings

● High speed and high volume transactional systems

● Virtual desktop infrastructure (VDI)

● Voice over IP (VoIP)

● Video Conference or web conference

● High performance computing (HPC)

Multi-Site:


● An organization with a diverse geographic footprint.

● Geo-location sensitive data.

● Data locality, in which specific data or functionality should be close

to users.

Hybrid Cloud:


● Bursting from a private cloud to a public cloud

● Disaster recovery

● Development and testing

● Federated cloud, enabling users to choose resources

from multiple providers

● Hybrid clouds built to support legacy systems as

they transition to cloud

Massively Scalable:


● Massively scaleable clouds for any purpose

Specialized Cases:


● Cloud environments based on Multi-Hypervisor

● SDN

● Desktop as a Service

● OpenStack on OpenStack

● Specialized hardware

Roozbeh Shafiee

[email protected]

innfinision.net

Thank you

openstack as an infrastructure

Technology

infrastructurewhy openstack

world openstack foundation

hybrid cloudswhy openstack

cloud environments

netinnfinision cloud

roozbeh shafiee cloud

subcomponents novaapi

favorite open source