Cloud Training

19.10.2019
Kamalakannan Sanjeevan
Agenda
1. Cloud computing and virtualization
2. IAAS, PAAS and SAAS
3. Introduction to Openstack
4. Cloudband products
5. Understanding HLD, LLD and UAT for cloud project
6. Demo on cloud band products
 Cloud Computing

• Cloud Computing provides us a means by which we can access the

applications as utilities, over the Internet/Intranet. It allows us to create,
configure, and customize applications online.
• Cloud Computing is both a combination of software and hardware based
computing resources delivered on a network service.
• Cloud is differentiated into Deployment Model and Service models
 Types of Cloud and deployment models

• Public Cloud : The Public Cloud allows systems and services to be easily
accessible to the general public. Public cloud may be less secure because
of its openness.
• Private Cloud : The Private Cloud allows systems and services to be
accessible within an organization. It offers increased security because of its
private nature.
• Hybrid Cloud : The Hybrid Cloud is mixture of public and private cloud.
However, the critical activities are performed using private cloud while the
non-critical activities are performed using public cloud.
• Community Cloud : The Community Cloud allows systems and services to
be accessible by group of organizations.
Types of Cloud and Service models

1. Infrastructure as a Service (IaaS)

2. Platform as a Service (PaaS)

3. Software as a Service (SaaS)

 IaaS

Infrastructure as a Service (IaaS)

IaaS is the delivery of technology infrastructure as an on demand scalable

service.
IaaS provides access to fundamental resources such as physical machines,
virtual machines, virtual storage, etc.

• Usually billed based on usage

• Usually multi tenant virtualized environment
• Can be coupled with Managed Services for OS and application support
IaaS Examples
 PaaS

Platform as a Service (PaaS)

PaaS provides the runtime environment for applications,development &

deployment tools, etc
PaaS provides all of the facilities required to support the complete life cycle of
building and delivering web applications and services entirely from the Internet.

Typically applications must be developed with a particular platform in mind

• Multi tenant environments
• Highly scalable multi tier architecture
PaaS Examples
 SaaS

Software as a Service (SaaS)

SaaS model allows to use software applications as a service to end users.

SaaS is a software delivery methodology that provides licensed multi-tenant

access to software and its functions remotely as a Web-based service.

• Usually billed based on usage

• Usually multi tenant environment
• Highly scalable architecture
SaaS Examples
Cloud Computing vs Virtualization

• Cloud Computing is a model for enabling convenient, on-demand network

access to a shared pool of configurable computing resources (e.g., networks,
servers, storage, applications, and services) that can be rapidly provisioned
and released with minimal management effort or service provider
interaction.
• Virtualization is a Software that creates “separated” multiple images of the
hardware and software on the same machine. This makes possible to install
multiple OS, multiple software and multiple applications on the same
physical machine.
• Cloud is good for public use, other side IT companies use Virtualization for
cost-efficient data center setup.
Cloud Computing vs Virtualization
 Cloud Computing vs Virtualization

https://www.educba.com/cloud-computing-vs-virtualization/
 Cloud Computing vs Virtualization

https://www.educba.com/cloud-computing-vs-virtualization/
What is virtualization
• Virtualization is changing the
mindset from physical to
logical.
• What virtualization means is
creating more logical IT
resources, called virtual
systems, within one physical
system.
• It most commonly uses the
hypervisor for managing the
resources for every virtual
system. The hypervisor is a
software that can virtualize the
hardware resources.
Types of hypervisors
• Type 1 hypervisor: hypervisors run directly on the system hardware – A “bare metal” embedded
hypervisor.
– VMware ESX and ESXi, Microsoft Hyper-V, Citrix XenServer
• Type 2 hypervisor: hypervisors run on a host operating system that provides virtualization
services, such as I/O device support and memory management.
– VMware Workstation/Fusion/Player, VMware Server, Microsoft Virtual PC, Oracle VM
VirtualBox, KVM, QEMU, LXC
Openstack and its history
• Jointly founded in July 2010 by Rackspace and NASA with
merger of two projects:
– Swift object storage based on Rackspace's Cloud Files platform
– Nova based on Nebula compute platform

• Openstack is a set of software tools for building and

managing cloud computing platforms for public and private
clouds
• Openstack is managed by the openstack Foundation, a non-
profit organization that oversees both development and
community building around the project
• Openstack is the future of cloud computing backed by some
of the biggest companies

https://www.openstack.org/foundation/companies/
Openstack Services
• Keystone - Identity service. Used for authentication and authorization
• Glance - Image service. Stores images that will be used for
creating VM’s
• Nova - Compute service. Used to allocate resources for VM’s
• Neutron - Networking services. Used for creating networks, routers,
subnets, ports
• Cinder - Storage service. Block Storage service for providing volumes
to Nova virtual machines, Ironic bare metal hosts, containers.
• Heat - Orchestration. It implements an orchestration engine to
launch multiple composite cloud applications based on templates
• Horizon - GUI dashboard used to provide access to end user
Openstack component architecture
Openstack component architecture - contd
Neutron architecture
 Neutron – types of data center networks
• Management network - Used for internal communication between OpenStack
Components. The IP addresses on this network should be reachable only within the
data center.
• Guest network - Used for VM data communication within the cloud deployment. The IP
addressing requirements of this network depend on the OpenStack Networking plug-in
in use and the network configuration choices of the virtual networks made by the
tenant.
• External network - Used to provide VMs with Internet access in some deployment
scenarios. The IP addresses on this network should be reachable by anyone on the
Internet.
• API network - Exposes all OpenStack APIs, including the OpenStack Networking API,
to tenants. The IP addresses on this network should be reachable by anyone on the
Internet. This may be the same network as the external network, as it is possible to
create a subnet for the external network that uses IP allocation ranges to use only less
than the full range of IP addresses in an IP block.
Neutron service architecture
 Neutron services
Neutron Server – This component is the face of the complete environment. It has three
modules:
REST service – It accepts API requests from other components and exposes all
internal working details like subnets, ports etc
RPC service – Communicates with messaging bus and enables bidirectional
agent communication
Plugin – Collection of python modules that implement a standard interface, which
accepts and receives some standard API calls.

L2 agent – Runs on the compute nodes. It provides connections to new servers in

appropriate network segments. Eg. Ethernet and Switching. Linux Bridge and OVS work in L2

L3 agent – It runs on network node . It is responsible for static routing, IP forwarding, and
other L3 features like DHCP.

Routing services examples VPNaaS, LBaaS, FWaaS

 Networking Concepts in Neutron
Network: A network is an isolated L2 segment, analogous to a VLAN in the physical
networking world.

Subnet: This is a block of IP addresses and the associated configuration state. Multiple
subnets can be associated with a single network

Port: A port is a connection point to attach a single device, such as the NIC of a virtual
server, to a virtual network

Router: A router is a device that can route traffic between different subnets and networks.
Any subnets on the same router can talk to each other without a routing table if the security
groups allow the connection.
Pictorial representation of Neutron communication
 Network Types
Provider Networks - OpenStack administrators create provider networks and map them to
external physical network in a data centre. Network types that can be used as provider
networks are flat and VLAN

Tenant networks - To have proper connectivity between the projects, users would create
tenant networks.
Flat: In flat tenant networks all the created instances will be in the same network
which can be shared with the hosts if needed. It does not support VLAN tagging and other
network segregations.
VLAN: Using VLAN IDs users can create any number of tenant or provider
networks corresponding to VLANs in the same physical network. This makes the
communication between the instances across environment easy and effective
VXLAN and GRE Tunnels: VXLAN and GRE are encapsulation protocols that
create overlay networks to activate and control communication between compute
instances. A Networking router is required to allow traffic to flow outside of the GRE or
VXLAN tenant network. A router is also required to connect directly-connected tenant
networks with external networks, including the Internet
Network Types
OpenvSwitch
• OpenVSwitch(OVS) is a Software
based virtual Switch
• Each VM has at least one
virtual network interface cards
(vNICs) that are sharing
physical network interface
cards (pNICs) on the physical
host through vSwitch
Openstack Hardware Architecture
Cloudband Products

CBIS – Cloudband Infrastructure Software

CBAM – Cloudband Application Manager
CBND – Cloudband Network Director
CBIS

CloudBand Infrastructure Software is OpenStack(Iaas)

aligned and provides multi-purpose NFV infrastructure
(NFVI) and virtualized infrastructure manager (VIM)
support.
It virtualizes and manages compute, storage, and
network resources. It enables VNFs to run and ensures
that they meet strict robustness, performance, and
security requirements.
CBAM

CBAM automates VNF lifecycle management and

cloud resource management, and its standards based
APIs make it easy to work with any vendor’s VNF,
Element Management System (EMS), Virtualized
Infrastructure Manager (VIM) and NFV Orchestrator
(NFVO).
CBND

CloudBand Network Director is an NFV resource and

network service orchestrator. It manages virtual
resources across geo-distributed NFV infrastructure
nodes.
It visualizes and automates the lifecycle of network
services in the virtual domain, decomposing them into
VNFs and virtual links(VLs).
Cloudband Architecture
CBIS Logical Architecture
CBIS – Services running on different services
THANK YOU