Fed4FIRE / Open-Multinet Resource Description Playground Alexander Willner Overview 2014-05-21
Overall Goal Federated Infrastructure Description and Discovery Language (FIDDLE)
Context Assumptions and applicability of this work
Assumptions and Applicability Concentrate on Future Internet Testbed Federations Federated Testbeds Federated Clouds Federated Smart Cities Federated Big Data Seite 4
Assumptions and Applicability Generalized High Level Overview and Stakeholders access resource (R) provides user domain domain domain domain owner runs federation operator Seite 5
Assumptions and Applicability Interoperability on Interface Level (SFA, FRCP, OMSP, ) researcher experiment Interface(s) federation Seite 6
Assumptions and Applicability Generalized Resource / Service Life-Cycle Discovery Requirements Reservation Provisioning Monitoring Experiment Termination R/S Information Model R/S Selection Description R/S Scheduling Model Direct or Orchestrated Instantiation R/S or Experiment Measurement Automated / Manual R/S Usage Data Storage and R/S Release Identity Management Authorization SLA Management Seite 7
Assumptions and Applicability Interoperability on the Information Model Level Discovery Requirements Reservation Provisioning Monitoring Experiment Termination R/S Information Model R/S Selection Description R/S Scheduling Model Direct or Orchestrated Instantiation R/S or Experiment Measurement Automated / Manual R/S Usage Data Storage and R/S Release Identity Management Authorization SLA Management Seite 8
Assumptions and Applicability Involves every step of the Life-Cycle Discovery Requirements Reservation Provisioning Monitoring Experiment Termination R/S Information Model R/S Selection Description R/S Scheduling Model Direct or Orchestrated Instantiation R/S or Experiment Measurement Automated / Manual R/S Usage Data Storage and R/S Release Identity Management Authorization SLA Management Seite 9
Assumptions and Applicability Generalized Approach Overview RSpec s, GLUE, NML, INDL, NDL-OWL, NOVI, related work requirements Discovery Requirements Reservation Provisioning Monitoring Experiment Termination R/S R/S R/S Direct or R/S or Automated / Data Storage Information Selection Scheduling Orchestrated Experiment Manual R/S and R/S Model Description Model Instantiation Measurement Usage Release Identity Management Authorization SLA Management evaluation defines upper ontology s/w integration concepts Seite 10
Current Situation XML Schema based modeling of information
Current Situation XML Schema based Data Model ((todo: concentrate on the RSpec Schema show comparable approaches such as the GLUE Schema)) Seite 12
What is Wrong? From a testbed owner, federation operator and user perspective
What s Wrong? Tree Data Model and XML Serialization ((todo: drawbacks of XML Schema; issues from user, owner and federation perspective)) Seite 14
How should it be? Connected RDF-based graphs for each step in the life-cycle
How should it be? Adopt Graph-based Approaches ((todo: advantages of RDF, RDFS, OWL, Reasoning, SPARQL, SWRL, )) Seite 16
How should it be? Graphical Interactive Example Seite 17
Current Proposal Open-Multinet Ontology based on existing work
Current Proposal Federation Meta-Data access resource (R) provides user domain domain domain domain owner runs federation operator Seite 19
Current Proposal Federation Meta-Data Concept nml:group rdfs:subclassof omn:federation rdf:type Fed4FIRE Summary: Description of the federation. Assumption: A federation is a specialized group. Classes: omn:federation Properties: none Typical Extensions: rdfs:label Fed4FIRE rdfs:comment This is foaf:depiction <url to logo> foaf:homepage <url to home> foaf:mbox <url to mail> Seite 20
Current Proposal Testbed Meta-Data access resource (R) provides user domain domain domain domain owner runs federation operator Seite 21
Current Proposal Testbed Meta-Data Concept nml:group rdfs:subclassof omn:partofgroup omn:groupcontains Summary: Description of a testbed. Assumption: A testbed is a specialized group and part of 0 n federations. Classes: omn:testbed xipi:testbed rdf:type rdf:type FUSECO Playground omn:partofgroup Fed4FIRE Seite 22 omn:testbed Properties: omn:partofgroup omn:groupcontains (inverse) Typical Extensions: rdfs:label FUSECO Playground rdfs:comment This is foaf:depiction <url to logo> foaf:homepage <url to home> foaf:mbox <url to mail> foaf:based_near geo:point
Current Proposal Testbed Meta-Data API s Summary: Testbeds should define endpoints. Assumption: A testbed offers FUSECO Playground omn:partofgroup Fed4FIRE multiple API s. Classes: omn:groupcontains omn:api AM rdf:type sfa:aggregatemnager omn:endpoint omn:version rdfs:subclassof <url> <version> omn:api Seite 23 sfa:aggregatemanager Properties: omn:endpoint omn:version Other examples: FRCP XMPP ID FI PPP GE X, Y, Z Teagle PTM OMSP Server
Current Proposal Testbed Meta-Data Integration into SFA { } Seite 24 'geni_allocate': 'geni_many', 'geni_api': 3, 'geni_single_allocation': 0, 'hostname': 'localhost', 'hrn': 'localhost', 'peers': { }, 'urn': 'urn:publicid: 'f4f_describe_testbed': text', 'f4f_endorsed_tools': [ { 'tool_homepage': text, ], tool_logo : url`} 'f4f_testbed_homepage': url', 'f4f_testbed_picture': url', Summary: Integration into SFA by extending the getversion result type. Assumption: Fed4FIRE extensions follow a similar approach. No security implications. Offering this data over other interfaces such as a SPARQL endpoint or within FRCP should be possible. Approach: JSON-LD serialized metadata of a testbed.
Current Proposal Resource Discovery access resource (R) provides user domain domain domain domain owner runs federation operator Seite 25
Current Proposal Resource Discovery Concept sfa:message rdfs:subclassof sfa:advertisement Summary: Message types are identified by an individual of a specific type. Assumption: This is needed for SFA clients to know the type of the answer. sfa:expires rdf:type Message sfa:generated Classes: sfa:message and subclasses Properties: sfa:expires and others Typical Extensions: none <datetime> <datetime> Seite 26
Current Proposal Resource Discovery Concept 5GFeasibilityAnalysis rdf:type fantaastic: FeasibilityAnalysis rdfs:subclassof fantaastic: ConsultingService rdfs:subclassof omn:partofgroup FUSECO Playground omn:partofgroup VMServer1 rdf:type mosaic:computational rdfs:subclassof nml:node omn:instantiates indl:virtualnode Summary: Resource instances are part of a testbed. They can instantiate resources (sliver). Assumption: Using NML and INDL as the main references. Classes: none Properties: omn:instantiates Typical Extensions: domain specific nml:service Seite 27
Current Proposal Resource Discovery Integration into SFA <?xml version="1.0" encoding="utf-8"?> <rdf:rdf xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:sfa="http://geni.net/ontology#" xmlns:omn="http://open-multinet.info/ontology#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema# > <rdf:description rdf:about="http://fuseco.fokus.fraunhofer.de/ ontology#message"> <rdf:type rdf:resource="http://geni.net/ ontology#advertisement"/> <sfa:expires rdf:datatype= Summary: Integration into SFA by filling the listresources result. Assumption: Returning any kind of XML-based data is fine. Approach: RDF/XML serialized data of testbed resources and services. Seite 28
Current Proposal Resource Reservation (SFA allocate) nml:group rdfs:subclassof omn:partofgroup novi:haslifetime Summary: Integration into SFA by defining NOVI reservation groups in the allocate call. Assumption: The NOVI reservation ontology is sophisticated enough. novi:reservation novi:haslifetime novi:lifetime Seite 29
Current Proposal Resource Instantiation (SFA provision) rdf:type :boundvm nml:implementedby Summary: Integration into SFA by defining resource instances of specific types. Assumption: Can be bound or unbound requests. indl:virtualnode fp:vmserver1 :unboundvm rdf:type indl:virtualnode Seite 30
Current Proposal Resource Monitoring (SFA describe or as OMSP stream) Summary: Integration into SFA by attaching monitoring specific graphs to existing resource instances (within listresources or describe). Another approach: serialize RDF graph as OMSP stream. Seite 31
Current Proposal Resource Control (FRCP related) Summary: Integration into FRCP by using the very same information used within SFA also to describe / control FRCP controlled resources. Seite 32