1.

Cloud Band Benefits

Share resources: Resources are share among all tenants

Measured Service: Users are charged only for what they use

Location independent: Resource location and user location are independent

Easily accessed: browser-based user interface.

Scalable and Elastic:

-Service provider maintains a very large resource pool

-Resources appear unlimited to the user

-Resources can be allocated to users dynamically

Self-provisioning:

-provisioning of resources can be done by users without involving provider customer service.

-Change in resources may be happen automatically, without human input.

2. Virtualization Components

Landlord
Controls the system HW and network configuration.
Provides shared resources of the facility, power, cooling, and connectivity.
Management domain for the allocation of these resources.

Hypervisor= provides software to manage virtual machine access to the underlying hardware.
The hypervisor creates, manages, and monitors virtual machines. OpenStack Compute (nova)
supports many hypervisors to various degrees, including:

KVM =kernel-based virtual machine

LXC
QEMU
VMware ESX/ESXi
Xen
Hyper-V
Docker

VNF
Physical NE becomes a Virtual Network Function (VNF) within the NFV architecture
 The creation of VNFs is simplified with templated configuration and automatic
instantiation
NFV software approach reduces operation cost related to physical hardware (hardware
agnostic), provides more efficient physical hardware (servers) utilization, provides faster
deployment of NEs and reduces time to market overall

EMS: Element Management System --Se encarga de la gestion de los elementos de red

---------------------------------------------------------------------------------------------------------------------------------------
**Elementos del lado derecho del diagrama

MANO: Management and Orchestration.

MANO is the blue color block in the diagram below that includes three Managers:

1. Virtualized Infrastructure Manager (VIM).

2. VNF Manager (VNFM).
3. NFV Orchestrator (VNFO).

NFV Orchestrator: on-boarding of new Network Service (NS), VNF-FG and VNF Packages NS
lifecycle management (including instantiation, scale-out/in, performance measurements, event
correlation, termination) global resource management, validation and authorization of NFVI
resource requests policy management for NS instances

VNF Manager: lifecycle management of VNF instances overall coordination and adaptation
role for configuration and event reporting between NFVI and the E/NMS

Virtualised Infrastructure Manager (VIM): controlling and managing the NFVI compute,
storage and network resources, within one operators infrastructure sub-domain collection
and forwarding of performance measurements and events

OSS/BSS
(VNF Automation)

MANO

EMS
Orchestrator
CloudBand

Virtual Network Function

VNFM
(VNF)
DSC/vPCRF

Virtual Resources Virtual Infrastructure

Hypervisor Manager (VIM)
Compute/Storage/Network

HW Resources
Compute/Storage/Network
3. OpenStack Components

1. Orchestration API (Heat)

Heat es un motor de orquestacin para que los desarrolladores puedan automatizar el
despliegue de infraestructura. Esto permite que las configuraciones de cmputo, redes y
almacenamiento sean asignadas automticamente a una mquina virtual o aplicacin

2. Keystone (Identity service): Is used to authenticate/ authorize OpenStack services.

3. Glance (Image catalog): Is used to catalogue the VNF images. Manages the access to the images

***Nova can show info about images, and produce and instance from them, BUT ONLY glance
can add, delete, share or duplicate images.

4. Neutron (networking): Is used to create the networks needed for the VNF.
5. Nova (Compute): Is used to manage: create, start, stop, evacuate, etc the VMs.
6. Cinder (Block storage): Is used to provide storage support for the VMs (Boot devices, persistent
Storage devices)
Users interact with block storage by attaching volumes to their running VM instances.
Is used to manage volumes, a volume its block-level storage that we are making
available to VM instance, in other words its the read/write disk that those machines will
use.
Block storage uses the Logical Volume Manager or VLM for linux by default

*** Before block storage support was available, OpenStack virtual machines used so-called
ephemeral storage, which meant the contents of the virtual machine were lost when that VM
was shut down.

7. Swift (Object Storage): Provides storage for image

8. Horizon (Dashboard): OpenStack GUI
 4. Ejemplo tpico de funcionamiento: lanzar una instancia
Dependiendo de los componentes de cada cloud y de si estos estn en el mismo o diferentes equipos, o
incluso del nmero de estos componentes que hay en el cloud, se har ms o menos complejo el proceso
de lanzar una instancia, pero a grosso modo podramos resumirlo en los siguientes pasos:

I. Un usuario se autentica en Keystone, bien directamente o a travs del panel web Horizon. De
esta manera obtiene un token de sesin que le permitir realizar acciones con el resto de
componentes de OpenStack sin necesidad de volver a autenticarse y estas acciones estarn
limitadas por los permisos del rol que tenga asignado el usuario en Keystone.
II. El usuario solicita a Glance la lista de imgenes disponibles. Estas imgenes las tendr alojadas
glance directamente en el equipo que se ejecuta o bien sern objetos almacenados en Swift.
III. El usuario selecciona una imagen y solicita a Nova que la instancie, para lo que nova le pedir las
caractersticas de la instancia (ram, disco, vcpu, etc.) y una vez recibidas las caractersticas, elegir
el nodo del cloud ms adecuado para ejecutar la instancia.
IV. De la configuracin de la red virtual donde se encuentra situada la instancia se encarga Neutron
(antes conocido como Quantum), permitiendo no slo que se pueda acceder a la instancia desde
fuera, a travs de la denominada IP flotante, sino incluso de la configuracin de redes complejas.
Two types of hypervisors:

Type 1:

-Runs directly on the HW

-Total control of physical resources, more efficient

-Most common for IaaS

Type2:

-run over the host OS

-Other apps can run separate from the hypervisor

-host OS can manage input/output devices

-More typical for client devices

VMM-HI = Virtualization Machine Management and Host Infrastructure

VMM-HI is the virtualization manager (hypervisor+) on a HP c7000 chassis to provide the applications
with hardware independence and flexible configuration of Virtual Machines (VM).