0% found this document useful (0 votes)
52 views14 pages

OpenStack (Autosaved)

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
52 views14 pages

OpenStack (Autosaved)

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

OpenStack

• OpenStack is a free, open standard cloud computing platform.


• It is mostly deployed as infrastructure-as-a-service in both public and private
clouds where virtual servers and other resources are made available to users.
• OpenStack is a cloud operating system that controls large pools of compute,
storage, and networking resources.

Why would I want to use OpenStack?


• Doesn’t have to purchase any service, rather I can build the software development
niche all by myself based on requirements
• OpenStack is completely free under APACHE 2.0 agreement.
• OpenStack has great industry support, it was developed by NASA.
• OpenStack has widely adopted across the IT community.
How does OpenStack work?

In principle, OpenStack agregates physical resources into one big pool and allocates virtual
resources out of this pool to users who can request them on-demand through a self-service portal
or application programming interfaces (APIs). But OpenStack itself does not handle
virtualisation. Instead, it leverages the existing virtualisation technologies. Therefore, OpenStack
is more like a wrapper around traditional virtualisation tools, enabling cloud-native capabilities.
The OpenStack components
• OpenStack's architecture is made up of numerous open source projects. These projects are used to
set up OpenStack's undercloud and overcloud—used by sys admins and cloud users, respectively.
Underclouds contain the core components sys admins need to set up and manage end users'
OpenStack environments, known as overclouds.

• There are 6 stable, core services that handle compute, networking, storage, identity, and images
while more than a dozen optional ones vary in developmental maturity. Those 6 core services are
the infrastructure that allows the rest of the projects to handle dashboarding, orchestration, bare-
metal provisioning, messaging, containers, and governance.
1. Nova
2. Neutron
3. Swift
4. Cinder
5. Keystone
6. Glance
The OpenStack components
1. Nova : Nova is the primary compute engine of OpenStack, responsible for instance scheduling,
creation and termination. In order to ensure widespread interoperability, Nova supports a wide
range of hypervisors. Nova is a full management and access tool to OpenStack compute
resources—handling scheduling, creation, and deletion.

2. Neutron: Neutron provides network connectivity between OpenStack instances, enabling multi-
VM deployments. For this purpose, Neutron uses various software-defined networking (SDN)
technologies, including Open Virtual Network (OVN), Open vSwitch (OVS), Juniper Contrail,
Cisco ACI, etc. Neutron connects the networks across other OpenStack services.

3. Swift: Swift is another storage component that provides a highly available and scalable object
storage service similar to Amazon S3. It enables storing and retrieving unstructured data objects
using a RESTful API for both OpenStack services and instances running on the cloud.Swift is a
highly fault-tolerant object storage service that stores and retrieves unstructured data objects
using a RESTful API.
The OpenStack components

4. Cinder: Cinder is a storage component that is responsible for provisioning, management and
termination of persistent block devices. Those can be later attached to the instances running on
OpenStack to enable persistent block storage. Cinder provides persistent block storage accessible
through a self-service API.

5. Keystone: Keystone serves as an identity service, providing authentication and authorization


functions for the users in order to enable multi-tenancy. Keystone can be easily integrated with
external identity systems, such as lightweight directory access protocol (LDAP) or Active Directory.
Keystone authenticates and authorizes all OpenStack services. It's also the endpoint catalog for all
services.

6. Glance: Glance is an image service, responsible for uploading, managing and retrieving cloud
images for instances running on OpenStack. Glance works across a variety of stores to provide the
most convenient location of images for organisations. Glance stores and retrieves virtual machine
disk images from a variety of locations.
What can I do with OpenStack?
• Private clouds
Private cloud distributions run on OpenStack can provide more substantial benefits than private
clouds built using custom code. IDC evaluated the value of Red Hat OpenStack Platform for private
clouds and found that organizations realized annual benefits of $ 6.81 million.

• Public clouds
OpenStack is the leading open source option for building public cloud environments. Whether your
company is a multibillion-dollar publicly traded enterprise or a startup, you can use OpenStack to set
up public clouds with services that compete with major public cloud providers.
Different ways to install OpenStack

1. Devstack
DevStack is a series of extensible scripts used to quickly bring up a complete OpenStack
environment based on the latest versions of everything from git master. It is used interactively as a
development environment and as the basis for much of the OpenStack project’s functional testing.
Devstack doesn’t care about persistence. After a reboot, the Devstack cloud is not in a usable state.
2. Microstack
It is a more polished product, with better user-friendliness. Devstack is a bit rough. On the other
hand, Microstack seems to be a bit shrink –wrapped with much less configuration options than
Devstack.
Commands to install OpenStack through
Microstack :

1. sudo snap install microstack --beta


2. snap list microstack
3. sudo microstack init --auto --control
4. microstack.openstack –version

To access the Dashboard


https://<your-ip>

To get password
sudo snap get microstack config.credentials.keystone-password

On browser :
Enter “admin” as the username
1. Create the Network

• Enter Network name “OpenStack network”


• Enter the network type “IPv4”
• Enter the network category “Unshared”
• Enter the subnet name “Subnet 1”
• Enter the subnet network address “192.168.1.0/24”
2. Creating the instances

• Click on Compute
• Click on Image
• Hover over the right side of the Cirros
• Click on Launch instance
• Enter the instance name and instance details

• Click on Flavours and select m1 tiny


• Then click on Networks tab, select the previously created network and launch the instance
3. Creating Routers:

• Click on Network
• Click on Routers
• Name router as “router-1”
• Select network as ‘openstacknetwork-1’
• Click on Create
• Click on Routers and name this router as
‘router-2’
• Click on create
• Now you should be able to see two routers
4. Manage Floating IP Associations
• Assign each address some IP address
• Associate to instance 2

5. Test the network


• Click on Instances
• Observe the IP address of Instance 2
• Click on the instance 1
• Click on console
• Login
• Ping instance 2 from instance 1 using command
• ‘ping <instance1-IP>
• Example : ‘ping 192.168.2.168’
• If ping is successful, one should be able to see that data packets are being transferred.

You might also like