Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update on Openstack Information #47

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Update on Openstack Information #47

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
171108a
Added Introduction
son-vyas Apr 5, 2018
ce8a8e0
Added control part
son-vyas Apr 5, 2018
b4135b3
Update control part
son-vyas Apr 5, 2018
f9af7fc
Added warning
son-vyas Apr 5, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
104 changes: 6 additions & 98 deletions chapter2/openstack_info.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,103 +1,11 @@
## What is OpenStack?
### Introduction to OpenStack

OpenStack is an free and open source cloud operating system, mostly
deployed as Infrastructure-As-Provider in case of ManageIQ, which
controls large pools of compute, storage, and networking resources
throughout a data center.
Hundreds of times you may have listened that ManageIQ is manager of managers. And these managers then eventually will be known as **components** or **providers**. Since this project is concerned with infrastruture management , that's why OpenStack comes into the picture with Infrastructure-As-Provider role within ManageIQ.

## Components of OpenStack
### How ManageIQ controls the integrated environment?

OpenStack has a modular architecture with various code names for its
components:
ManageIQ collects inventory information like request VMs, networking images from the OpenStack provider. ManageIQ uses REST API to communicate with OpenStack and further OpenStack uses REST API to communicate with its components.

1. Nova (Compute)
2. Swift (Object Storage)
3. Cinder (Block Storage)
4. Glance (Image Service)
5. Neutron (Networking)
6. Horizon (Dashboard )
7. Ceilometer (Telemetry)
8. Heat (Orchestration)
### Genuine warning

### Keystone (Identity Service)

It’s the main authentication and authorization service. It authorizes
the following:-

1. Users
2. Services
3. Endpoints

Keystone uses tokens for authorization and maintains Session state.

### Nova (Compute)

Nova compute provides a platform on which we are going to run our guest
machines. It’s the virtual machine provisioning and management module
that defines drivers that interact with underlying virtualization.

### Glance (Image Service)

In simple words glance is the Image Registry, it stores and Manage our
guest (VM) images, Disk Images, snap shots etc. Instances are booted
from the glance image registry. A feature of Glance is to store images
remotely so to save local disk space.

### Swift (Object Storage)

Swift offers cloud storage software, as they are not attached to
servers, they are individual addressable objects. It’s built for scale
and optimized for durability, availability, and concurrency across the
entire data set.

### Cinder (Block Storage)

Cinder is also one of the storage modules of OpenStack; It has the
performance characteristics of a Hard drive but much slower then Swift
and has low latency. Block Volume are created in swift and attached to
running Volumes for which you want to attach an extra partition or for
copying data to it. It survives the termination of an Instance. It is
used to keep persistence storage. Cinder Images are mostly stored on our
shared storage environment for readily availability. These Images can be
clones and snapshot which can be turned in to bootable images. Its
similar to Amazon Elastic block Storage.

### Neutron (Networking)

Neutron, the networking component which was formally called Quantum.
This component provides the software defined Networking Stack for
OpenStack. It Provides networking as a service. It gives the cloud
tenants an API to build rich networking topologies, and configure
advanced network policies in the cloud. It enables innovation plugins
(open and closed source) that introduce advanced network capabilities
which let anyone build advanced network services (open and closed
source) that plug into OpenStack tenant networks means that you can
create advance managed switches and routers. You can even create an
intelligent switch from a PC (Yes you can use it as a standalone
component) and use it to replace your managed switch or atleast make it
act as a backup Switch.

### Heat (Orchestration)

It creates a human and machine-accessible service for managing the
entire lifecycle of infrastructure and applications within OpenStack
clouds. It contains human readable templates with simple instruction
that is read by the Heat Engine. Heat along with ceilometer (explained
below) can create an auto-scaling the cloud.

### Telemetry (Ceilometer)

This module is responsible for metering Information. It can be used
generate bills and based on the statistics of usage. Its API can be used
with external billing systems. Administrators can create certain alarms
that are triggered based on performance statistics

### Horizon (Dashboard )

Horizon is the Dashboard to OpenStack. It provides a web based user
interface to OpenStack services including Nova, Swift, Keystone etc

## OpenStack Releases

Please do checkout the releases at
[releases.openstack.org](https://releases.OpenStack.org/)
Please do prior check the provider version and make sure it is compatible with your environment. Otherwise, things will mess and take a lot of time to come up on right track.