Beyond brokering: Proactive Role of Cloud Federations in Resource Management

Size: px

Start display at page:

Download "Beyond brokering: Proactive Role of Cloud Federations in Resource Management"

Byron Bates
3 years ago
Views:

What does Contrail bstract?
What does the Portal model manage?

1 Beyond brokering: Proactive Role of Cloud Federations in Resource Management Massimo Coppola (CNR-ISTI)! contrail is co-funded by the EC 7th Framework Programme under Grant greement nr

2 Contrail in a Nutshell The Contrail Project develops an Open Source Cloud Federation Platform Trusted, secure distributed platform Horizontal integration of different IaaS providers SL management (multiple QoS aspects) Seamless use from multiple users and location Vertical integration physical resources, IaaS, Federated IaaS, ConPaaS

3 IaaS providers What do we mean with different providers? Infrastructure as a Service Data centers provide computation, storage and network distinct Clouds may have different interfaces, access rules and prices different service capabilities (due to HW/SW) Specific providers computation storage (long-term as opposed to short term) networking (special service conditions)

4 Contrail Iaas Federation Contrail Federation integrates in a common platform multiple Clouds, of public and private kind User identities, data, and resources are interoperable within the federation, thanks to common supports for authentication and authorization common mechanisms for policy definition, monitoring, and enforcing of all aspects of QoS : SL, QoP, etc. a common economic model

5 Contrail bstract rchitecture Coordinate deployment and management of application on multiple clouds Each app can exploit more providers pplication Federation PI Resource Storage Network Resource Public Cloud Storage

6 Federation = distribution Multiple access points Mechanism coordination and integration pplication pplication Federation PI + Fed. core Federation PI + Fed. core pplication Federation PI + Fed. core Resource Storage Network Resource Public Cloud Storage

7 Concrete rchitecture bstract View of a single ccess point Interactions, some modules not shown Interfaces sit on top of this core uth/utz mechanisms included Federation Core PEP SL Coordination SL Negotiation Proxy in first release PEP Watcher Manager Federation Runtime Manager Mapping PEP Java PI Dynamic information internal State User Management Registration Management Registration PEP PEP SL Template Repository Proxy in first release PEP dapters Provisioning Manager Driver N S V I G F PEP

8 Cloud interoperation Interoperation requirements over multiple providers SL trust security scalability monitoring ability deploy onto multiple distributed providers migration, coordinate deploy Very little detail today on SL, security, monitoring, access decentralization We focus on application deployment and management resource management

9 Cloud PI standards Interoperation of de-facto and evolving standards pplication description Cloud resource management SL description and management WS, OVF, OCCI... Standards have implementation variants due to incomplete specification incomplete implementation subset of features custom extensions

10 Models for interaction Portal model single access point to more resources (Clouds) manages whole lifecycle of each request (app) translates PIs, locates resources, emulates features, provides some guarantees Brokering model single access point for resource location and negotiation (auctioning) no responsibility after application deployment Federation model each access point looks the same common set of functionalities and mechanisms distributed implementation management is shared responsibility

11 Federations In a federation, distinct companies providing a service aggregate together User only needs to see and pay the final result each access point looks the same common set of functionalities and mechanisms distributed implementation, shared management responsibility real life examples: flight companies Cloud Federations multiple providers join forces to provide a larger service market doesn t often happen in practice larger Cloud players have their own distributed infrastructure

12 Cloud Federation model Besides interoperation mechanisms Provide guarantees = takes on risks s differ in features, reliability, cost model and prices fixed qualities and prices flexible qualities, price to be negotiated fixed qualities, price changes with availability different feature provided Federated support translates features and enforces or grants the associated SLs Risk evaluation and proactive risk mitigation is needed for a viable federation business model Federation can be a 3 rd party: business margin! Real world examples stand for the approach

13 Real Life Examples Power provisioning in electrical grids federations of producers, carriers, resellers to endusers simple contracts: flat rate and caps on utilization, simple QoS industrial contracts: different, non-linear rates, min/ max caps, complex QoS any complain goes to your reseller Underlying technology is complex and critical deviations in the power distribution can crash a whole national power grid still a major economic advantage is sought via competition and decentralization in power production and resale

14 Real Life Examples Travelling agencies mostly act as brokers popular metaphor on the web, travel service providers low-cost air carriers embrace this approach QoS compensation on the final provider main flight companies federate common infrastructure mechanism to provide services (booking, reservation) guarantees on connected resources flight-flight, flight-train commercial and legal agreements on QoS compensations (cancellation, delays, losses...) There is space also in the Cloud business for federated approaches

15 Interoperability PI and protocol translations User pplication Federation PI + Fed. core Federation PI + Fed. core Federation PI + Fed. core Resource Storage Network Resource Public Cloud Storage

16 Interoperability : PI and protocol PI and protocol translations User Translation from OVF to internal representation pplication Federation PI + Fed. core pplication splitting and modification Translation from internal representation to : WS, OVF and other formats Resource Storage Network Resource Public Cloud Storage

17 Interoperability: features and functions Contrail-specific providers developed in the project VEP Virtual Execution Platform Implement Contrail essential functions on top of existing open source Cloud providers OpenNebula, OpenStack Complemented with SL management Integrate with Contrail Security (uth/uthz) nother level of PI translation e.g. translate OVF to calls to OpenNebula PI

18 OVF toolkit Parsing and serialization from/to OVF deal with minor variants of OVF e.g. network parameter specification produce internal Java data structure Developed in the project to streamline internal development provide flexibility w.r.t. application representation formats Next step: parse/output WS and other formats

19 Mapping applications (or parts) OVF toolkit will integrate in the common data structure also information from SL gather full application description for the mapping phase develop features of contrail as a set of visitor and serializer patterns exploit the JgraphT graph library pplications represented as labelled, cost/ weighted graphs develop algorithms to split / map app graph to resources from simple location algorithms to application splitting allows evaluation of app. model in abstract

20 Mapping applications (or parts) Once the app representation is loaded match over providers known in the federation exploit static and dynamic information to evaluate feasibility and reliability of each one rank potential deployments on cost, performance No single match? recursively search for subsets of the application which can be conveniently mapped infer feasible global mappings hard multicriteria optimization in general

21 Contrail Innovations Federation = more than a simple broker, or portal Interoperability Heterogeneous providers Dynamically choosing best providers t deploy time and at runtime llow to combine providers Migration, elasticity Security and privacy framework Sophisticated QoS SL, QoP + other Via provider selection and integration Enforcement mechanisms Federation as a mediator and a 3 rd party

22 Some topics for collaboration Development, extension, exploitation of the OVF toolkit rosetta stone library Integration with more types of providers e.g. advanced QoS aware network supports for bandwidth reservation Heuristics for mapping and autonomic SL management of applications over multiple providers decomposition via distributed patterns/skeletons rules associated with patterns nalysis and research on Federation business models

23 Thank you! Contacts! ctivitiesdashboard/contrail! contrail is co-funded by the! EC 7th Framework Programme! Funded under: FP7 (Seventh Framework Programme)! rea: Internet of Services, Software & Virtualization (ICT )! Project reference: FP7-IST ! Total cost: 11,29 million euro! EU contribution: 8,3 million euro! Execution: From till ! Duration: 36 months! Contract type: Collaborative project (generic)!

Cloud Federations in Contrail

Cloud Federations in Contrail Emanuele Carlini 1,3, Massimo Coppola 1, Patrizio Dazzi 1, Laura Ricci 1,2, GiacomoRighetti 1,2 " 1 - CNR - ISTI, Pisa, Italy" 2 - University of Pisa, C.S. Dept" 3 - IMT Lucca,

Beyond brokering: Proactive Role of Cloud Federations in Resource Management

What does Contrail bstract?

What does the Portal model manage?