4361602 226480316018

Prcatical-1
Aim-Sketch out and analyze the architecture of Openstack/ Eucalyptus/
OpenNebula/ KVM and identify different entities to understand the structure of
it.

❖ OpenStack
➢ Introduction
OpenStack is an open-standard and free platform for cloud computing. Mostly, it is deployed
as IaaS (Infrastructure-as-a-Service) in both private and public clouds where various virtual
servers and other types of resources are available for users. This platform combines irrelated
components that networking resources, storage resources, multi-vendor hardware processing
tools, and control diverse throughout the data center. Various users manage it by the
command-line tools, RESTful web services, and web-based dashboard.

➢ Architecture of OpenStack
OpenStack contains a modular architecture along with several code names for the
components.

• Nova (Compute):
o Function: Manages and provisions large networks of virtual machines (VMs).
o Role: Acts as the primary compute engine, responsible for deploying and
managing VMs across the cloud infrastructure.

• Swift (Object Storage):

o Function: Provides a scalable storage system for unstructured data objects.

1
4361602 226480316018

o Role: Handles the storage and retrieval of data objects via a RESTful API,
ideal for data that do not require a fixed schema.

• Cinder (Block Storage):

o Function: Delivers persistent block storage to running instances.
o Role: Works like traditional hard drives, providing storage that can be
attached to VMs for data persistence.

• Neutron (Networking):
o Function: Manages networking and IP addressing within the cloud.
o Role: Ensures that cloud resources are connected, offering network
connectivity as a service between interface devices managed by OpenStack
services.

• Keystone (Identity Service):

o Function: Provides authentication and high-level authorization.
o Role: Manages user authentication, access control, and service discovery,
ensuring secure access to OpenStack services.

• Glance (Image Service):

o Function: Stores and retrieves virtual machine disk images.
o Role: Allows users to discover, register, and retrieve virtual machine images,
supporting a variety of back-end stores.

• Horizon (Dashboard):
o Function: Provides a web-based user interface.
o Role: Allows administrators and users to manage OpenStack resources and
services through a graphical interface, simplifying cloud operations.

➢ Advantages of using OpenStack

• It boosts rapid provisioning of resources due to which orchestration and scaling up
and down of resources becomes easy.
• Deployment of applications using OpenStack does not consume a large amount of
time.
• Since resources are scalable therefore they are used more wisely and efficiently.
• The regulatory compliances associated with its usage are manageable.
•
➢ Disadvantages of using OpenStack
• OpenStack is not very robust when orchestration is considered.
• Even today, the APIs provided and supported by OpenStack are not compatible with
many of the hybrid cloud providers, thus integrating solutions becomes difficult.
• Like all cloud service providers OpenStack services also come with the risk of
security breaches.
•
➢ List of key entities in OpenStack
• Keystone (Identity Management): Users, Projects, Roles, Service Tokens.
• Nova (Compute): Instances, Key Pairs, Hypervisors.
• Cinder (Block Storage): Volumes, Snapshots.

2
4361602 226480316018

• Neutron (Networking): Networks, Routers, Subnets, Floating IPs, Security Groups.

• Glance (Image Service): Images.
• Swift (Object Storage): Containers, Objects.
• Heat (Orchestration): Stacks.
• Ceilometer/Aodh (Telemetry and Alarming): Alarms, Telemetry data.

❖ Eucalyptus
Eucalyptus is an open-source cloud computing platform that provides Infrastructure-as-a-
Service (IaaS). It allows users to build private and hybrid clouds that are compatible with
Amazon Web Services (AWS) APIs. In Eucalyptus, the concept of entities refers to the key
components, resources, and objects within the cloud infrastructure. These entities are part of
the overall architecture and work together to manage the cloud's compute, storage, and
networking services.
❖ Eucalyptus Architecture

• Node Controller is the lifecycle of instances running on each node. Interacts with the
operating system, hypervisor, and Cluster Controller. It controls the working of VM
instances on the host machine.
• Cluster Controller manages one or more Node Controller and Cloud Controller
simultaneously. It gathers information and schedules VM execution.
• Storage Controller (Walrus) Allows the creation of snapshots of volumes. Persistent
block storage over VM instances. Walrus Storage Controller is a simple file storage
system. It stores images and snapshots. Stores and serves files using S3(Simple
Storage Service) APIs.
• Cloud Controller Front-end for the entire architecture. It acts as a Complaint Web
Services to client tools on one side and interacts with the rest of the components on
the other side.
➢ Eucalyptus Entities:

• Identity and Access Management: Users, Groups, Roles, Projects (Tenants).

• Compute Resources: Instances (VMs), Key Pairs.
• Storage: Images, Volumes (EBS), Snapshots, Walrus (Object Storage).
• Networking: Floating IPs, Virtual Networks, Subnets, Routers, Security Groups.
• Scalability and Availability: Elastic Load Balancer (ELB), Clusters, Nodes, Elastic IPs.

3
4361602 226480316018

• Cloud Management: Cloud Controller (CLC), Elastic Compute Service (ECS), Elastic Block
Store (EBS).

❖ OpenNebula

OpenNebula is a powerful, but easy-to-use, open source platform to build and manage
Enterprise Clouds. OpenNebula provides unified management of IT infrastructure and
applications, avoiding vendor lock-in and reducing complexity, resource consumption and
operational costs.

➢ Architecture of OpenNebula

• Host: Physical machine running a supported hypervisor.

• Cluster: Pool of hosts that share datastores and virtual networks.
• Template: Virtual Machine definition.
• Image: Virtual Machine disk image.
• Virtual Machine: Instantiated Template. A Virtual Machine represents one life-cycle,
and several Virtual Machines can be created from a single Template.
• Virtual Network: A group of IP leases that VMs can use to automatically obtain IP
addresses. It allows the creation of Virtual Networks by mapping over the physical ones.
They will be available to the VMs through the corresponding bridges on hosts. Virtual
network can be defined in three different parts:

1. Underlying of physical network infrastructure.

2. The logical address space available (IPv4, IPv6, dual stack).
3. Context attributes (e.g. net mask, DNS, gateway). OpenNebula also comes with a
Virtual Router appliance to provide networking services like DHCP, DNS etc.

➢ OpenNebula Entities:

• Users and Groups: Manage access and control through roles and permissions.
• Compute Resources: Virtual Machines (VMs), VM Templates, Clusters, Hosts.
• Storage: Datastores, Image Repository, Storage Drivers, Volumes.
• Networking: Virtual Networks, Virtual Switches, Network Interfaces, Security
Groups.
• Resource Management: Leases, Resource Pools, Schedules, Templates.
• Cloud Management: Sunstone UI, Cloud API, Orchestration (Flow).

4
4361602 226480316018

• Automation & Orchestration: Leases, Schedules, Flow for multi-step workflows.

❖ KVM

Kernel-based Virtual Machine (KVM) is a software feature that you can install on physical
Linux machines to create virtual machines. A virtual machine is a software application that
acts as an independent computer within another physical computer. It shares resources like
CPU cycles, network bandwidth, and memory with the physical machine. KVM is a Linux
operating system component that provides native support for virtual machines on Linux. It
has been available in Linux distributions since 2007.

➢ KVM Architecture

• Host OS (Linux Kernel): Provides virtualization support through KVM.

• KVM: Kernel module that provides the core hypervisor functionality.
• QEMU: User-space component that handles emulation of devices and virtual machine
management.
• Libvirt: Management layer that provides tools for creating, managing, and interacting
with virtual machines.
• Virtual Machines: The virtualized.

➢ Entities of KVM

• Host Machine: The physical hardware running the Linux OS and KVM.
• KVM Kernel Module: The core module enabling Linux to act as a hypervisor.
• QEMU: User-space emulator for device emulation and VM management.
• Libvirt: API and management toolkit for interacting with KVM.
• Virtual Machines (VMs): The virtualized operating systems running on the host.
• VM Images: Persistent disk images representing virtual machine storage.
• Virtual CPUs (vCPUs): Virtualized CPU resources allocated to VMs.
• Virtual Networks / Switches: Virtualized networking interfaces for communication.
• Virtio Devices: Paravirtualized I/O devices for high-performance communication.
• Management Tools: Utilities like virsh.