Changes between Version 1 and Version 2 of InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService


Ignore:
Timestamp:
02/17/12 17:03:42 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService

    v1 v2  
    22
    33
    4 === 4.5)  Descriptors, Objects and Registries, and Lookup Service  ===
     4== 4.5)  Descriptors, Objects and Registries, and Lookup Service  ==
    55Descriptor Schema and Registry Service  [[BR]]
    66Object Names and Registry Service  [[BR]]
     
    1010
    1111
    12 1)  Definition of topic:  [[BR]]
     12=== 1) Goals ===
    1313
    14 a)  MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
    1514
    16 b)  MDOD registry.  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
    1715
    18 c)  Object (e.g., I&M service) names;  need a public reference. (consider DataCite)  [[BR]]
     16=== 2) Tasks ===
    1917
    20 d)  Object registry, with names and public key. [[BR]]
     18 a)  Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
     19 b)  Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
     20 c)  Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
     21 d)  MDOD registry.  Use UNIS lookup service?  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
     22 e)  MDOD creation and editing service.  [[BR]]
     23 f)  Need object (e.g., Measurement Data Object or I&M Service) names;  need a public reference;  consider DataCite  [[BR]]
     24 g)  Do we need object registry, with names and public key? [[BR]]
    2125
    22 e)  Home and global Lookup Service, as defined by perfSONAR  [[BR]]
    2326
    24 f)  Map MDOD into metadata that is registered  [[BR]]
     27=== 3) Team ===
    2528
    26 g)  Can Lookup Service be used for finding portals?  [[BR]]
     29Jason Zurawski (Internet2) [[BR]]
     30Ezra Kissel (U Delaware) [[BR]]
     31Eric Boyd (Internet2) [[BR]]
     32Beth Plale (IU) [[BR]]
     33Chris Small (GEMINI, IU) [[BR]]
     34Scott Jensen (Indiana U) [[BR]]
     35Larry Lannom (CNRI) [[BR]]
     36LEAD Giridhar Manepalli (CNRI) [[BR]]
     37Deniz Gurken (GIMI, UH) [[BR]]
     38Harry Mussman (GPO)  [[BR]] [[BR]]
    2739
    28 h)  Also Topology Service?  following UNIS?  [[BR]]
     40 
     41=== 4) Meetings ===
    2942
    30 2)  Who:  Jason Zurawski (Internet2);  Ezra Kissel (U Delaware);  Eric Boyd (Internet2);  Chris Small (GEMINI, IU);  Scott Jensen (Indiana U);  Larry Lannom (CNRI);  LEAD Giridhar Manepalli (CNRI);  Deniz Gurken (GIMI, UH);  Aaron Helsinger (GPO)  [[BR]]
     43(organized calls or meetings before GEC13?)
     44Review conclusions in pre-meeting at GEC13
     45
     46Review with working team at GEC13
     47
     48=== 5) Open Issues ===
     49
     50
     51=== 6)  Definition of Measurement Data Object Descriptor (MDOD) ===
     521:05pm  [[BR]]
     53Harry Mussman[[BR]]
     54
     55==== 1) Overview ====
     56
     57Format (syntax) [[BR]]
     58  Goal remains:  one data model for GENI [[BR]]
     59  Assume:  transfer format is XML record (file) [[BR]]
     60  Have example in XML-like format, and schema/types in RelaxNG  [[BR]]
     61  Need:  first software to generate (and consume) MDODs [[BR]]
     62   
     63Contents (semantics) [[BR]]
     64  Few required elements, many optional elements [[BR]]
     65  To meet use cases in arch document, sec 4.5 [[BR]]
     66  Want one-for-one mapping to key elements in current tools  (started:  perfSONAR;  GENI rspec) [[BR]]
     67
     68Point-of-view [[BR]]
     69  Often global;  therefore includes locators for data objects;  must be updated as objects are copied, moved [[BR]]
     70  Sometimes associated;  need to understand [[BR]]
     71  Should we consider:  storing all MDODs in global, MI srvc?  this becomes a MD object registry [[BR]]
     72 
     73Structure [[BR]]
     74  identifier(s) [[BR]]
     75  descriptor(s) [[BR]]
     76  holder(s) [[BR]]
     77
     78==== 2)  Use Cases ====
     79  Read the following sections of the [http://groups.geni.net/geni/attachment/wiki/GeniInstrumentationandMeasurementsArchitecture/122010i%20GENI-SE-IM-ARCH-1.0.doc  Architecture document:]  [[BR]]
     80
     814.5     GATHERING, TRANSFERRING AND SHARING MD   [[BR]]
     82
     834.5.1    Schema and Provenance of MD     [[BR]]
     84  schema for MD object contained in MDOD [[BR]]
     85  provenance of MD object contained in MDOD [[BR]]
     86
     874.5.2    Gathering MD into a Slice       [[BR]]
     88  by first holder, the "owner" [[BR]]
     89  starts MDOD [[BR]]
     90  as owner, sets sharing policy, disposal policy [[BR]]
     91  as gatherer, deals with privacy [[BR]]
     92
     934.5.3    Transferring MD between I&M Services in the Same Slice  [[BR]]
     94  holder updates MDOD as transfers MD object between locations [[BR]]
     95  option:  registers MDOD with MI service [[BR]]
     96
     974.5.4    Transferring MD between I&M Services in Different Slices        [[BR]]
     98  e.g., holder 1 to holder 2 [[BR]]
     99  holder 1 authorizes transfer, sends object and copy of MDOD [[BR]]
     100  holder 1 records the transfer in their MDOD [[BR]]
     101  holder 2 accepts MD object and MDOD, and adds their local location to their MDOD [[BR]]
     102  holder 2 tracks further transfers in their MDOD [[BR]]
     103
     1044.5.5    Sharing MD with Others [[BR]]
     105  e.g., holder 1 offers MD object at a portal, and registers this with MI srvc [[BR]]
     106  user 7 requests MD object [[BR]]
     107  holder 1 checks their sharing policy, authorizes transfer, and records the transfer in their MDOD [[BR]]
     108 
     109  e.g., holder 1 transfers MD object to DOA srvc [[BR]]
     110  user 9 requests MD object from DOA srvc [[BR]]
     111  DOA srvc checks sharing policy in associated MDOD, authorizes transfer, and records the transfer in their MDOD [[BR]]
     112
     113  Use these [http://groups.geni.net/geni/attachment/wiki/GeniInstrumentationandMeasurementsArchitecture/Visio-4.x%20%20030911%20_IM-ARCH-Figures.pdf  figures][[BR]]
     114 
     115  A summary of the topic is presented in these [http://groups.geni.net/geni/attachment/wiki/GEC10InstMeasWorkingSession/031711_GatheringTransferringMD_I%26MArch_Overview.pptx  slides][[BR]]
     116
     117  See: I&M in Experimenter's Slice  [[BR]]
     118[[Image(Visio-070111_UseCases_Services_MDOD_Page_01.jpg, 90%)]]  [[BR]]
     119
     120  See:  I&M in Operator's Infrastructure Measurement Slice  [[BR]]
     121  For example:  a GENI operator could get resources, setup a long-running measurement slice, and make data available to other operators or even experimenters.  [[BR]]
     122[[Image(Visio-070111_UseCases_Services_MDOD_Page_02.jpg, 90%)]]  [[BR]]
     123
     124 
     125==== 3)  Content (Semantics) ====
     126  Read the following sections of the [http://groups.geni.net/geni/attachment/wiki/GeniInstrumentationandMeasurementsArchitecture/122010i%20GENI-SE-IM-ARCH-1.0.doc  Architecture document:] [[BR]]
     127  8     SCHEMA AND ELEMENTS FOR MEASUREMENT DATA OBJECT DESCRIPTORS (MDODS)      [[BR]]
     128  8.1    MEASUREMENT DATA OBJECTS (MDOS)         [[BR]]
     129  8.2    MEASUREMENT DATA (MD) OBJECT DESCRIPTOR         [[BR]]
     130  8.3    MD OBJECT DESCRIPTOR DATA MODEL         [[BR]]
     131  8.4    MD OBJECT DESCRIPTOR SCHEMAS    [[BR]]
     132
     133  A summary of the topic is presented in these [http://groups.geni.net/geni/attachment/wiki/GEC10InstMeasWorkingSession/031711_MDObjectsDescriptors%20_I%26MArch_Overview.pptx  slides][[BR]]
     134
     135  DRAFT MDOD Data Models, Elements and Values  [[BR]]
     136
     137    v0.2.x XML-like example (HEM)   [[BR]]
     138    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072011_ver0.2_MDOD_DataModel.txt  v0.2 text][[BR]]
     139    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072511_ver0.2.1_MDOD_DataModel.txt  v0.2.1 text][[BR]]
     140    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072511_ver0.2.1_mandatoryonly_MDOD_DataModel.txt  v0.2.1 text, only mandatory elements][[BR]]
     141
     142    v0.3.x RelaxNG-Compact version (EK);  includes RNC and converted XSD files, both schema and types  [[BR]]
     143    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072111_v0.3_MDOD.rnc  v0.3 schema  RNC]  [[BR]]
     144    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072111_v0.3_MDOD.xsd  v0.3 schema  converted XSD]  [[BR]]
     145    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072111_v0.3_MDOD_types.rnc  v0.3 types  RNC]  [[BR]]
     146    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072111_v0.3_MDOD_types.xsd  v0.3 types  converted XSD]  [[BR]]
     147
     148    XML examples provided by Jason Zurawski:  [[BR]]
     149    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072811Zurawski_instance1.xml     example of proposed schema, with questions]  [[BR]]
     150    [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072811Zurawski_instance_proposed.xml     modified schema, for further discussion]  [[BR]]
     151
     152  MDOD Discussion Points  [[BR]]
     153
     154    For meeting on 072611  [http://groups.geni.net/geni/attachment/wiki/GEC11InstMeasWorkingSession/072511_MDOD_Discussion.txt  text]  [[BR]]
     155
     156==== 4)  Supported Object Types and Formats  ====
     157   Instrumentation Tools (Kentucky) [[BR]]
     158   OMF/OML  (NICTA) [[BR]]
     159   perSONAR/LAMP  (Delaware, I2) [[BR]]
     160   OnTimeMeasure   (Ohio State) [[BR]]
     161   Scalable Sensing Service?  (Purdue, HP Labs) [[BR]]
     162   GMOC? (Indiana)[[BR]]
     163   NetCDF?[[BR]]
     164   others?  [[BR]]
     165
     166==== 5)  Next Steps ====
     167   First review of data model and schema  (completed)  [[BR]]
     168
     169   For each tool:  map key elements into current data model;  review expected use cases  who?  when?  [[BR]]
     170   Review suggested approach to recording provenance   who?  when?  [[BR]]
     171   Review choice for primary and secondary identifiers  who?  when?  [[BR]]
     172   Review formats for slice_id, etc.  who?  when?  [[BR]]
     173
     174   Understand relationship to rspec?  who?  when? [[BR]]
     175
     176   Complete third pass at data model and schema     who?  when?[[BR]]
     177 
     178   Complete first prototype software to create MDOD  who?  when?[[BR]]
     179
     180