GIMI_v1.0_BasicUseCase: 080312_I&M_GIMI_BasicUseCase.txt

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