Changes between Version 21 and Version 22 of GEC14Agenda/IMDesignTopics


Ignore:
Timestamp:
06/26/12 13:40:33 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC14Agenda/IMDesignTopics

    v21 v22  
    107107* Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
    108108
    109 Martin Swany will review:  [[BR]]
     109Martin Swany and Jim Griffioen will review:  [[BR]]
    110110
    111111* Current architecture, design and status. [[BR]]
     
    177177 [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  work in progress]  [[BR]]
    178178 v0.1 design reviewed at GEC13    [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx  slides] (Giridhar Manepalli)  Conclusion:  too complex  [[BR]]
    179  DRAFT simplified v0.2 design  [ [  slides] (Harry Mussman)[[BR]]
     179 DRAFT simplified v0.2 design [  slides] (Harry Mussman)[[BR]]
    180180
    181181Discussion
     
    186186
    187187
    188 == 6)  Reports on operational I&M services, being introduced by GIMI and GEMINI projects ==
     188== 6)  Reports on persistent multi-user I&M services, being introduced by GIMI and GEMINI projects ==
    1891899:00am [[BR]]
    190190
     
    259259
    260260Tasks
    261  Establish persistent IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project
     261 Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project  [[BR]]
    262262
    263263Summary
     
    276276 Do we need a breakout session for further discussion?  when?  [[BR]]
    277277
    278 === S4)  INSTOOLS Portal Service ===
     278=== S4)  INSTOOLS portal-to-GUIs Service ===
    2792799:30am [[BR]]
    280280
    281 Team [[BR]]
    282  LEAD Jim Griffioen (U Kentucky) [[BR]]
     281Charles Carpenter (U Kentucky) [[BR]]
    283282
    284283Tasks:
    285  What persistent operational services must be supported: [[BR]]
    286  a)  Descriptor registry   required?  use UNIS?  DOR?  iRODS? IF-MAP? [[BR]]
    287  b)  Object registry   required?  use DOR? [[BR]]
    288  c)  XML Messaging service [[BR]]
    289  d)  Measurement Information (MI)service  [[BR]]
    290  e)  GENI User services [[BR]]
    291  f) Digital Object Archive (DOA) service [[BR]]
    292  Can all services can be shared by GIMI and GEMINI tools? [[BR]]
    293  How do these relate to other GENI services/functions, including clearinghouse?
    294 
     284 Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]]
     285
     286Summary
     287 Current configuration  [  slides]  [[BR]]
     288 Proposed configuration [  slides]  [[BR]]
     289 Operations plan  [  slides]  [[BR]]
     290
     291Discussion
     292 How are partitions for different users managed? [[BR]]
     293 How is authorization for a user done? [[BR]]
     294 What additional features are under consideration?
     295 Will the GIMI project want to use the INSTOOLS portal-to-GUIs service?  [[BR]]
     296 Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service?  [[BR]]
     297 Do we need a breakout session for further discussion?  when?  [[BR]]
    295298
    296299=== S5) UNIS Service ===
    2973009:40am  [[BR]]
    298301
    299 Team  [[BR]]
    300  LEAD Ahmed El-Hassany (IU)  [[BR]]
    301  Martin Swany (IU)  [[BR]]
    302 
     302Ahmed El-Hassany (IU)  [[BR]]
    303303
    304304Tasks   [[BR]]
    305  The MI service will be built by the GEMINI project using UNIS technology;  see the Spiral 4 SOW of the GEMINI project for the detailed steps, which include:  [[BR]]
    306  1) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances: [[BR]]
    307  2) Update topology model to Rspec version 3 and AM API (February 2012) [[BR]]
    308  3) Modifications to allow local UNIS to register with global UNIS (March 2012) [[BR]]
    309  4) Initial deployment of persistent GENI Global I&M Registry (GGR) service, based on UNIS. (May 2012) [[BR]]
    310  5) Complete noSQL (MongoDB) backend (September 2012)  [[BR]]
    311  6) Unify Perl and Python implementations (September 2012) [[BR]]
    312  Define, prototype, demonstrate and operate a MI service, starting in May, 2012. [[BR]]
    313  Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
    314  Define operations plan for MI service. [[BR]]
    315 
    316 [wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
    317 
    318 Summary of current status:  (Ahmed El-Hassany) [[BR]]
    319  [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T7%29%20%20GEC13.pdf  slides]  [[BR]]
     305 Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set.
     306
     307Summary
     308 [wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
     309 Current configuration  [  slides] [[BR]]
     310 Proposed configuration [  slides]  [[BR]]
     311 Operations plan  [  slides] [[BR]]
     312
     313Discussion
     314 Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]]
     315 What additional features are under consideration?
     316 Will the GIMI project want to use the UNIS service?  [[BR]]
     317 Will other parts of GENI want to use the UNIS service?  [[BR]]
     318 Do we need a breakout session for further discussion?  when?  [[BR]]
     319
    320320
    321321== 7)  Goals for the next 4 months ==
    3223229:50am [[BR]]
    323323
    324 Team [[BR]]
    325  LEAD  Harry Mussman  (GPO) [[BR]]
     324Harry Mussman  (GPO) [[BR]]
     325
     326Goals
     327 
    326328
    327329== 8)  Adjourn ==