Adopting the DSM paradigm: defining federation scenarios through resource brokers for experimentally driven research <br /...
Introduction <br />Experimentally driven research<br />An emerging paradigm for the Future Internet<br />Validating throug...
The Federation Scenario term<br />User realization of resource requirements<br />A well-defined specification of required ...
The key-role of resource brokers<br />A resource broker matches customer requested services and provider resources from th...
Federation of Resource Providers and Brokers<br />C. Tranoris - Univ. of Patras, Greece<br />API<br />API<br />Provider<br...
Federation of Resource Providers and Brokers<br />C. Tranoris - Univ. of Patras, Greece<br />API<br />API<br />API<br />Pr...
This work<br />Adopted DSM practices where systematic use of a Domain Specific Language (DSL) is involved<br />Defined a m...
The family of DSLs<br />OfficeDL to define a resource broker or a resource provider<br />Service Description Language(SDL)...
Prerequisites for Defining Federation Scenarios<br />A common model to capture the Federation domain<br />Seamless transit...
The need for a Federation meta-model<br />There is a need for defining federation scenarios in unambiguous ways <br />A fo...
Office meta-model<br />M2<br />M<br />M<br />Model To Model<br />Transformation<br />Other Office<br />Provider Z<br />Off...
Office meta-model<br />C. Tranoris - Univ. of Patras, Greece<br />Compute<br />officeA (broker)<br />officeA.comp1234<br />
C. Tranoris - Univ. of Patras, Greece<br />Office meta-model<br /><ul><li>A Contract between Offered Service and Offered R...
Office Model maintains an aggregation of promises! </li></li></ul><li>The OfficeDL<br />enables rapid prototyping of the O...
The Office meta-model<br />EMF<br />Office meta-model<br />implements<br />Office <br />Definition<br />Office A<br />C. T...
The OfficeDL<br />C. Tranoris - Univ. of Patras, Greece<br />
From service definitions to federation resources<br />SDL: Service Description Language<br />Describes an offered service:...
The Service Description Language SDL<br />C. Tranoris - Univ. of Patras, Greece<br />
The Resource Description Language RDL(RaDL)<br />C. Tranoris - Univ. of Patras, Greece<br />
Service Description Language<br />SDL<br />Office model<br />Resource Adapter<br />Description<br />Language<br />RADL<br ...
install<br />RAActivator.java<br />RAInstance.java<br />SampleService.java<br />PTM<br />RADL ecore<br />Meta-model<br />W...
Defining federation scenarios:Definition with a Domain Specific Language<br />FSDL - Federation Scenario Description Langu...
View of the Requested Federation Scenario<br />C. Tranoris - Univ. of Patras, Greece<br />
Example usage<br />C. Tranoris - Univ. of Patras, Greece<br />Central Federal Entity (Broker)<br />Private Request<br />Pa...
Defining federation scenarios:Importing conformant offices<br />Office meta-model<br />Local Office<br />Public office<br ...
Defining federation scenarios:Example Use case: Private / Panlab Federation<br />Central Federal Entity<br />(Broker)<br /...
Workbench view<br />C. Tranoris - Univ. of Patras, Greece<br />
An example with Panlab and Amazon<br />C. Tranoris - Univ. of Patras, Greece<br />
The syntax of FSDL in XText<br />C. Tranoris - Univ. of Patras, Greece<br />
From service definitions to federation resources<br />User request consists of definitions from a pool of services (XaaS)<...
From service definitions to federation resources<br />Resource Provider<br />Resource Provider<br />Requested Office Servi...
From service definitions to resources<br />C. Tranoris - Univ. of Patras, Greece<br />Requested Office Services<br />Resou...
Automated generation of a Federation API todynamically interact with offered resources of a federation<br />C. Tranoris - ...
The Panlabcase<br />TEAGLE <br />SERVICES<br />PTM<br />PTM<br />C. Tranoris - Univ. of Patras, Greece<br />VCT tool<br />...
Federation Computing Interface (FCI)<br />An API for accessing resources in the federation<br />Used for developing applic...
An example use caseP2P client testing in large scale, best effort environment<br />Client<br />Server<br />Producer<br />L...
Experimenter will provide:
 a XEN image which will include: OS + Packages + p2p Client
 a XEN image which will include: OS + Packages + Logger facilities</li></li></ul><li>An example use caseP2P client testing...
Instantiating VMs<br />Client<br />Server<br />Logger image<br />Client (server) image<br />Producer<br />IGW<br />User si...
The FSDL description of scenario<br />
Operation View<br />C. Tranoris - Univ. of Patras, Greece<br />
Provisioning<br />C. Tranoris - Univ. of Patras, Greece<br />API<br />API<br />M<br />T<br />M<br />T<br />Provider<br />P...
REST http requests are used to communicate with gateways (or APIs like EC2)</li></li></ul><li>Extending the toolkit: Exten...
Wrapping up<br />Office meta-model for resource brokers and resource providers is available<br />A family of DSLs is defin...
Criticism<br />The syntax of the DSLs might be difficult to learn or there are inconsistencies, but this will be improved ...
Why Textual DSL?<br />it provides rapid prototyping and validation of the underlying model<br />it supports unambiguous re...
Upcoming SlideShare
Loading in …5
×

Adopting the DSM paradigm: defining federation scenarios through resource brokers for experimentally driven research

755 views
682 views

Published on

presented at 1st conference on Managing Federations, co-located with IM2011, Dublin

Published in: Technology, Travel
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
755
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • EMF, ecore model
  • Need for Domain Specific,Glwssa na ta perigrapsoume kai semantics
  • Adopting the DSM paradigm: defining federation scenarios through resource brokers for experimentally driven research

    1. 1. Adopting the DSM paradigm: defining federation scenarios through resource brokers for experimentally driven research <br />Christos Tranoris, PhD<br />Electrical and Computer Eng. department<br />University of Patras, Greece<br />
    2. 2. Introduction <br />Experimentally driven research<br />An emerging paradigm for the Future Internet<br />Validating through testing-scenarios new architectures and systems at scale and under realistic environments<br />Testbeds used have usually a certain scope of testing capabilities<br />Addresses the need to evolve the test beds into coherent experimentation facilities, enabling broader scope experimentation<br />Possible by enabling large-scale federated infrastructures of exposed organizational resources and testbed facilities.<br />Such future experimental facilities are leaded by global efforts like US-GENI and EU-FIRE<br />C. Tranoris - Univ. of Patras, Greece<br />
    3. 3. The Federation Scenario term<br />User realization of resource requirements<br />A well-defined specification of required (heterogeneous) services/resources along with their configurations, offered by a diverse pool of organizations in order to form new richer infrastructures. <br />Is instantiated as an SLA which is required by the user of the federation<br />Represents customer needs such as <br />i) evaluation and testing specifications of new technologies, products, services<br />ii) execution of network and application layer experiments, or even <br />iii) complete commercial applications that are executed by the federation’s infrastructure in a cost-effective way.<br />C. Tranoris - Univ. of Patras, Greece<br />
    4. 4. The key-role of resource brokers<br />A resource broker matches customer requested services and provider resources from the federation<br />The cloud computing community :<br />C. Tranoris - Univ. of Patras, Greece<br />“Federation is the act of combining data or identities across multiple systems. Federation can be done by a cloud provider or by a cloud broker. A broker has no cloud resources of its own, but matches consumers and providers based on the SLA required by the consumer. The consumer has no knowledge that the broker does not control the resources.”<br />Resource Provider<br />Broker<br />Requested Services<br />Resource Provider<br />Resource Provider<br />
    5. 5. Federation of Resource Providers and Brokers<br />C. Tranoris - Univ. of Patras, Greece<br />API<br />API<br />Provider<br />Provider<br />R<br />R<br />R<br />R<br />R<br />R<br />Resource Broker<br />End-user<br />Federation<br />
    6. 6. Federation of Resource Providers and Brokers<br />C. Tranoris - Univ. of Patras, Greece<br />API<br />API<br />API<br />Provider<br />Provider<br />Provider<br />Provider<br />API<br />R<br />R<br />R<br />R<br />R<br />R<br />R<br />R<br />R<br />R<br />R<br />R<br />Resource Broker<br />Federation of Federation<br />Resource Broker<br />API<br />Federation<br />End-user<br />API<br />Resource Broker<br />Federation<br />
    7. 7. This work<br />Adopted DSM practices where systematic use of a Domain Specific Language (DSL) is involved<br />Defined a meta-model for resource brokers matching requested services with providers’ resources<br />Defined a family of DSLs, used by resource brokers, resource providers and experimenters, that have the proposed meta-model as an abstract syntax<br />Tooling in Eclipse workbench available through pluginscalled Federation Scenario Toolkit (FSToolkit)<br />Part of Panlab – PII FP7 project<br />C. Tranoris - Univ. of Patras, Greece<br />
    8. 8. The family of DSLs<br />OfficeDL to define a resource broker or a resource provider<br />Service Description Language(SDL) defines offered services of a broker to the end-user<br />Resource Description Language (RDL/RADL) defines a provider’s offered resources implementing services<br />C. Tranoris - Univ. of Patras, Greece<br />Resource brokers and resource providers to describe themselves use:<br />The end-user (an experimenter or customer) uses the Federation Scenario Description Language (FSDL)<br />
    9. 9. Prerequisites for Defining Federation Scenarios<br />A common model to capture the Federation domain<br />Seamless transition from Requested Services to offered Resources<br />C. Tranoris - Univ. of Patras, Greece<br />
    10. 10. The need for a Federation meta-model<br />There is a need for defining federation scenarios in unambiguous ways <br />A formal specification is needed which:<br />Captures domain’s knowledge<br />Captures domain’s common entities<br />Uses existing standards, terminology and taxonomies<br />Provides a proper base for tools<br />C. Tranoris - Univ. of Patras, Greece<br />
    11. 11. Office meta-model<br />M2<br />M<br />M<br />Model To Model<br />Transformation<br />Other Office<br />Provider Z<br />Office Z<br />Office B<br />Office A<br />M1<br />Import statements<br />M0<br />specifies<br />Federation Scenario<br />definition<br />End-user<br />
    12. 12. Office meta-model<br />C. Tranoris - Univ. of Patras, Greece<br />Compute<br />officeA (broker)<br />officeA.comp1234<br />
    13. 13. C. Tranoris - Univ. of Patras, Greece<br />Office meta-model<br /><ul><li>A Contract between Offered Service and Offered Resource
    14. 14. Office Model maintains an aggregation of promises! </li></li></ul><li>The OfficeDL<br />enables rapid prototyping of the Office meta-model <br />enables easy instantiations of the meta-model <br />has as abstract syntax the meta-model<br />concrete syntax based on the textual modeling framework (TMF) of Eclipse , the Xtextframework<br />tools can import the instantiated models which are validated from the framework<br />resource brokers can use it to describe their users, offered services, providers and contracts<br />resource providers may use it for describing only their own organization resources for local usage and offer all the available tooling to their users<br />C. Tranoris - Univ. of Patras, Greece<br />
    15. 15. The Office meta-model<br />EMF<br />Office meta-model<br />implements<br />Office <br />Definition<br />Office A<br />C. Tranoris - Univ. of Patras, Greece<br />Office <br />Description Language<br />
    16. 16. The OfficeDL<br />C. Tranoris - Univ. of Patras, Greece<br />
    17. 17. From service definitions to federation resources<br />SDL: Service Description Language<br />Describes an offered service: capabilities, interfaces,…<br />RDL(RADL): Resource Adapter Description Language<br />Describes an offered resource which “implements” an offered service<br />C. Tranoris - Univ. of Patras, Greece<br />
    18. 18. The Service Description Language SDL<br />C. Tranoris - Univ. of Patras, Greece<br />
    19. 19. The Resource Description Language RDL(RaDL)<br />C. Tranoris - Univ. of Patras, Greece<br />
    20. 20. Service Description Language<br />SDL<br />Office model<br />Resource Adapter<br />Description<br />Language<br />RADL<br />SDL<br />RADL<br />Contract<br />C. Tranoris - Univ. of Patras, Greece<br />
    21. 21. install<br />RAActivator.java<br />RAInstance.java<br />SampleService.java<br />PTM<br />RADL ecore<br />Meta-model<br />Workflow<br />(xpt files)<br />install<br />M<br />T<br />M<br />T<br />M<br />T<br />M<br />T<br />Sample.java<br />FOKUS<br />PTM<br />Workflow<br />(xpt files)<br />Sample.radl<br />Sample model<br />Sample.xml<br />post<br />Workflow<br />(xpt files)<br />Teagle Repository<br />Sample.wsdl<br />post<br />Workflow<br />(xpt files)<br />Broker<br />Repository<br />
    22. 22. Defining federation scenarios:Definition with a Domain Specific Language<br />FSDL - Federation Scenario Description Language<br />Office meta-model<br />Import<br />office<br />Request of services and configurations<br />Scenario<br />Definition<br />Panlab office<br />C. Tranoris - Univ. of Patras, Greece<br />
    23. 23. View of the Requested Federation Scenario<br />C. Tranoris - Univ. of Patras, Greece<br />
    24. 24. Example usage<br />C. Tranoris - Univ. of Patras, Greece<br />Central Federal Entity (Broker)<br />Private Request<br />Panlab Federation<br />Panlab office<br />(public model)<br />Panlab Gateway<br />Eclipse +FSDL toolkit<br />Eclipse +FSDL toolkit<br />Domain manager<br />Univ. of Patras office<br />(local model)<br />Configuration<br />DM<br />Configuration<br />Providers<br />RA<br />RA<br />RA<br />DM<br />DM<br />RA<br />RA<br />RA<br />RA<br />RA<br />RA<br />DM<br />Panlab Provider<br />RA<br />RA<br />RA<br />Panlab Provider<br />Local Testbed<br />Panlab Provider<br />
    25. 25. Defining federation scenarios:Importing conformant offices<br />Office meta-model<br />Local Office<br />Public office<br />C. Tranoris - Univ. of Patras, Greece<br />Import<br />office<br />Request of services and configurations<br />FS<br />Definition<br />
    26. 26. Defining federation scenarios:Example Use case: Private / Panlab Federation<br />Central Federal Entity<br />(Broker)<br />Offered Services<br />Domain manager<br />Broker Gateway<br />Public office<br />(public model)<br />Eclipse +FSDL toolkit<br />Local Office<br />(local model)<br />DM<br />Provider<br />Configuration<br />Configuration<br />RA<br />RA<br />RA<br />DM<br />DM<br />Provider<br />RA<br />RA<br />RA<br />RA<br />RA<br />RA<br />DM<br />Offered Resources<br />RA<br />RA<br />RA<br />Provider<br />Offered Resources<br />Offered Resources<br />Local Testbed<br />Offered Resources<br />C. Tranoris - Univ. of Patras, Greece<br />
    27. 27. Workbench view<br />C. Tranoris - Univ. of Patras, Greece<br />
    28. 28. An example with Panlab and Amazon<br />C. Tranoris - Univ. of Patras, Greece<br />
    29. 29. The syntax of FSDL in XText<br />C. Tranoris - Univ. of Patras, Greece<br />
    30. 30. From service definitions to federation resources<br />User request consists of definitions from a pool of services (XaaS)<br />Federation mechanisms propose Resources that “implement” the requested services<br />C. Tranoris - Univ. of Patras, Greece<br />
    31. 31. From service definitions to federation resources<br />Resource Provider<br />Resource Provider<br />Requested Office Services<br />Resource Provider<br />C. Tranoris - Univ. of Patras, Greece<br />Choose resources (provider agnostic)<br />Propose Plan<br />Review Resources (for reservation)<br />Provision<br />
    32. 32. From service definitions to resources<br />C. Tranoris - Univ. of Patras, Greece<br />Requested Office Services<br />Resource Advisor<br />Requested Resources <br />from providers<br />(towards a final SLA)<br />
    33. 33. Automated generation of a Federation API todynamically interact with offered resources of a federation<br />C. Tranoris - Univ. of Patras, Greece<br />Federation API<br />core<br />M<br />T<br />Resource model<br />JAVA<br />C<br />Python<br />….<br />Workflow<br />Code<br />Generation<br />Model-to-Text<br />APIs to be used by developers that<br />Work with a federation scenario<br />Federation Scenario<br />(Requested Resources - SLA)<br />UA/SUT<br />Scenario def<br />FCI Core<br />
    34. 34. The Panlabcase<br />TEAGLE <br />SERVICES<br />PTM<br />PTM<br />C. Tranoris - Univ. of Patras, Greece<br />VCT tool<br />repo<br />UA/SUT<br />OE<br />TGW<br />RA<br />RA<br />RA<br />RA<br />RA<br />RA<br />
    35. 35. Federation Computing Interface (FCI)<br />An API for accessing resources in the federation<br />Used for developing applications that access requested resources through a broker’s services<br />Utilizes broker’s gateway and available API<br />C. Tranoris - Univ. of Patras, Greece<br />
    36. 36. An example use caseP2P client testing in large scale, best effort environment<br />Client<br />Server<br />Producer<br />Logger<br />IGW<br />IGW<br />IGW<br />IGW<br />Testbed<br /><ul><li>Testbed providers with Computing resources: XEN hosts
    37. 37. Experimenter will provide:
    38. 38. a XEN image which will include: OS + Packages + p2p Client
    39. 39. a XEN image which will include: OS + Packages + Logger facilities</li></li></ul><li>An example use caseP2P client testing in large scale, best effort environment<br />Client<br />Server<br />Producer<br />Logger<br />IGW<br />IGW<br />XEN server<br />IGW<br />IGW<br />Testbed<br /><ul><li>The 1st step is to deploy the XEN images to the machines</li></li></ul><li>Image deployment<br />Logger image<br />Client (server) image<br />Client<br />Server<br />User site<br />Producer<br />IGW<br />Logger<br />UoPTestbed<br />Testbed<br />IGW<br />Host<br />TSSG/ Testbed<br />IGW<br />IGW<br />RA: XENImageStore<br />-Name<br />-InputURL<br />-OutputURL<br />IGW<br />CosmoteTestbed<br />ISI Testbed<br />Synchromedia (Canada)<br />Initially the provided images will be copied to each testbed, to decrease deployment time<br />
    40. 40. Instantiating VMs<br />Client<br />Server<br />Logger image<br />Client (server) image<br />Producer<br />IGW<br />User site<br />Logger<br />UoPTestbed<br />Testbed<br />IGW<br />Host<br />TSSG/ Testbed<br />IGW<br />IGW<br />IGW<br />RA: XENVMDeploy<br />CosmoteTestbed<br />-Name<br />-URL<br />-IP<br />-MEM<br />-GW<br />-CAP<br />ISI Testbed<br />Synchromedia (Canada)<br />Then VMs are created on each testbed <br />
    41. 41. The FSDL description of scenario<br />
    42. 42. Operation View<br />C. Tranoris - Univ. of Patras, Greece<br />
    43. 43. Provisioning<br />C. Tranoris - Univ. of Patras, Greece<br />API<br />API<br />M<br />T<br />M<br />T<br />Provider<br />Provider<br />R<br />R<br />R<br />R<br />R<br />R<br />FSDL Request<br />Workflow<br />BGW<br />BPEL ODE<br />Workflow<br />Composer<br />SPATEL OE<br />BGW<br />REST<br />Reqs<br /><ul><li>In our prototype FSToolkit the jobs API of java is used
    44. 44. REST http requests are used to communicate with gateways (or APIs like EC2)</li></li></ul><li>Extending the toolkit: Extension Points<br />A Remote Provisioning Engine<br />Local Provisioning Engine<br />FS Toolkit<br />IWorkflowEngine<br />IProvisionResource<br />IProvisioningJobListener<br />fstoolkit. Amazon<br />fstoolkit. UoPoffice<br />IOfficeRepository<br />fstoolkit. euca2ools<br />fstoolkit. Panlaboffice<br />FCI<br />FCI Panlab<br />FCI UoP<br />FCI Amazon<br />FCI euca2ools<br />
    45. 45. Wrapping up<br />Office meta-model for resource brokers and resource providers is available<br />A family of DSLs is defined targeting brokers, providers and end-users having the meta-model as abstract syntax<br />C. Tranoris - Univ. of Patras, Greece<br />
    46. 46. Criticism<br />The syntax of the DSLs might be difficult to learn or there are inconsistencies, but this will be improved as more domain experts use the languages for their scenarios and model descriptions<br />C. Tranoris - Univ. of Patras, Greece<br />
    47. 47. Why Textual DSL?<br />it provides rapid prototyping and validation of the underlying model<br />it supports unambiguous requirement specifications<br />helps the Federation Scenario designer to specify simple or complex Federation Scenarios avoiding ambiguities of design and configuration and<br />it enables text version control and distributed definitions by versioning tools (i.e. svn, cvs, etc.)<br />C. Tranoris - Univ. of Patras, Greece<br />
    48. 48. Thank you<br />Questions?<br />Downloads and wiki at: http://nam.ece.upatras.gr/fstoolkit<br />Open source under Apache 2.0 licensehttp://svn.panlab.net/PII/repos/Software/sources/FCI/org.panlab.software.office.model/model/<br />C. Tranoris - Univ. of Patras, Greece<br />

    ×