Standards in the RESERVOIR Project

Transcription

1 IaaS Cloud Interoperability through Standards in the RESERVOIR Project Fermín Galán Márquez Telefónica I+D The research leading to these results is partially supported by the European Community's Seventh Framework Programme (FP7/ ) under grant agreement n

2 The RESERVOIR Project Goal Develop an IaaS cloud computing open architecture, aiming at site federation and advanced features, such as Efficient placement Automatic elasticity Migration between sites Some facts 17M EC funding Three years long, from February 2008 to March partners from 9 countries More info on RESERVOIR at 2

3 Uses Cases worked on the project Multi-tier multi-vee services VEE = Virtual Execution Environment VEE ~ Virtual Machine (VM) Four uses cases demonstrated in the project Oracle Grid Engine SAP ERP egovernment Telco industry Front End 1 Back End 1 External network FW LB LB Back End 2 Front End 2 Back End 3 3

4 The Reservoir Architecture Service Provider Service Provider Site1 Manifest SMI Service Manager Site2 Site3 SLA SLA VEE Manager (VEEM) VHI VEE Host (VEEH) (e.g., Hypervisor, VJSC Host) Reservoir Site 4

5 The Reservoir Architecture Entry point to RESERVOIR cloud for SPs Holistic service management as sets of VEEs Provides placement transparency Service Provider Based in Telefónica s Claudia platform Service Provider Manifest SMI Site2 Site1 Manage VEEs Placement (policy engine) Implements Site3 federation Based in UCM s OpenNebula SLA Service Manager VEE Manager (VEEM) SLA Physically host the VMs Basically, an hypervisor Based in KVM (for conventional VMs) and VJSC Host (for VJSC VEEs) VHI VEE Host (VEEH) (e.g., Hypervisor, VJSC Host) Reservoir Site 5

6 The Reservoir Architecture Service Provider Service Provider Site1 Manifest SMI Service Manager Site2 Site3 SLA SLA VEE Manager (VEEM) VHI VEE Host (VEEH) (e.g., Hypervisor, VJSC Host) Reservoir Site 6

7 Why standards are needed in RESERVOIR? Three areas 1. Service packaging format So the same services that customers get from ISVs, deploy in their in-house IT infrastructure and/or other clouds, can also be seamlessly deployed in RESERVOIR 2. Management API for Service Providers (SMI) So the SP can manage RESERVOIR cloud as any other standard-based cloud, e.g. using the same management tools 3. Inter-component interfaces (, VHI) So different implementations of each one of the three middleware layers (SM, VEEM, VEEH) can be used 7

8 Service packaging format Independent ISV Service Provider Other IaaS clouds In-house Service Provider IT infrastructure 8

9 Service packaging format We have chosen the DMTF s Open Virtualization Format (OVF) Virtual Appliance (VA) packaging format In RESERVOIR, VA = Multi-tier multi-vee service Mature: released in February 2009, ANSI standard (ANSI INCITS ) since August 2010 Widely supported in mature virtualization products by the main vendors (VMware, Citrix, etc.) Also supported in emerging cloud standards (e.g. vcloud) RESERVOIR s advanced features have been implemented using OVF extensibility Rules governing service automatic elasticity Deployment time configuration (e.g. IP addresses) Placement constraints (e.g. country-based) 9

10 Service packaging format.vmdk,.iso,.xml, etc OVF package (.ova OVF descriptor (.ovf (XML Resource 1 Resource 2 Resource N File description <Reference>s Global meta-data sections Virtual System 1 System specific data sections RESERVOIR s extensions signs Manifest file (.mf (optional X.509 certificate (.cert (optional Virtual System M System specific data sections 10

11 Management API for Service Providers A lot of fragmentation in management APIs for cloud Each cloud ~ 1 different API There isn t any consolidated standard So, instead of choosing a non-existing standard we have opted to contribute to standardization body to define a standard management API for clouds TCloud API submission to DMTF (February 2002) Telefonica s very active participation in DMTF CMWG (Cloud Management Working Group) The main vendors are CMWG member VMware, Citrix, IBM, Microsoft, Oracle, 11

12 Management API for Service Providers A lot of fragmentation in management APIs for cloud Each cloud ~ 1 different vendor-specific API There isn t any consolidated standard So, instead of choosing a non-existing standard we have opted to contribute to standardization body to define a standard management API for clouds TCloud API submission to DMTF (February 2002) Telefonica s very active participation in DMTF CMWG (Cloud Management Working Group) Specification is expected by 2011 The main vendors are CMWG member VMware, Citrix, IBM, Microsoft, Oracle, 12

13 Management API for Service Providers TCloud API Based on VMware vcloud REST-based API Highly oriented to services Uses OVF as service representation mechanism Core functionalities Self-Provisioning (resources provisión: services, VMs,etc.) Self-Management (power on/off, take snapshot, etc.) Extension functionalities Self-Monitoring (pull/push) Self-Administration (manage Org/VDCs) 13

14 Management API for Service Providers fp7.eu/api/org/.eu/api/org/56 56/vdc/ /vdc/3/vapp/sales/fe /vapp/sales/fe1/hw/ /hw/5 Cloud Org Org Task VDC VDC VApp Net VM Snapshoot hw 14 Final Project Review, Taormina March 9, 2011

15 Inter-component interfaces SM-VEEM () Several alternatives have been explored OCCI TCloud API reduced set (VM-oriented) VEEM-VEEM () OCCI VEEM-VEEH (VHI) Probably the integration point where makes more sense an inter-component standard, given the heterogeneity of hypervisors Libvirt KVM, Xen, VMware ESX, and many others ( 15

16 RESERVOIR Standards Map Service Provider OVF Manifest SM MI TCloud API (services) Service Manager SLA OCCI TCloud API (VMs) / OCCI VH HI VEE Manager (VEEM) libvirt SLA OCCI VEE Host (VEEH) (e.g., Hypervisor, VJSC Host) Reservoir Site 16

17 Exploitation and Future Cooperation Continue evolving these standards in new projects FP7 4CaaST FP7 VISION NUBA (Spanish research program) Actively contributing to DMTF s main groups related with virtualization and cloud SVPC, CMWG Technology transfer to industrial products Telefónica s IaaS cloud products and services are based on the Service Manager evolution (Claudia platform), developed in RESERVOIR 17

18 18