28 | | |
29 | | == 2) Topics for this meeting == |
30 | | |
31 | | === T9) GENI Storage and Archive Service (based on iRODS) === |
32 | | 8:35am [[BR]] |
33 | | |
34 | | Shu Huang (RENCI) [[BR]] |
35 | | |
36 | | Tasks |
37 | | * Design and deploy GENI Storage and Archive Service for use by all GENI services. |
38 | | * Provide functions similar to the Measurement Data Archive (MDA) service prototype, designed by CNRI. |
39 | | * Use to store all types of experiment artifacts (not just measurement data), and identify objects to be moved to a long-term archive. |
40 | | * Implement using the iRODS data grid service, by defining rules (interfaces) to provide the necessary GENI functions. [[BR]] |
41 | | |
42 | | Design goals and approach |
43 | | * [wiki:InstMeasTopic_4.9ArchiveService status at GEC13] [[BR]] |
44 | | * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides at GEC13] [[BR]] |
45 | | * iRODS service has been established at RENCI [[BR]] |
46 | | * iRODS service has been established at Univ of Kentucky [[BR]] |
47 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx iRODS configuration at GEC14] [[BR]] |
48 | | * Proposed configuration? [[BR]] |
49 | | * Operations plan? [[BR]] |
50 | | |
51 | | Current implementation and next steps |
52 | | |
53 | | * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/iRODS%20GENI%20plan.docx iRODS GENI Plan] [[BR]] |
54 | | |
55 | | Open issues |
56 | | * Who is lead? [[BR]] |
57 | | * Will all iRODS services be federated, for redundancy? |
58 | | * How to move data to service: move file; move SQL DB; or? [[BR]] |
59 | | * How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] |
60 | | * How are partitions for different users managed? [[BR]] |
61 | | * How is authorization for a user done? [[BR]] |
62 | | * How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
63 | | * How will the GEMINI project use the iRODS service? [[BR]] |
64 | | * Will other parts of GENI want to use the iRODS service? [[BR]] |
65 | | * Do we need a breakout session for further discussion? when? [[BR]] |
66 | | |
67 | | Team |
68 | | * Shu Huang (RENCI), GIMI project, Lead |
69 | | * ? , GEMINI project |
70 | | * Giridhar Manepalli (CNRI) |
71 | | * Harry Mussman and Jeanne Ohren (GPO) |
72 | | |
73 | | |
74 | | |
75 | | === S5) Unified Network Information Service (UNIS) === |
76 | | 9:45am [[BR]] |
77 | | |
78 | | Ahmed El-Hassany (IU) [[BR]] |
79 | | |
80 | | Tasks [[BR]] |
81 | | * Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set. |
82 | | |
83 | | Summary |
84 | | * [wiki:InstMeasTopic_4.7LookupService status at GEC13] [[BR]] |
85 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/UNIS_GEC14.pdf UNIS configuration at GEC14; proposed configuration] [[BR]] |
86 | | |
87 | | Discussion |
88 | | * Who is lead? [[BR]] |
89 | | * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] |
90 | | * What additional features are under consideration? [[BR]] |
91 | | * What new interfaces are under consideration? [[BR]] |
92 | | * Will the GIMI project want to use the UNIS service? [[BR]] |
93 | | * Will other parts of GENI want to use the UNIS service, e.g., stitching? [[BR]] |
94 | | * Do we need a breakout session for further discussion? when? [[BR]] |
95 | | |
96 | | |
97 | | |
98 | | |