| | 94 | Goals: [[BR]] |
| | 95 | |
| | 96 | Provides operational home and global Lookup Services [[BR]] |
| | 97 | Creates and maps MDOD into metadata that is registered in Lookup Service [[BR]] |
| | 98 | |
| | 99 | Expand authorization at interface where data is shared; introduce use of GENI credentials [[BR]] |
| | 100 | |
| | 101 | Continue to participate in the GENI I&M effort, particularly in defining the schema for the “measurement data object descriptor”, and mapping it to the perfSONAR metadata that is registered with the Lookup Service. [[BR]] |
| | 102 | |
| | 103 | Provide LAMP images for creating “infrastructure measurement slices” in both protoGENI and ORCA environments. [[BR]] |
| | 104 | |
| | 105 | Install and operate a perfSONAR Lookup Service, for use with “infrastructure measurement slices”. [[BR]] |
| | 106 | |
| | 107 | Demonstrate and/or help others to demonstrate “infrastructure measurement slices” in both protoGENI and ORCA environments, with the data available at the perfSONAR MP is registered with the operational Lookup Service. [[BR]] |
| | 108 | |
| | 109 | Demonstrate using GENI credentials to authorize access to the data available at the perfSONAR MP. [[BR]] |
| | 110 | |
| | 111 | Define a plan for using ABAC to replace simple credentials to authorize the access to the data available at a perfSONAR MP. [[BR]] |
| | 112 | |
| | 118 | Goals: |
| | 119 | |
| | 120 | Continue to participate in the GENI I&M effort, particularly in defining the schema for the “measurement data object descriptor”. [[BR]] |
| | 121 | |
| | 122 | Work with the LAMP project to understand the LAMP/perfSONAR tools, and demonstrate using them to implement “infrastructure measurement slices” in today’s GENI backbone and access networks. [[BR]] |
| | 123 | |
| | 124 | Assuming LAMP/perfSONAR tools, develop a plan to evaluate the performance of today’s GENI IP backbone and access networks, using persistent or temporary “infrastructure measurement slices”, and utilizing existing perSONAR nodes in I2 and/or other networks. [[BR]] |
| | 125 | |
| | 126 | Define a procedure for evaluating the performance of GENI’s backbone and access networks when carrying L2 VLANs; start with the existing IP measurement tools including in the LAMP/perfSONAR tools, but consider tools that are specialized for evaluating the performance of L2 networks. [[BR]] |
| | 127 | |
| | 128 | Define a procedure for evaluating the performance of GENI’s backbone and access networks when using OpenFlow (e.g., “Tango GENI”); consider how to monitor the performance of OF networks, and introducing new specialized tools. [[BR]] |
| | 135 | Goals: |
| | 136 | |
| | 137 | Participate in the GENI I&M effort, particularly in defining the schema for the “measurement data object descriptor”, and uses of “descriptors” in tracking provenance. [[BR]] |
| | 138 | |
| | 139 | Work with the GENI I&M community to define extensions to the “descriptor” that would locate and describe objects beyond “measurement data objects” associated with an experiment, such as scripts, images, etc. [[BR]] |
| | 140 | |
| | 141 | Modify your tools to create, gather and forward “descriptors”, that could locate and describe all objects associated with an experiment; demonstrate how “descriptors” can be automatically created. [[BR]] |
| | 142 | |
| | 143 | |
| | 144 | Work with the GENI I&M community to define a modified “descriptor” that would provide a standardized GENI “resource event record”; these records could describe events such as assignments, faults or errors. [[BR]] |
| | 145 | |
| | 146 | Add modules to your tools to create, gather and forward “resource event records”, that when logged could fully describe the sequence of an experiment. [[BR]] |
| | 147 | |
| | 148 | Demonstrate forwarding your “records” using pub/sub servers and to repositories provided by the IMF project. [[BR]] |
| | 149 | |
| | 150 | Demonstrate your tools, and support experimenters in using them. [[BR]] |
| | 151 | |
| | 152 | Participate in the GENI I&M effort, in fitting your provenance tools into the “experimenter’s portal”. [[BR]] |
| | 153 | |
| | 159 | Goals: [[BR]] |
| | 160 | |
| | 161 | Participate in the GENI I&M effort, focusing on providing basic capabilities, and on extending the architecture to include a pub/sub mechanism. [[BR]] |
| | 162 | |
| | 163 | Prototype and demonstrate a GENI I&M capability to manage I&M services/slivers within a slice using a “measurement orchestration service”; use ORBIT Management Framework (OMF) software modules provided by NICTA, including the Experiment Controller (EC) and the Resource Controller (RC), that communicate using a pub/sub mechanism utilizing an XMPP server. [[BR]] |
| | 164 | |
| | 165 | Define and prototype an authorization mechanism for your sliver management service; consider message signing being proposed by NICTA. [[BR]] |
| | 166 | |
| | 167 | Demonstrate your capability to manage a sliver. [[BR]] |
| | 168 | |
| | 169 | Prototype and demonstrate a GENI I&M capability to transport event (or measurement) records; include software modules that collect the records, communicate using a pub/sub mechanism utilizing an XMPP server, archive the records in a repository, search the records, and display the records. [[BR]] |
| | 170 | |
| | 171 | Define and prototype an authorization mechanism for your event record transport service. [[BR]] |
| | 172 | |
| | 173 | Demonstrate your capability by transporting and distributing standardized GENI “resource event records”, as defined by the NetKarma project; these records could describe events such as assignments, faults or errors. [[BR]] |
| | 174 | |
| | 175 | Prototype and operate a GENI I&M service to provide pub/sub services utilizing an XMPP server, for use by your sliver management and event record transport services. [[BR]] |
| | 176 | |
| | 177 | Define and prototype a resource assignment mechanism (using the GENI AM API, if possible) for users (experimenters and operators) to define nodes within your GENI pub/sub service, as they establish modules that publish or subscribe. [[BR]] |
| | 178 | |
| | 179 | Prototype and operate a data repository associated with your pub/sub service, that could subscribe to a node and archive all event messages. [[BR]] |
| | 185 | |
| | 186 | Goals: [[BR]] |
| | 187 | |
| | 188 | Continue to deploy a prototype Measurement Data Archive (MDA) service, and support integration with GENI I&M tools. [[BR]] |
| | 189 | |
| | 190 | Participate in the GENI I&M effort, particularly in the MDA specification effort that includes defining metadata model for archived entities, defining access-control layer, and integrating control framework authorization scheme with the MDA. [[BR]] |
| | 191 | |
| | 192 | Enforce metadata schema on archived objects, and enable access control rights as defined by the MDA specification. [[BR]] |
| | 193 | |
| | 194 | Integrate GENI identity management and authorization scheme if feasible and applicable, resources permitting. [[BR]] |
| | 195 | |
| | 196 | Evangelize and demonstrate how the MDA/DOR service can be used to archive published data. [[BR]] |
