| 73 | | ==== 2.3) Prototype Measurement Data Archive (MDA) Service ==== |
| 74 | | 1:45pm [[BR]] |
| 75 | | Giridhar Manepalli (CNRI) [[BR]] |
| 76 | | Measurement Data Archive (MDA) Service [[BR]] |
| 77 | | |
| 78 | | Defined earlier in these [http://groups.geni.net/geni/attachment/wiki/GEC10InstMeasWorkingSession/110410%20%20Topic2_MDASrvc_GEC9_Agenda_WGMtgInstAndMeas.ppt slides][[BR]] |
| 79 | | |
| 80 | | Overview of User Workspace and Digital Object Archive services presented in these summarized in these [http://groups.geni.net/geni/attachment/wiki/GEC10InstMeasWorkingSession/031711_SharingMDObjects%20_I%26MArch_Overview.pptx slides]:[[BR]] |
| 81 | | |
| 82 | | CNRI prototype defined:[[BR]] |
| 83 | | [http://groups.geni.net/geni/attachment/wiki/GEC10InstMeasWorkingSession/031011%20%20Measurement%20Data%20Archive%20Prototype.docx text][[BR]] |
| 84 | | [http://groups.geni.net/geni/attachment/wiki/GEC10InstMeasWorkingSession/MDA_CNRI_Giridhar.pptx Discussion Slides][[BR]] |
| 85 | | |
| 86 | | Demo[[BR]] |
| 87 | | |
| 88 | | First users?[[BR]] |
| 89 | | |
| 90 | | Other uses in GENI?[[BR]] |
| 91 | | |
| 92 | | |
| 93 | | |
| 94 | | |
| 95 | | |
| 96 | | === 4) Measurement Data Objects and Descriptors (i.e, metadata) === |
| 97 | | 3:00pm [[BR]] |
| 98 | | Harry Mussman [[BR]] |
| 99 | | 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]] |
| 100 | | 8 SCHEMA AND ELEMENTS FOR MEASUREMENT DATA OBJECT DESCRIPTORS (MDODS) [[BR]] |
| 101 | | 8.1 MEASUREMENT DATA OBJECTS (MDOS) [[BR]] |
| 102 | | 8.2 MEASUREMENT DATA (MD) OBJECT DESCRIPTOR [[BR]] |
| 103 | | 8.2.1 Uses [[BR]] |
| 104 | | 8.2.2 One Data Model [[BR]] |
| 105 | | 8.2.3 Multiple Schemas [[BR]] |
| 106 | | 8.3 MD OBJECT DESCRIPTOR DATA MODEL [[BR]] |
| 107 | | 8.3.1 Vocabulary [[BR]] |
| 108 | | 8.3.2 Identifier Elements [[BR]] |
| 109 | | 8.3.3 Interoperability Elements: [[BR]] |
| 110 | | 8.3.4 Discovery Elements [[BR]] |
| 111 | | 8.3.5 Administrative Elements: [[BR]] |
| 112 | | 8.3.6 Mapping into Descriptors from GENI MD Schemas [[BR]] |
| 113 | | 8.4 MD OBJECT DESCRIPTOR SCHEMAS [[BR]] |
| 114 | | 8.4.1 File Schema [[BR]] |
| 115 | | 8.4.2 MI Registration Schema [[BR]] |
| 116 | | 8.4.3 Archive Schema [[BR]] |
| 117 | | |
| 118 | | 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]] |
| 119 | | |
| 120 | | DRAFT MDOD Data Model, Elements and Values: [[BR]] |
| 121 | | |
| 122 | | Identifier (type, value) Mandatory [[BR]] |
| 123 | | |
| 124 | | Locator (type, value) Mandatory [[BR]] |
| 125 | | |
| 126 | | [Collection (member of): type; name; index] --- Optional [[BR]] |
| 127 | | |
| 128 | | [Structure: (where object includes multiple sub-objects) [[BR]] |
| 129 | | |
| 130 | | Sub-object x descriptor: [[BR]] |
| 131 | | (repeat above) [[BR]] |
| 132 | | |
| 133 | | Sub-object y descriptor: [[BR]] |
| 134 | | (repeat above) [[BR]] |
| 135 | | ] Optional [[BR]] |
| 136 | | |
| 137 | | Object type: flow | file | directory | data base | GUI | digital object Mandatory [[BR]] |
| 138 | | |
| 139 | | Measurement data schema: template; names; parameters; types Mandatory [[BR]] |
| 140 | | |
| 141 | | Size: (type, value) Optional [[BR]] |
| 142 | | |
| 143 | | Encryption: (type, owner) Optional [[BR]] |
| 144 | | |
| 145 | | Subject: what; where Mandatory [[BR]] |
| 146 | | |
| 147 | | Time: when Optional [[BR]] |
| 148 | | |
| 149 | | Keywords Optional [[BR]] |
| 150 | | |
| 151 | | Description Optional [[BR]] |
| 152 | | |
| 153 | | GENI-specific discovery elements: (services; identifiers; slices; experiments; runs) Mandatory [[BR]] |
| 154 | | |
| 155 | | Owner/creator: (slice; experiment; run; when; who; contact; processing; annotation) Mandatory [[BR]] |
| 156 | | |
| 157 | | Previous holder(s): (slice; experiment; run; when; who; contact; processing; annotation) Optional [[BR]] |
| 158 | | |
| 159 | | Current holder: (slice; experiment; run; when; who; contact; processing; annotation) Optional [[BR]] |
| 160 | | |
| 161 | | Last modified: (date; time; contact) Mandatory [[BR]] |
| 162 | | |
| 163 | | Licenses: Optional [[BR]] |
| 164 | | |
| 165 | | Private information: type; mitigation; responsibilities Optional [[BR]] |
| 166 | | |
| 167 | | Transfer rules: Optional [[BR]] |
| 168 | | |
| 169 | | Disposal rules: Optional [[BR]] |
| 170 | | |
| 171 | | |
| 172 | | Comments from earlier discussion: [[BR]] |
| 173 | | |
| 174 | | Camilo Viecco:[[BR]] |
| 175 | | |
| 176 | | All parameters look fine. I have one question: The 'Time' optional parameter appears to be redundant. Should it not match the owner/creator when mandatory value?[[BR]] |
| 177 | | |
| 178 | | There is also the issue of metadata for time ranges. How do we express that? If we remove the time, then I belive this is a good place to start[[BR]] |
| 179 | | |
| 180 | | Hussam Nasir:[[BR]] |
| 181 | | |
| 182 | | I agree with Camillo suggestions and dont see any more addition/removal i would want to make.[[BR]] |
| 183 | | |
| 184 | | Max Ott: [[BR]] |
| 185 | | |
| 186 | | As for meta data I first of all want to stress that we really should find a way to align this with the Resource Description spec of the Control Framework. While there is substantial reluctance there to embrace anything assembling some kind of structure, I'm not giving up the fight that easily. I just find it utterly silly to have two or more different ways to describe resources. Measurements are resources as well and metadata is all about describing where the measurements are coming from, that includes the resources we provision through the control framework.[[BR]] |
| 187 | | |
| 188 | | I know , with the little (or zero as in my case) funding we have available, nobody is excited about re-factoring for alignment sakes, but we shouldn't forget why we are we doing this in the first place. We just published a paper which included an analysis of last year's edition of one of the major conferences in our field. 26 out of the 36 accepted papers had substantial flaws in their respective analysis section, ranging from not even describing the experiment to the sloppy "10-run average" without any indication of precision. The numbers would have looked a lot grimmer if we would have tried to figure out on how to repeat the results.[[BR]] |
| 189 | | |
| 190 | | Coming back to meta data and repeating my RSpec argument. We first need an object/component/resource model and then we need a way to attach meaning to various 'groups' of model instances. The first part (model) should be quite stable as it gets baked into tools, services, and code and is expensive to change. The second part (semantics) should be easy to change as it inadvertently will as it reflects our changing needs, understandings, use cases. In other words, the rate of change somewhat reflects the vibrancy of the community using it.[[BR]] |
| 191 | | |
| 192 | | This is sitting in my drafts folder already for a few days, still half baked, but hopefully still of some marginal value.[[BR]] |
| 193 | | |
| 194 | | |
| 195 | | Discussion[[BR]] |
| 196 | | |
| 197 | | Consensus?[[BR]] |
| 198 | | |
| 199 | | Next steps? [[BR]] |
| 200 | | |
| 201 | | |
| 202 | | |
| 203 | | === 5) Current I&M Design and Prototyping Efforts === |
| 204 | | 3:45pm [[BR]] |
| | 73 | ==== 2.4) Supported Object Types ==== |
| | 74 | Instrumentation Tools (Kentucky) [[BR]] |
| | 75 | OMF/OML (NICTA) [[BR]] |
| | 76 | perSONAR/LAMP (Delaware, I2) [[BR]] |
| | 77 | OnTimeMeasure (Ohio State) [[BR]] |
| | 78 | Scalable Sensing Service? (Purdue, HP Labs) [[BR]] |
| | 79 | GMOC? (Indiana)[[BR]] |
| | 80 | NetCDF?[[BR]] |
| | 81 | others? [[BR]] |
| | 82 | |
| | 83 | ==== 2.5 Next Steps ==== |
| | 84 | |
| | 85 | |
| | 86 | === 3) Current I&M Design and Prototyping Efforts === |
| | 87 | 1:35pm [[BR]] |
| | 88 | |
| | 89 | |
| | 90 | ==== 3.1) Instrumentation Tools (Kentucky) ==== |
| | 91 | (Each one slide, or less) |
| | 92 | Summary and status |
| | 93 | Intended use(s): experimenter's slice? operator's infrastructure measurement slice? |
| | 94 | Creates or includes info for MDOD? mapping to MDOD elements? object_format? interpretation_method? |
| | 95 | Includes (or requires) persistent operational services? |
| | 96 | Status of integration with MDA service? issues? |
| | 97 | Authorization methods supported and/or issues? |
| | 98 | |
| | 99 | |
| | 100 | ==== 3.2) OMF/OML (NICTA) ==== |
| | 101 | (Each one slide, or less) |
| | 102 | Summary and status |
| | 103 | Intended use(s): experimenter's slice? operator's infrastructure measurement slice? |
| | 104 | Creates or includes info for MDOD? mapping to MDOD elements? object_format? interpretation_method? |
| | 105 | Includes (or requires) persistent operational services? |
| | 106 | Status of integration with MDA service? issues? |
| | 107 | Authorization methods supported and/or issues? |
| | 108 | |
| | 109 | |
| | 110 | ==== 3.3) perSONAR/LAMP (Delaware, I2) ==== |
| | 111 | (Each one slide, or less) |
| | 112 | Summary and status |
| | 113 | Intended use(s): experimenter's slice? operator's infrastructure measurement slice? |
| | 114 | Creates or includes info for MDOD? mapping to MDOD elements? object_format? interpretation_method? |
| | 115 | Includes (or requires) persistent operational services? |
| | 116 | Status of integration with MDA service? issues? |
| | 117 | Authorization methods supported and/or issues? |
| | 118 | |
| | 119 | |
| | 120 | ==== 3.4) OnTimeMeasure (Ohio State) ==== |
| | 121 | (Each one slide, or less) |
| | 122 | Summary and status |
| | 123 | Intended use(s): experimenter's slice? operator's infrastructure measurement slice? |
| | 124 | Creates or includes info for MDOD? mapping to MDOD elements? object_format? interpretation_method? |
| | 125 | Includes (or requires) persistent operational services? |
| | 126 | Status of integration with MDA service? issues? |
| | 127 | Authorization methods supported and/or issues? |
| | 128 | |
| | 129 | ==== 3.5) Meas Data Archive (MDA) Prototype Service ==== |
| | 130 | (Each one slide, or less) |
| | 131 | Summary and status |
| | 132 | Intended use(s): experimenter's slice? operator's infrastructure measurement slice? |
| | 133 | Creates or includes info for MDOD? mapping to MDOD elements? object_format? interpretation_method? |
| | 134 | Includes (or requires) persistent operational services? |
| | 135 | Status of integration with MDA service? issues? |
| | 136 | Authorization methods supported and/or issues? |
| | 137 | |
| | 138 | ==== 3.6) Others? ==== |
| | 139 | Scalable Sensing Service? (Purdue, HP Labs) [[BR]] |
| | 140 | GMOC? (Indiana)[[BR]] |
| | 141 | |
| | 142 | |
| | 143 | |
