GIMI_v1.0_BasicUseCase: 053012_I&M_GIMI_BasicUseCase.txt

File 053012_I&M_GIMI_BasicUseCase.txt, 9.7 KB (added by hmussman@bbn.com, 7 years ago)
Line 
1[[PageOutline]]
2
3== GIMI I&M Tools:  Basic Experimenter Use Case ==
4
5For discussion on 053012:
6
71)  Establish test/experiment environment
8
92)  Obtain slice of GENI resources, install and configure GIMI I&M tools and reference/actual experiment
10
113)  Run and orchestrate GIMI I&M tools and reference/actual experiment
12
134)  Observe I&M measurement results on GIMI presentation service inside of the slice
14
155)  Push I&M measurement results to iRODS archive service
16
176)  Pull I&M measurement results from iRODS archive service to IREEL portal service, then analyze/process/present results, and push back to iRODS archive service
18
19
20=== 1)  Establish test/experiment environment ===
21
221.1)  Establish user workspace service
23
241.2)  Verify availability of desired aggregates
25
261.3)  Verify availability of desired software images/packages
27
281.4)  Verify avaialbility of necessary oeprational services
29
30 -  XMPP server
31 -  IREEL portal service
32 -  iRODS archive service
33
34=== 2)  Obtain slice of GENI resources, install and configure GIMI I&M tools and reference/actual experiment ===
35
362.1)  Select target aggregates:
37
38 - a)  ExoGENI rack VMs, one aggregate
39   - MC on VM
40   - MPs and ExperApp on VMs  (2 or more)
41   
42 - b)  ExoGENI rack VMs, multiple aggregates  (2 or more)
43   - MC on VM; each aggregate or one aggregate?
44   - MPs and ExperApp on VMs, each aggregate  (2 or more)   
45       
462.2)  Select desired software images/packages:
47
48 - a)  VM image including OS plus all GIMI I&M code
49        - GIMI I&M code includes both MC and MP code
50        - if Gush is used, Gush client can be loaded in image
51
52 - b)  Reference/Active Experiment pkg(s)
53    - need:  experiment topology
54        - option:  one package to be installed on all nodes
55        - option:  multiple packages, to be installed on different nodes
56       
572.3)  Obtain certs, credentials, passwords and keys
58
59 - required services:  GENI CA;  GENI SA;  GENI key generation service
60 
61 - tools:  shell scripts   (later:  clearinghouse portal)
62 
63 - at completion:    certs, credentials, passwords (to iRODS) and keys in local store, in user workspace
64 
65 - typically, do not have to repeat
66
67
682.4)  Formulate slice topology for test/experiment, and build request rspec
69
70 - tools:   how to visualize topology of experiment and I&M tools?    use  FLUKES?
71 
72 - tools:  how to build request rspec?  edit respec file?   use  FLUKES?
73 
74 - at completion:    request rspec in local store, in user workspace
75
76
772.5)  Acquire resources and load images
78
79 - tools:   OMNI, to acquire resources and load images
80 
81 - option:  also loads software packages for reference/actual experiment
82 
83 - at completion:    completed slice/slivers of hosts, with images, with VLAN connections
84 
85 - at completion:  manifest rspec in local store, in user workspace
86 
87 - verification:  shell scripts that use keys to ssh into hosts;  also ping other hosts
88 
89 - note:  2.1) through 2.5) parallels rack acceptance tests
90
91
922.6)  Load software packages for reference/actual experiment (as needed)
93
94 - tools:  shell scripts
95 
96 - at completion:    completed slice/slivers of hosts, with images, with VLAN connections, with all software packages installed
97 
98 - verification:  shell scripts that ssh into hosts, also ping other hosts;  also verify all desired software installed
99
100
101
1022.7)  Start software processes  (as selected) 
103
104 - Select options for each node:
105   - I&M Measurement Collector (MC), including  analysis and presentation (yes or no)
106   - I&M Measurement Point (MP) for basic host measurements, e.g., cpu and memory usage  (yes or no)
107   - I&M Measurement Point (MP) for active network measurements, e.g., ping and iperf (yes or no)
108   - Reference/Actual Experiment  (yes or no)  option:  differnet processes on different nodes
109       
110 - Typical selections:
111    -  One node with MC;  multiple nodes with MP + Ref/Actual Exper
112
113 - tools:  shell scripts  or use Gush?
114 
115 - at completion:    completed slice/slivers of hosts, with images, with VLAN connections, with all software packages installed, with selected software processes running
116 
117 - verification:  shell scripts that ssh into hosts, ping other hosts, verify all software installed, verify selected processes running or Gush that verifies selected processes running
118 
119 
1202.8)   Configure selected I&M services
121
122 - objectives:
123   - binds services together, e.g., between each MP and the MC
124   - configures baseline services
125   - verifies that they are ready to run
126
127 - tools:  use what tool to assign MPs to interfaces?   use what tool to point data from MPs to MC?
128 
129 - tools:  use what tool to point browser at MC?  use what tool to configure presentation service in MC?
130 
131 - tools:  use what tool (OMF?) to start, stop, reset I&M services; and to observe the transition 
132 
133 - at completion:    configured I&M services, ready to run and collect data
134 
135
1362.9)  Configure selected reference/actual experiment services
137
138 - objectives:
139   - binds services together to realize overall reference/actual experiment
140   - configures baseline services
141   - verifies that they are ready to run   
142   
143 - tools:  use what tool to select options in reference/actual experiment?  use what tool to bind services together? 
144   
145 - tools:  use what tool (OMF?) to start, stop, reset reference/actual experiment services; and to observe the transition 
146 
147 - at completion:    configured reference/actual experiment services, ready to run and process data, which can be observed by I&M services
148 
149 
150 
151 
152=== 3)  Run and orchestrate GIMI I&M tools and reference/actual experiment  ===
153
154
1553.1)  Initial setup:  start basic host measurement and ping active network measurement I&M services, to verify functionality of I&M services and topology of slice
156
157 - tools:  use what tool (OMF?) to start basic host measurement and ping active network measurement I&M services, and observe the transition
158
159 - tools:  use what to find GUI on MC, then use GUI to observe  presentation of measurements by MAP (is there a way to script this?)
160 
161 - verify getting expected measurements from each MP, and collection at MC  (is there a way to script this?)
162 
163 - tools:  stop I&M services
164 
165 - at completion:    I&M services have collected basic host measurements and ping active network measurements from each MP, measured data is in MC, and measured data has been visualized by MAP service;  functionality of I&M services and topology of slice has been verified
166 
167 
1683.2)  Continuity test:  start basic host measurement and iperf active network measurement I&M services, to verify continuity of slice
169
170 - tools:  use what tool (OMF?) to start basic host measurement and iperf active network measurement I&M services, and observe the transition
171
172 - tools:  use what to find GUI on MC, then use GUI to observe  presentation of measurements by MAP (is there a way to script this?)
173 
174 - verify getting expected measurements from each MP, and collection at MC  (is there a way to script this?)
175 
176 - tools:  stop I&M services
177 
178 - at completion:    I&M services have collected basic host measurements and iperf active network measurements from each MP, measured data is in MC, and measured data has been visualized by MAP service;  functionality of I&M services and continuity of  slice has been verified
179 
1803.3)  Instrument reference/actual experiment:  start basic host measurement and ping active network measurement I&M services;  then start reference/actual experiment, and gather measurments to  verify functionality of refrence/actual experiment in slice
181
182 - tools:  use what tool (OMF?) to start basic host measurement and ping active network measurement I&M services, and observe the transition
183 
184 - tools:  use what tool (OMF?) to start reference/actual experiment services; and to observe the transition
185
186 - tools:  use what to find GUI on MC, then use GUI to observe  presentation of measurements by MAP (is there a way to script this?)
187 
188 - verify getting expected measurements from each MP, and collection at MC  (is there a way to script this?)
189 
190 - tools:  stop I&M services and reference/actual experiment services
191 
192 - at completion:    I&M services have collected basic host measurements and ping active network measurements from each MP while reference/actual experiment is running, measured data is in MC, and measured data has been visualized by MAP service;  functionality of of refrence/actual experiment in slice has been verified
193 
194=== 4)  Observe I&M measurement results on GIMI presentation service inside of the slice ===
195
196 - use GUI on MC to observe measurement results in real time  (as noted above)
197 
198 - use GUI on MC to observe measurement results after experiment has been completed
199 
200 - use what tool to configure presentation of measurment results?
201 
202 - can measurement results be keyed to a topology map?
203
204=== 5)  Push I&M measurement results to iRODS archive service ===
205
206 - use what tool to format group measurement results?
207 
208 - use what tool to push measurement results to iRODS archive service?
209 
210 - use what tool to formulate Measurement Data Object Descriptor (MDOD) for measurement results?  to add annotation?
211 
212 - use what tool to push MDOD to iRODS archive service?
213
214=== 6)  Pull I&M measurement results from iRODS archive service to IREEL portal service, then analyze/process/present results, and push back to iRODS archive service ===
215
216 - use what tool to pull measurement results from iRODS archive service to IREEL portal service?
217 
218 - what are options to analyze/process/present results in IREEL service?  how are these configured?
219 
220 - use what tool to push measurement results from  IREEL portal service back to iRODS archive service, after they have been modified?
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250