Transcript: #StandardsGoals for 2024: What’s new for BISAC - Tech Forum 2024
Adopting the DSM paradigm: defining federation scenarios through resource brokers for experimentally driven research
1. Adopting the DSM paradigm: defining federation scenarios through resource brokers for experimentally driven research Christos Tranoris, PhD Electrical and Computer Eng. department University of Patras, Greece
2. Introduction Experimentally driven research An emerging paradigm for the Future Internet Validating through testing-scenarios new architectures and systems at scale and under realistic environments Testbeds used have usually a certain scope of testing capabilities Addresses the need to evolve the test beds into coherent experimentation facilities, enabling broader scope experimentation Possible by enabling large-scale federated infrastructures of exposed organizational resources and testbed facilities. Such future experimental facilities are leaded by global efforts like US-GENI and EU-FIRE C. Tranoris - Univ. of Patras, Greece
3. The Federation Scenario term User realization of resource requirements 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. Is instantiated as an SLA which is required by the user of the federation Represents customer needs such as i) evaluation and testing specifications of new technologies, products, services ii) execution of network and application layer experiments, or even iii) complete commercial applications that are executed by the federation’s infrastructure in a cost-effective way. C. Tranoris - Univ. of Patras, Greece
4. The key-role of resource brokers A resource broker matches customer requested services and provider resources from the federation The cloud computing community : C. Tranoris - Univ. of Patras, Greece “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.” Resource Provider Broker Requested Services Resource Provider Resource Provider
5. Federation of Resource Providers and Brokers C. Tranoris - Univ. of Patras, Greece API API Provider Provider R R R R R R Resource Broker End-user Federation
6. Federation of Resource Providers and Brokers C. Tranoris - Univ. of Patras, Greece API API API Provider Provider Provider Provider API R R R R R R R R R R R R Resource Broker Federation of Federation Resource Broker API Federation End-user API Resource Broker Federation
7. This work Adopted DSM practices where systematic use of a Domain Specific Language (DSL) is involved Defined a meta-model for resource brokers matching requested services with providers’ resources Defined a family of DSLs, used by resource brokers, resource providers and experimenters, that have the proposed meta-model as an abstract syntax Tooling in Eclipse workbench available through pluginscalled Federation Scenario Toolkit (FSToolkit) Part of Panlab – PII FP7 project C. Tranoris - Univ. of Patras, Greece
8. The family of DSLs OfficeDL to define a resource broker or a resource provider Service Description Language(SDL) defines offered services of a broker to the end-user Resource Description Language (RDL/RADL) defines a provider’s offered resources implementing services C. Tranoris - Univ. of Patras, Greece Resource brokers and resource providers to describe themselves use: The end-user (an experimenter or customer) uses the Federation Scenario Description Language (FSDL)
9. Prerequisites for Defining Federation Scenarios A common model to capture the Federation domain Seamless transition from Requested Services to offered Resources C. Tranoris - Univ. of Patras, Greece
10. The need for a Federation meta-model There is a need for defining federation scenarios in unambiguous ways A formal specification is needed which: Captures domain’s knowledge Captures domain’s common entities Uses existing standards, terminology and taxonomies Provides a proper base for tools C. Tranoris - Univ. of Patras, Greece
11. Office meta-model M2 M M Model To Model Transformation Other Office Provider Z Office Z Office B Office A M1 Import statements M0 specifies Federation Scenario definition End-user
12. Office meta-model C. Tranoris - Univ. of Patras, Greece Compute officeA (broker) officeA.comp1234
13.
14.
15. The Office meta-model EMF Office meta-model implements Office Definition Office A C. Tranoris - Univ. of Patras, Greece Office Description Language
17. From service definitions to federation resources SDL: Service Description Language Describes an offered service: capabilities, interfaces,… RDL(RADL): Resource Adapter Description Language Describes an offered resource which “implements” an offered service C. Tranoris - Univ. of Patras, Greece
20. Service Description Language SDL Office model Resource Adapter Description Language RADL SDL RADL Contract C. Tranoris - Univ. of Patras, Greece
21. install RAActivator.java RAInstance.java SampleService.java PTM RADL ecore Meta-model Workflow (xpt files) install M T M T M T M T Sample.java FOKUS PTM Workflow (xpt files) Sample.radl Sample model Sample.xml post Workflow (xpt files) Teagle Repository Sample.wsdl post Workflow (xpt files) Broker Repository
22. Defining federation scenarios:Definition with a Domain Specific Language FSDL - Federation Scenario Description Language Office meta-model Import office Request of services and configurations Scenario Definition Panlab office C. Tranoris - Univ. of Patras, Greece
23. View of the Requested Federation Scenario C. Tranoris - Univ. of Patras, Greece
24. Example usage C. Tranoris - Univ. of Patras, Greece Central Federal Entity (Broker) Private Request Panlab Federation Panlab office (public model) Panlab Gateway Eclipse +FSDL toolkit Eclipse +FSDL toolkit Domain manager Univ. of Patras office (local model) Configuration DM Configuration Providers RA RA RA DM DM RA RA RA RA RA RA DM Panlab Provider RA RA RA Panlab Provider Local Testbed Panlab Provider
25. Defining federation scenarios:Importing conformant offices Office meta-model Local Office Public office C. Tranoris - Univ. of Patras, Greece Import office Request of services and configurations FS Definition
26. Defining federation scenarios:Example Use case: Private / Panlab Federation Central Federal Entity (Broker) Offered Services Domain manager Broker Gateway Public office (public model) Eclipse +FSDL toolkit Local Office (local model) DM Provider Configuration Configuration RA RA RA DM DM Provider RA RA RA RA RA RA DM Offered Resources RA RA RA Provider Offered Resources Offered Resources Local Testbed Offered Resources C. Tranoris - Univ. of Patras, Greece
28. An example with Panlab and Amazon C. Tranoris - Univ. of Patras, Greece
29. The syntax of FSDL in XText C. Tranoris - Univ. of Patras, Greece
30. From service definitions to federation resources User request consists of definitions from a pool of services (XaaS) Federation mechanisms propose Resources that “implement” the requested services C. Tranoris - Univ. of Patras, Greece
31. From service definitions to federation resources Resource Provider Resource Provider Requested Office Services Resource Provider C. Tranoris - Univ. of Patras, Greece Choose resources (provider agnostic) Propose Plan Review Resources (for reservation) Provision
32. From service definitions to resources C. Tranoris - Univ. of Patras, Greece Requested Office Services Resource Advisor Requested Resources from providers (towards a final SLA)
33. Automated generation of a Federation API todynamically interact with offered resources of a federation C. Tranoris - Univ. of Patras, Greece Federation API core M T Resource model JAVA C Python …. Workflow Code Generation Model-to-Text APIs to be used by developers that Work with a federation scenario Federation Scenario (Requested Resources - SLA) UA/SUT Scenario def FCI Core
34. The Panlabcase TEAGLE SERVICES PTM PTM C. Tranoris - Univ. of Patras, Greece VCT tool repo UA/SUT OE TGW RA RA RA RA RA RA
35. Federation Computing Interface (FCI) An API for accessing resources in the federation Used for developing applications that access requested resources through a broker’s services Utilizes broker’s gateway and available API C. Tranoris - Univ. of Patras, Greece
45. Wrapping up Office meta-model for resource brokers and resource providers is available A family of DSLs is defined targeting brokers, providers and end-users having the meta-model as abstract syntax C. Tranoris - Univ. of Patras, Greece
46. Criticism 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 C. Tranoris - Univ. of Patras, Greece
47. Why Textual DSL? it provides rapid prototyping and validation of the underlying model it supports unambiguous requirement specifications helps the Federation Scenario designer to specify simple or complex Federation Scenarios avoiding ambiguities of design and configuration and it enables text version control and distributed definitions by versioning tools (i.e. svn, cvs, etc.) C. Tranoris - Univ. of Patras, Greece
48. Thank you Questions? Downloads and wiki at: http://nam.ece.upatras.gr/fstoolkit Open source under Apache 2.0 licensehttp://svn.panlab.net/PII/repos/Software/sources/FCI/org.panlab.software.office.model/model/ C. Tranoris - Univ. of Patras, Greece
Notes de l'éditeur
EMF, ecore model
Need for Domain Specific,Glwssa na ta perigrapsoume kai semantics