36 | | |
37 | | === 0) Overview of experiment === |
38 | | |
39 | | 0.1) Title and abstract |
40 | | |
41 | | 0.2) Goals |
42 | | |
43 | | 0.3) Configuration |
44 | | |
45 | | 0.4 Process (flow chart) |
46 | | |
47 | | |
48 | | === 1) Establish experiment environment === |
49 | | |
50 | | 1.1) Establish experiment managment (user workspace) service |
51 | | |
52 | | 1.2) Gather necessary keys, certificates and credentials |
53 | | |
54 | | 1.3) Verify availability of desired aggregates |
55 | | |
56 | | 1.4) Verify availability of desired software images/packages |
57 | | |
58 | | 1.5) Verify availability of necessary operational services, and access to those services |
59 | | |
60 | | |
61 | | === 2) Obtain slice of GENI resources, install I&M tools and experiment services === |
62 | | |
63 | | 2.1) Select target aggregates |
64 | | |
65 | | 2.2) Select desired software images/packages for I&M tools and experiment services |
66 | | |
67 | | 2.3) Obtain certs, credentials, passwords and keys |
68 | | |
69 | | 2.4) Formulate slice topology for experiment, and build request rspec |
70 | | |
71 | | 2.5) Acquire resources and load images/packages for I&M tools and experiment services |
72 | | |
73 | | 2.6) Start selected software processes |
74 | | |
75 | | 2.7) Confirm slice with installed I&M tools and experiment services |
76 | | |
77 | | |
78 | | === 3) Configure I&M tools and experiment services === |
79 | | |
80 | | 3.1) Configure selected I&M services |
81 | | |
82 | | - objectives: |
83 | | - binds services together, e.g., between each MP and the MC |
84 | | - configures baseline services |
85 | | - verifies that they are ready to run |
86 | | |
87 | | - at completion: configured I&M services, ready to run and collect data |
88 | | |
89 | | |
90 | | 3.2) Configure selected experiment services |
91 | | |
92 | | - objectives: |
93 | | - binds services together to realize overall reference/actual experiment |
94 | | - configures baseline services |
95 | | - verifies that they are ready to run |
96 | | |
97 | | - at completion: configured experiment services, ready to run and process data, which can be observed by I&M services |
98 | | |
99 | | |
100 | | === 4) Run and orchestrate I&M services and experiment services to complete run of experiment === |
101 | | |
102 | | |
103 | | 4.1) Initial setup: start basic host measurements and basic ping active network measurements |
104 | | |
105 | | - objectives: |
106 | | - verify functionality of hosts |
107 | | - verify topology of slice |
108 | | |
109 | | - observe measurements with a real-time presentation service |
110 | | |
111 | | - continue measurements throughout duration of the test/tutorial/experiment |
112 | | |
113 | | - at completion: |
114 | | - functionality of hosts and topology of slice has been verified throughout duration of the experiment |
115 | | |
116 | | |
117 | | 4.2) Continuity test: for a limited time, run iperf active network measurements |
118 | | |
119 | | - objectives: |
120 | | - verify ability of slice to carry traffic expected from experiment |
121 | | |
122 | | - observe measurements with a real-time presentation service |
123 | | |
124 | | - once satisfactory measurements have been observed, stop continuity test |
125 | | |
126 | | - at completion: |
127 | | - capability of slice to carry traffic expected from experiment has been verified |
128 | | |
129 | | |
130 | | 4.3) Instrument and run experiment: |
131 | | |
132 | | - objectives: |
133 | | - gather measurements during experiment that allow experiment goals to be met |
134 | | |
135 | | - include desired measurement points within hosts and/or experiment services to instrument test/tutorial/experiment |
136 | | |
137 | | - begin to run and orchestrate measurement services |
138 | | |
139 | | - begin to run and orchestrate experiment services |
140 | | |
141 | | - observe measurements with a real-time presentation service, to verify expected operation of experiment |
142 | | |
143 | | - collect all measurements for duration of experiment |
144 | | |
145 | | - stop experiment services, when this run of the experiment has been completed |
146 | | |
147 | | - stop measurement services |
148 | | |
149 | | - at completion: |
150 | | - one run of experiment has been completed |
151 | | - real-time look at measurements has verfied expected operation of experiment |
152 | | - a full set of measurements has been collected, for later analysis and presentation |
153 | | - collected measurments have been transfered to storage service, so that slice resources can be released (if desired) |
154 | | |
155 | | 4.4) Store collected measurements and other artifacts from test/tutorial/experiment in storage service |
156 | | |
157 | | - at completion: |
158 | | - collected measurements and other artifacts have been transfered to storage service |
159 | | - collected measurements and other artifacts are available for later analysis |
160 | | - slice resources can then be released at any time, without loss of any measurements or artifacts |
161 | | |
162 | | === 5) Analyze and visualize measurement results after completing run of experiment === |
163 | | |
164 | | - if necessary, retrieve measurement results from archive service |
165 | | |
166 | | - analyze and format results as desired, for visualization with presentation service |
167 | | |
168 | | - as appropriate, store analyzed results and/or visualization in storage service |
169 | | |
170 | | |
171 | | === 6) Move selected collected measurements and other artifacts from storage service to long-term archive service === |
172 | | |
173 | | - identify archived objects with peristent identifier |
174 | | |
175 | | - include policy for sharing with others |
176 | | |
177 | | - allow retrieval for further analysis and visualization |
178 | | |
179 | | |
180 | | === 7) Release experiment resources === |