1 | [[PageOutline]]
|
---|
2 |
|
---|
3 |
|
---|
4 | = GIMI tasks, issues, next steps =
|
---|
5 |
|
---|
6 | - After discussion on 4/5/12:
|
---|
7 | - After iRODS review with Shu on 4/12/12:
|
---|
8 | - After status call with Mike and Max on 4/18/12:
|
---|
9 | - After status call on 4/25/12:
|
---|
10 |
|
---|
11 | == 1) Status calls and reviews ==
|
---|
12 |
|
---|
13 | - on 4/25: when is next status call? 5/2
|
---|
14 | - on 4/25: when is design review? not 5/2; week of 5/7? week of 5/14?
|
---|
15 | - *** marks items that will be important to review on the next call
|
---|
16 | - 3) *** Architecture of GIMI tools for GEC14 tutorial
|
---|
17 | - 4) *** Introduce XML messaging service: required for OMF messages, used to orchestrate services
|
---|
18 | - 7) *** Steps towards GIMI testing: start by forwarding all code and plans for GEC13 demo; by 4/25?
|
---|
19 | - 8) *** Steps towards GIMI tutorial at GEC14
|
---|
20 |
|
---|
21 |
|
---|
22 | == 2) Target aggregates for GEC14 tutorial ==
|
---|
23 |
|
---|
24 | a) (Ilia) exoGENI racks; all VMs (Ilia)
|
---|
25 |
|
---|
26 | b) ( Ilia) access to shell on all nodes by public IP address; authentication/authorization using keys
|
---|
27 |
|
---|
28 | c) ( Ilia) access to web interfaces (GUIs) on all nodes by public IP address; authentication/authorization using keys? certificates?
|
---|
29 |
|
---|
30 |
|
---|
31 |
|
---|
32 | == 3) *** Architecture of GIMI tools for GEC14 tutorial ==
|
---|
33 |
|
---|
34 | a) (Mike) need to arrive at nominal configuration ASAP
|
---|
35 | - on 4/18: good discussion (see below); still need a clear and complete description soon; when?
|
---|
36 | - on 4/25: discussion as noted below; still need a clear and complete description soon, and a full design review; when?
|
---|
37 |
|
---|
38 | a') on 4/20: issue: how to configure MPs/MCs? from EC to RC in MP/MC?
|
---|
39 |
|
---|
40 | a!'') on 4/20: issue: is there a MAP on common node? at least to preview data? is there a MAP in user workspace? what?
|
---|
41 | - on 4/25: for 1st, no MAP on common node
|
---|
42 |
|
---|
43 | b) MPs with multiple possible measurements: host info; basic network performance with iperf, ping; data from app
|
---|
44 | - on 4/25: need to list baseline measurements, and configurable parameters
|
---|
45 |
|
---|
46 | c) MC (OML server) in common node (node n+1)
|
---|
47 |
|
---|
48 | d) where is MAP service installed? in common node? in user workspace? what is planned for this service? how can analysis/presentation be configured? is there an r script? is there a GUI? how is GUI accessed?
|
---|
49 | - on 4/25: for 1st, expect MAP only bin user workspace
|
---|
50 | - on 4/25: what is 1st MAP service? what functions are provided? can these be done using iREEL and r?
|
---|
51 |
|
---|
52 | e) movement of data from MC (OML server) to MAP service: direct? how? via iRODS, i.e., MC to iRODS to MAP? how?
|
---|
53 | - on 4/18, per Shu, and discussion: could login to MC node; establish first transfer from iRODS client on MC to to iRODS with iput; use iinit, so iRODS client remembers password; then periodic transfers with no human intervention; another push protocol, from MC to iRODS.
|
---|
54 | - on 4/18, per Shu, and discussion: next, can install iRODS client on user workspace, then pull data back to user workspace for analysis and presentation, and then push back to iRODS for archive
|
---|
55 |
|
---|
56 | f) 1st: common node in slice; 2nd: common node in user workspace (out of slice) (is this beyond GEC14?)
|
---|
57 | - on 4/25: for 1st, do common node in slice, but plan one per aggregate
|
---|
58 |
|
---|
59 | g) 1st: nodes on VMs, one aggregate; 2nd: nodes on VMs, multiple aggregates
|
---|
60 |
|
---|
61 | h) 1st: Load image for common node, MP nodes; 2nd: load MP code as package before/after app
|
---|
62 | - on 4/25: what is test app? need to have something visible, e.g., video to a web page?
|
---|
63 |
|
---|
64 | i) Is there authentication/authorization when data pushed fom MP to MC? 1st: none; considered OK 2nd: add ssl?
|
---|
65 |
|
---|
66 | j) Is there authentication/authorization when accessing GUI (MAP) on common node? how? does this use portal to GUIs?
|
---|
67 | - on 4/25: not in 1st
|
---|
68 |
|
---|
69 | == 4) *** Introduce XML messaging service: required for OMF messages, used to orchestrate services ==
|
---|
70 |
|
---|
71 | a) (Max, Christoph) public XMPP server must be available; what? where?
|
---|
72 |
|
---|
73 | b) (Max, Christoph) signed OMF messages: need summary of arrangement from NICTA. what are names? who configures pub/sub nodes? what is structure? how to generate and distribute keys? is a public key registry required? how would it be done?
|
---|
74 | - on 4/18: Max explains plan to use OMF6.0 approach; limited messages; can use XMPP or another transport; signed messages; can start with no authentication/authorization, and then turn it on later;
|
---|
75 | - on 4/18: need clear and complete description soon, particularly naming and establsihment of XMPP nodes. so that others can consider for use and Jeanne can begin testing.
|
---|
76 | - on 4/18: expect release of first OMF6.0 by mid-May, with firm RC and skeleton EC; expect updated EC by mid-June; is this too late for GEC14?
|
---|
77 | - on 4/25: need to start with an earlier version of OMF, e.g., OMF 5.3
|
---|
78 |
|
---|
79 | == 5) Tools in user workspace ==
|
---|
80 |
|
---|
81 | a) includes stores for keys, certificates, credentials, rspecs
|
---|
82 |
|
---|
83 | b) (Jeanne A, David) Use Gush with OMNI to acquire resources, load images/packages, setup connectivity, manage processes
|
---|
84 |
|
---|
85 | c) (Christoph) Use OMF EC to configure/orchestrate services; can EC drive scripts?
|
---|
86 |
|
---|
87 | d) (Ilia) FLUKES optional to create (or observe) rspec
|
---|
88 |
|
---|
89 | e) (Ilia) what is best way to load images? packages?
|
---|
90 |
|
---|
91 | f) (Christoph) Add iREEL (experimenter portal service);
|
---|
92 | - on 4/25: what can this do? can it provide MAP functions? can it drive scripts? (need copy to run locally)
|
---|
93 |
|
---|
94 | g) (From GEMINI; under discussion) Include portal service to find other GUIs?
|
---|
95 | - on 4/25: for 1st, not necessary
|
---|
96 |
|
---|
97 | h) (Giridhar, Jeanne, Shu) Include Directory Archive (DA) service ,which can push data to DOA service, using OI service (all from CNRI, also GPO )
|
---|
98 | - on 4/25: now replaced with iRODS client
|
---|
99 |
|
---|
100 | i) (Giridhar, Jeanne, Shu) Include MDOD creator/editor How does this interface with iRODS, ot push MDOD to iRODS?
|
---|
101 | - on 4/18: who on GIMI project will help define final MDOD schema? Shu.
|
---|
102 | - on 4/25: need to get group together, to revise MDOD schema, and consider implementation of creator/editor
|
---|
103 |
|
---|
104 |
|
---|
105 |
|
---|
106 |
|
---|
107 | == 6) Introduce iRODS service ==
|
---|
108 |
|
---|
109 | After review with Shu on 4/12/12:
|
---|
110 |
|
---|
111 | a) (Shu) define configuration of iRODS servers, etc. also logins for users
|
---|
112 |
|
---|
113 | b) (Shu) define functions, interfaces to iRODS, and iRODS client can a host mount a file system in iRODS?
|
---|
114 |
|
---|
115 | c) (Shu) define naming in iRODS
|
---|
116 |
|
---|
117 | d) (Shu) define use case for: moving data from MC to iRODS, then from iRODS to user workspace
|
---|
118 | - use iRODS cleint in MC to push to iRODS? how is authentication/authorization handled?
|
---|
119 | - use iRODS client in user workspace to pull to user workspace? how is authentication/authorization handled?
|
---|
120 |
|
---|
121 | On 4/18: use cases received:
|
---|
122 |
|
---|
123 | GIMI iRODS Use Cases - Preparation
|
---|
124 |
|
---|
125 | Create an account for user: shuang
|
---|
126 | iadmin mkuser shuang user_type
|
---|
127 | Assign user to a group
|
---|
128 | iadmin atg groupName shuang
|
---|
129 | Admin can assign password to user (also supports GSI/Kerberos)
|
---|
130 | iadmin moduser shuang password xxx
|
---|
131 | A lot of other things can be done:
|
---|
132 | iadmin h
|
---|
133 | Create an iRODS directory for the user OML measurement data
|
---|
134 | imkdir results
|
---|
135 |
|
---|
136 | GIMI iRODS Use Case 1
|
---|
137 | Perform an OML-based measurement, result is saved in a file (a.sqlite3) under /home/shuang/results
|
---|
138 | Put the file into iRODS
|
---|
139 | iput a.sqlite3 (suppose ipwd is /geniRenci/home/shuang/results)
|
---|
140 | Work on the local copy under /home/shuang/results
|
---|
141 | Push the modified file back into iRODS (think it as a version control system)
|
---|
142 | Irsync r /home/shuang/result i:/geniRenci/home/shuang/results
|
---|
143 |
|
---|
144 | GIMI iRODS Use Case 2
|
---|
145 | Check out a file in iRODS to my local directory
|
---|
146 | iget a.sqlite3
|
---|
147 | Work on the local copy
|
---|
148 | Push the modified file back into iRODS
|
---|
149 | irsync a.sqlite3 i:a.sqlite3
|
---|
150 |
|
---|
151 | GIMI iRODS Use Case 3
|
---|
152 | Suppose there are many files under /home/shuang/data that need to be copied into iRODS, we can mount the local directory directly into iRODS
|
---|
153 | imkdir /geniRenci/home/shuang/mountpoint
|
---|
154 | imcoll m filesystem /home/shuang/data /geniRenci/home/shuang/mountpoint
|
---|
155 | Work on the local files
|
---|
156 | Sync with iRODS
|
---|
157 | Irsync r /home/shuang/data i:/geniRenci/home/shuang/mountpoint
|
---|
158 |
|
---|
159 | GIMI iRODS Use Case 4
|
---|
160 | Data processing e.g. filtering files under /geniRenci/home/shuang
|
---|
161 | Write a rule called filter.r which filters files and save them under /geniRenci/home/shuang/filtered
|
---|
162 | irule F filter.r *Path=/geniRenci/home/shuang
|
---|
163 |
|
---|
164 | e) (Shu) consider interface to get unique handle; need to get current handle minting service from CNRI
|
---|
165 |
|
---|
166 | f) (Shu) consider storing and possibly formulating MDOD in iRODS how?
|
---|
167 |
|
---|
168 | g) (Shu) review above with GEMINI team
|
---|
169 |
|
---|
170 |
|
---|
171 | == 7) *** Steps towards GIMI testing ==
|
---|
172 |
|
---|
173 | a) (Jeanne) Arrange user workspace
|
---|
174 |
|
---|
175 | c) (Mike) What is first configuration of tools code? when? who?
|
---|
176 | - on 4/18: plan to forward all code and plans for GEC13 to Jeanne
|
---|
177 | - on 4/18: code leads are David and Delip; will join future calls
|
---|
178 |
|
---|
179 | d) (Jeanne) What are first test scripts? when?
|
---|
180 | - on 4/25: need to outline process for using tools in user workspace
|
---|
181 | - on 4/25: need to provide first test plan
|
---|
182 |
|
---|
183 | e) (Jeanne) When are first tests?
|
---|
184 |
|
---|
185 |
|
---|
186 |
|
---|
187 | == 8) *** Steps towards GIMI tutorial at GEC14 ==
|
---|
188 |
|
---|
189 | a) (Ilia) Start with GEC13 ORCA turorial?
|
---|
190 |
|
---|
191 | b) (Mike) Define covered use cases, and review with experiment support team (Mark, Niky)
|
---|
192 |
|
---|
193 | c) (Mike) When is first demo?
|
---|
194 |
|
---|
195 | d) (Mike) Need to establish high-level schedule: freeze code by end of June? then only testing, tutorial prep?
|
---|
196 |
|
---|
197 |
|
---|
198 |
|
---|
199 | == 9) Use GIMI in WiMAX site ==
|
---|
200 |
|
---|
201 | a) (Mike, Cong) Can we do something by GEC14? what?
|
---|
202 | - on 4/25: agree UMass Amherst WiMAX site should be up by GEC14
|
---|
203 | - on 4/25: agree should have plan to integrate GIMI with WiMAX by GEC14, but does not need to be done
|
---|
204 |
|
---|
205 |
|
---|
206 |
|
---|