Open Source Private Cloud Software

• Eucalyptus
• Open Nebula
• Open Stack.
Eucalyptus
• Eucalyptus stands for Elastic Utility
Computing Architecture for Linking Your
Programs to Useful Systems.
• Eucalyptus
– Linux-based open-source software architecture for
cloud computing
– A storage platform that implements IaaS.
– Provides quick and efficient computing services.
– Designed to provide services compatible with
Amazon’s EC2 cloud and Simple Storage
Service(S3).
Important Features
• Images
– A good example is the Eucalyptus Machine Image which is a
module software bundled and uploaded to the Cloud.
• Instances
– When we run the picture and utilize it, it turns into an instance.
• Networking:
– Three modes:
• Static mode (allocates IP address to instances),
• System mode (assigns a MAC address and imputes the instance’s network
interface to the physical network via NC),
• Managed mode (achieves local network of instances).
• Access Control
– It is utilized to give limitations to clients. 
• Elastic Block Storage:
– It gives block-level storage volumes to connect to an instance. 
• Auto-scaling and Load Adjusting:
– It is utilized to make or obliterate cases or administrations
dependent on necessities.
Eucalyptus components
Eucalyptus components
• Node Controller : 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 (CC) manages one or more Node Controller and
Cloud Controller simultaneously. CCs gather information about a set
of NCs and schedules virtual machine (VM) execution on specific NCs
• 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 (CLC): 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.
Operation Modes Of Eucalyptus
• Managed Mode: Numerous security groups to users as the network
is large. Each security group is assigned a set or a subset of IP
addresses. Ingress rules are applied through the security groups
specified by the user. The network is isolated by VLAN between
Cluster Controller and Node Controller. Assigns two IP addresses
on each virtual machine.
• Managed (No VLAN) Node: The root user on the virtual machine
can snoop into other virtual machines running on the same
network layer. It does not provide VM network isolation.
• System Mode: A MAC address is assigned to a virtual machine
instance and attached to Node Controller’s bridge Ethernet device.
• Static Mode: Similar to system mode but has more control over
the assignment of IP address. MAC address/IP address pair is
mapped to static entry within the DHCP server. The next set of
MAC/IP addresses is mapped.  
Advantages Of The Eucalyptus Cloud

1. Eucalyptus can be utilized to benefit both the eucalyptus

private cloud and the eucalyptus public cloud.
2. Examples of Amazon or Eucalyptus machine images can be
run on both clouds.
3. Its API is completely similar to all the Amazon Web Services.
4. Eucalyptus can be utilized with DevOps apparatuses like
Chef and Puppet.
5. It allows users to deliver their own data centers into a
private cloud.
OpenNebula
• OpenNebula is a cloud computing platform
for managing heterogeneous distributed
data center infrastructures.
• The OpenNebula platform manages a data
center's virtual infrastructure to build
private, public and hybrid implementations
of Infrastructure as a Service
• Free and open-source software
OpenNebula Internal Architecture
Internal architecture: Basic components

• Host:
– Physical machine running a supported hypervisor.
• Cluster:
– Pool of hosts that share datastores and virtual networks.
• Template:
– Virtual Machine definition.
• Virtual Machine:
– Instantiated Template. A Virtual Machine represents one
life-cycle, and several Virtual Machines can be created from
a single Template.
• Image:
– Virtual Machine disk image.
Internal architecture …
• 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.
OpenNebula Deployment Model
• The OpenNebula Project's deployment
model
– A front-end (master node)
– Hypervisor enabled hosts (worker nodes)
– Datastores
– A physical network
Front-end machine / master node
• OpenNebula is installed.
• Executes all the OpenNebula services.
• Services
– the management daemon (oned),
– scheduler (sched),
– the web interface server (Sunstone server)
• These services are responsible for queuing, scheduling, and
submitting jobs to other machines in the cluster.
• Manages the entire system.
– Adding virtual machines
– Monitoring the status of virtual machines
– Hosting the repository
– Transferring virtual machines when necessary
Hypervisor enabled-hosts
• The worker nodes
• Provide the actual computing resources needed
for processing all jobs submitted by the master
node.
– Hypervisors used are Vmware, Xen, or KVM.
• Virtualization hosts are the physical machines
that run the virtual machines and various
platforms can be used with OpenNebula.
• A Virtualization Subsystem interacts with these
hosts to take the actions needed by the master
node.
Storage/datastores
• Hold the base images of the Virtual Machines.
• The datastores must be accessible to the front-end;
– Done using NAS, SAN, or direct attached storage.
• Three different datastores
– System datastores
• Hold the images used for running the virtual machines.
– Image datastores
• Store the disk image repository.
• Images from the image datastores are moved to or from the system
datastore when virtual machines are deployed or manipulated.
– File datastores
• For regular files and is often used for kernels, ram disks, or
context files.
Physical networks
• Physical networks are required to support the
interconnection of storage servers and virtual machines
in remote locations.
• It is also essential that the front-end machine can
connect to all the worker nodes or hosts.
• Two physical networks
– Service network
• For OpenNebula front-end daemons to access the hosts in
order to manage and monitor the hypervisors, and move
image files.
– Instance network.
• Network allows the virtual machines to connect across
different hosts.
Open Source Private Cloud Software

• Eucalyptus
• Open Nebula
• Open Stack.
OpenStack
• OpenStack is a collection of open source software modules and tools
that provides a framework to create and manage both public cloud and
private cloud infrastructure.
• OpenStack delivers infrastructure-as-a-service (IaaS) functionality
• It pools, provisions and manages large concentrations of compute,
storage and network resources.
• These resources, which include bare metal hardware, virtual machines
(VMs) and containers, are managed through application programming
interfaces (APIs) as well as an OpenStack dashboard
• Other OpenStack components provide orchestration, fault management
and services intended to support reliable, high availability operations.
• Businesses and service providers can deploy
– OpenStack on premises (in the data center to build a private cloud),
– in the cloud to enable or drive public cloud platforms,
– at the network edge for distributed computing systems.
OpenStack
• OpenStack® is an open source
software platform for private clouds
and public clouds.
• As an Infrastructure as a Service
(IaaS) platform, OpenStack enables
companies to easily and efficiently add
servers, storage and networking
components to their cloud.
What does OpenStack do?
• To create a cloud computing environment,
an organization typically builds off of its
existing virtualized infrastructure, using a
well-established hypervisor such as VMware
vSphere, Microsoft Hyper-V or KVM.
• However, cloud computing offers more than
just virtualization -- a public or private cloud
provides extensive provisioning, lifecycle
automation, user self-service, cost reporting
and billing, orchestration and other features.
OpenStack Architecture
OpenStack components
1. Keystone - Identity Service
2. NOVA - cloud computing fabric controller
3. Glance – Image service
4. Swift - Object Storage service
5. Neutron - Network Service
6. Cinder - Block Storage (Volume) Service
7. Horizon - Dashboard
8. Heat - Orchestration
9. Ceilometer - Monitoring and Metering
10.TripleO - Deployment
11.Manila - File storage
• Keystone
– Provides identity services for OpenStack.
– Common authorization framework
– Manages users, tenants and roles
– A central list of users/permissions
mapped against OpenStack services.
– Provides multiple means of access.
– Pluggable backends (SQL, PAM, LDAP,
IDM, etc)
NOVA
– Cloud computing fabric controller, main part
of an IaaS system.
– It is designed to manage and automate pools
of computer resources
– Core compute service comprised of
• Compute Nodes – hypervisors that run virtual
machines
– Supports multiple hypervisors KVM, Xen, LXC, Hyper-
V and ESX
• Distributed controllers that handle scheduling,
API calls, etc
– Native OpenStack API and Amazon EC2 compatible API
• Glance
– provides image services to OpenStack.
– Stores and retrieves disk images (virtual
machine templates)
– Supports Raw, QCOW, VMDK, VHD, ISO,
OVF & AMI/AKI
– Backend storage : Filesystem, Swift,
Gluster, Amazon S3
• Swift
– Object Storage service
– storage system for objects and files.
– Provides simple service for storing and
retrieving arbitrary data
– Users refer to a unique file identifiers:
OpenStack decides where to store/back-up
etc.
– Modeled after Amazon's S3 service
– Native API and S3 compatible API
Neutron
– Network Service
– provides the networking capability for
OpenStack.
– Provides framework for Software Defined
Network (SDN)
– Plugin architecture
– Allows integration of hardware and software
based network solutions
• Open vSwitch, Cicso UCS, Standard Linux Bridge,
Nicira NVP
Cinder
– Block storage component, analogous to
the traditional access on a disk drive.
– Provides block storage for virtual
machines (persistent disks)
– Similar to Amazon EBS service
– Plugin architecture for vendor extensions
• eg. NetApp driver for Cinder
Horizon
– The dashboard behind OpenStack.
– The only native graphical interface to
OpenStack.
– Provides simple self service UI for end-
users
– Basic cloud administrator functions
• Define users, tenants and quotas
• No infrastructure management
• HEAT : OpenStack Orchestration
– The orchestration component of OpenStack.
– Users can store the requirements of a cloud
application in a file.
– Defines what resources are necessary for the
application.
– Provides template driven cloud application
orchestration
• Modeled after AWS CloudFormation
– Targeted to provide advanced functionality such
as high availability and autoscaling
• Ceilometer :
– Goal: To provide a single infrastructure to
collect measurements from an entire OpenStack
infrastructure; eliminate need for multiple
agents attaching to multiple OpenStack projects
– Ceilometer: provides telemetry services.
– Metering, monitoring and reporting.
– Allows OpenStack to provide billing services to
users.
– provides extensibility
• Deployment (TripleO)
– Installing, upgrading and operating Openstack using Openstack’s own
cloud facilities (nova, neutron and heat)
– Continuous integration and deployment testing at the bare metal layer
(Ironic)
• File storage (Manila)
– Shared filesystem as a service
– NFS, Cifs and others
OTHER COMPONENTS
• Database Service (Trove)
• Bare metal (Ironic)
• Raksha (Backup)
• Queue service (Marconi)
• Common Libraries (Oslo)
Why Use OpenStack?
• Cost Savings /Affordable
– OpenStack software is free and open source to help users avoid vendor
lock-in with expensive hardware.
• Cloud Options
– Deploy OpenStack as a public, private or hybrid cloud.
– The stack’s key components include compute, storage, networking,
identity services and image services.
• Scalability
– Users can deploy virtual machines, apps and other resources easily and
quickly, scaling their operations up and down as their needs change.
• Flexibility
– Because OpenStack is an open source project, its code can be accessed
and changed based on needs.
– Users often share these modifications so that everyone benefits from a
worldwide community of users.
Why Use OpenStack? …
• Reliable.
– With almost a decade of development and use, OpenStack
provides a comprehensive and proven production-ready
modular platform upon which an enterprise can build and
operate a private or public cloud.
– Its rich set of capabilities includes scalable storage, good
performance and high data security, and it enjoys broad
acceptance across industries.
• Vendor-neutral.
– Because of OpenStack's open source nature, some
organizations also see it as a way to avoid vendor lock-in,
as an overall platform as well as its individual component
functions.
Cons
What are the cons of OpenStack?
• Complexity.
– Because of its size and scope, OpenStack requires an IT staff with
significant knowledge to deploy the platform and make it work.
– In some cases, an organization might require additional staff or a
consulting firm to deploy OpenStack, which adds time and cost.
• Support.
– As open source software, OpenStack is not owned or directed by
any one vendor or team.
– This can make it difficult to obtain support for the technology,
beyond the open source community.
• Consistency.
– The OpenStack component suite is always in flux as new
components are added and others are deprecated.