diff options
Diffstat (limited to 'doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml')
-rw-r--r-- | doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml | 258 |
1 files changed, 249 insertions, 9 deletions
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml index e3414f4..fb8ff8d 100644 --- a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml +++ b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml | |||
@@ -13,7 +13,7 @@ | |||
13 | TH.</para> | 13 | TH.</para> |
14 | 14 | ||
15 | <section id="onb_vnf_image"> | 15 | <section id="onb_vnf_image"> |
16 | <title>VNF - Onboard_VNF_Image<remark>all titles are formated with | 16 | <title>VNF - Onboard a VNF Image<remark>all titles are formated with |
17 | underscores can this be changed or should it be left as | 17 | underscores can this be changed or should it be left as |
18 | is?</remark></title> | 18 | is?</remark></title> |
19 | 19 | ||
@@ -60,7 +60,7 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
60 | </section> | 60 | </section> |
61 | 61 | ||
62 | <section id="offb_vnf"> | 62 | <section id="offb_vnf"> |
63 | <title>VNF - Offboard_VNF</title> | 63 | <title>VNF - Offboard a VNF</title> |
64 | 64 | ||
65 | <para><emphasis role="bold">Description:</emphasis> Removing a VNF | 65 | <para><emphasis role="bold">Description:</emphasis> Removing a VNF |
66 | Descriptor from the uCPE Manager. For details please refer to:</para> | 66 | Descriptor from the uCPE Manager. For details please refer to:</para> |
@@ -92,7 +92,7 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
92 | </section> | 92 | </section> |
93 | 93 | ||
94 | <section id="add_device"> | 94 | <section id="add_device"> |
95 | <title>Device - Add_Device</title> | 95 | <title>Device - Add a device</title> |
96 | 96 | ||
97 | <para><emphasis role="bold">Description:</emphasis> Adding a uCPE device | 97 | <para><emphasis role="bold">Description:</emphasis> Adding a uCPE device |
98 | to the uCPE Manager. For details please refer to:</para> | 98 | to the uCPE Manager. For details please refer to:</para> |
@@ -124,8 +124,248 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
124 | <Device-name> device already exists!</programlisting></para> | 124 | <Device-name> device already exists!</programlisting></para> |
125 | </section> | 125 | </section> |
126 | 126 | ||
127 | <section id="device_upload_image"> | ||
128 | <title>Device - Upload a NFV Access image</title> | ||
129 | |||
130 | <para><emphasis role="bold">Description:</emphasis> Upload a NFV Access image | ||
131 | file onto the uCPE Manager. For details please refer to:</para> | ||
132 | |||
133 | <itemizedlist> | ||
134 | <listitem> | ||
135 | <para><filename><AF-TH-install-dir>/playbooks/uploadImage.yml</filename></para> | ||
136 | </listitem> | ||
137 | |||
138 | <listitem> | ||
139 | <para><filename><AF-TH-install-dir>/automation_framework/device/uploadImage.py</filename></para> | ||
140 | </listitem> | ||
141 | </itemizedlist> | ||
142 | |||
143 | <para><emphasis role="bold">Precondition:</emphasis> The image path must | ||
144 | already exist.</para> | ||
145 | |||
146 | <para><emphasis role="bold">Example:</emphasis> <programlisting>ansible-playbook playbooks/uploadImage.yml -e \ | ||
147 | image_path="/tmp/enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \ | ||
148 | upgrade_type="xeon_d"</programlisting></para> | ||
149 | |||
150 | <para><emphasis role="bold">Action:</emphasis> Run the | ||
151 | <filename>uploadImage.yml</filename> Ansible playbook with the | ||
152 | <filename><Image-path></filename> and | ||
153 | <filename><Upgrade-type></filename> as extra-vars:</para> | ||
154 | |||
155 | <para><programlisting>ansible-playbook playbooks/deleteUpgradeFile.yml -e \ | ||
156 | image_path="<Image-path>" -e upgrade_type="<Upgrade-type>"</programlisting></para> | ||
157 | |||
158 | <para><emphasis role="bold">Result:</emphasis> Output of the test case | ||
159 | run using the Test Harness:</para> | ||
160 | |||
161 | <para><programlisting>TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework] | ||
162 | localhost : ok=1 changed=1 unreachable=0 failed=0</programlisting><emphasis | ||
163 | role="bold">Note:</emphasis> The test will fail if the image file has | ||
164 | already been uploaded.</para> | ||
165 | |||
166 | <para><programlisting>TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework] | ||
167 | ok=0 changed=0 unreachable=0 failed=1 | ||
168 | |||
169 | # debug | ||
170 | A file with the same name is already uploaded.</programlisting></para> | ||
171 | </section> | ||
172 | |||
173 | <section id="dev_del_upgrade"> | ||
174 | <title>Device - Delete Upgraded File</title> | ||
175 | |||
176 | <para><emphasis role="bold">Description:</emphasis> Deleting an uploaded | ||
177 | NFV Access image file from the uCPE Manager. For details please refer to:</para> | ||
178 | |||
179 | <itemizedlist> | ||
180 | <listitem> | ||
181 | <para><filename><AF-TH-install-dir>/playbooks/deleteUpgradeFile.yml</filename></para> | ||
182 | </listitem> | ||
183 | |||
184 | <listitem> | ||
185 | <para><filename><AF-TH-install-dir>/automation_framework/device/deleteUpgradeFile.py</filename></para> | ||
186 | </listitem> | ||
187 | </itemizedlist> | ||
188 | |||
189 | <para><emphasis role="bold">Preconditions:</emphasis> The image file | ||
190 | must already be uploaded onto the uCPE Manager.</para> | ||
191 | |||
192 | <para><emphasis role="bold">Example:</emphasis></para> | ||
193 | |||
194 | <programlisting>ansible-playbook playbooks/deleteUpgradeFile.yml -e \ | ||
195 | image_name="enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"</programlisting> | ||
196 | |||
197 | <para><emphasis role="bold">Action:</emphasis> Run the | ||
198 | <filename>deleteUpgradeFile.yml</filename> Ansible Playbook with the | ||
199 | <literal><Image-name></literal> as extra-vars:<programlisting>ansible-playbook playbooks/deleteUpgradeFile.yml -e \ | ||
200 | image_name="<Image-name>"</programlisting></para> | ||
201 | |||
202 | <para><emphasis role="bold">Result:</emphasis> Output of the test case | ||
203 | run using the Test Harness:<programlisting>TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework] | ||
204 | localhost : ok=1 changed=1 unreachable=0 failed=0</programlisting> | ||
205 | <emphasis role="bold">Note:</emphasis> The test will fail if the image | ||
206 | file does not exist: <programlisting>TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework] | ||
207 | ok=0 changed=0 unreachable=0 failed=1 | ||
208 | |||
209 | # debug | ||
210 | No oid found for '<image_name>' image name</programlisting></para> | ||
211 | </section> | ||
212 | |||
213 | <section id="dev_clear_info"> | ||
214 | <title>Device - Clear information about upgrades of uCPE devices</title> | ||
215 | |||
216 | <para><emphasis role="bold">Description:</emphasis> Clear information | ||
217 | about upgrades of uCPE devices. For details please refer to:</para> | ||
218 | |||
219 | <itemizedlist> | ||
220 | <listitem> | ||
221 | <para><filename><AF-TH-install-dir>/playbooks/clearCompletedUpgradesInfo.yml</filename></para> | ||
222 | </listitem> | ||
223 | |||
224 | <listitem> | ||
225 | <para><filename><AF-TH-install-dir>/automation_framework/device/clearCompletedUpgradesInfo.py</filename></para> | ||
226 | </listitem> | ||
227 | </itemizedlist> | ||
228 | |||
229 | <para><emphasis role="bold">Preconditions:</emphasis> No preconditions | ||
230 | needed.</para> | ||
231 | |||
232 | <para><emphasis role="bold">Action:</emphasis> Run the | ||
233 | <filename>clearCompletedUpgradesInfo.yml</filename> Ansible | ||
234 | Playbook:<programlisting>ansible-playbook playbooks/clearCompletedUpgradesInfo.yml</programlisting></para> | ||
235 | |||
236 | <para><emphasis role="bold">Result:</emphasis> Output of the test case | ||
237 | run using the Test Harness:<programlisting>TASK [Clear completed info about upgrading -- Run \ | ||
238 | clearCompletedUpgradesInfo.py module from automation framework]] | ||
239 | localhost : ok=1 changed=1 unreachable=0 failed=0</programlisting></para> | ||
240 | </section> | ||
241 | |||
242 | <section id="dev_inst_activ"> | ||
243 | <title>Device - Install and Activate a NFV Access image</title> | ||
244 | |||
245 | <para><emphasis role="bold">Description:</emphasis> Installing and | ||
246 | Activating a NFV Access image on a uCPE device from the uCPE Manager. For | ||
247 | details please refer to:</para> | ||
248 | |||
249 | <itemizedlist> | ||
250 | <listitem> | ||
251 | <para><filename><AF-TH-install-dir>/playbooks/installAndActivate.yml</filename></para> | ||
252 | </listitem> | ||
253 | |||
254 | <listitem> | ||
255 | <para><filename><AF-TH-install-dir>/automation_framework/device/installAndActivate.py</filename></para> | ||
256 | </listitem> | ||
257 | </itemizedlist> | ||
258 | |||
259 | <para><emphasis role="bold">Preconditions:</emphasis> <itemizedlist> | ||
260 | <listitem> | ||
261 | <para>The device must be previously added to the uCPE Manager | ||
262 | instance.</para> | ||
263 | </listitem> | ||
264 | |||
265 | <listitem> | ||
266 | <para>The image file must already be uploaded onto the uCPE | ||
267 | Manager.</para> | ||
268 | </listitem> | ||
269 | </itemizedlist></para> | ||
270 | |||
271 | <para><emphasis role="bold">Example:</emphasis></para> | ||
272 | |||
273 | <programlisting>ansible-playbook playbooks/installAndActivate.yml -e \ | ||
274 | image_name="enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \ | ||
275 | upgrade_type=xeon_d -e device=inteld1521-16"</programlisting> | ||
276 | |||
277 | <para><emphasis role="bold">Action:</emphasis> Run the | ||
278 | <filename>installAndActivate.yml</filename> Ansible Playbook with the | ||
279 | <literal><Image-name></literal>, | ||
280 | <literal><Upgrade-type></literal>, and the | ||
281 | <literal><Device-name></literal> as extra-vars:<programlisting>ansible-playbook playbooks/installAndActivate.yml -e \ | ||
282 | image_name="<Image_name>" -e upgrade_type="<Upgrade_type>" -e \ | ||
283 | device="<Device-name>"</programlisting></para> | ||
284 | |||
285 | <para><emphasis role="bold">Result:</emphasis> Output of the test case | ||
286 | run using the Test Harness:<programlisting>TASK \ | ||
287 | [Install And Activate -- Run installAndActivate.py module from automation_framework] | ||
288 | localhost : ok=1 changed=1 unreachable=0 failed=0</programlisting> | ||
289 | <emphasis role="bold">Note:</emphasis> The test will fail if the image | ||
290 | has already been installed on the uCPE device:<programlisting>TASK \ | ||
291 | [Install And Activate -- Run installAndActivate.py module from automation_framework] | ||
292 | ok=0 changed=0 unreachable=0 failed=1 | ||
293 | |||
294 | # debug | ||
295 | Duplicate entry - Release already installed</programlisting></para> | ||
296 | </section> | ||
297 | |||
298 | <section id="dev_upload_inst_activ"> | ||
299 | <title>Device - Upload, Install and Activate a NFV Access image on a uCPE | ||
300 | device</title> | ||
301 | |||
302 | <para><emphasis role="bold">Description:</emphasis> Upload, install and | ||
303 | activate a NFV Access image on a uCPE device from the uCPE Manager. For details | ||
304 | please refer to:</para> | ||
305 | |||
306 | <itemizedlist> | ||
307 | <listitem> | ||
308 | <para><filename><AF-TH-install-dir>/playbooks/installNFVAImage.yml</filename></para> | ||
309 | </listitem> | ||
310 | |||
311 | <listitem> | ||
312 | <para>The playbook imports the previously described | ||
313 | playbooks:<itemizedlist spacing="compact"> | ||
314 | <listitem> | ||
315 | <para><filename>playbook/addDevice.yml</filename></para> | ||
316 | </listitem> | ||
317 | |||
318 | <listitem> | ||
319 | <para><filename>playbook/uploadImage.yml</filename></para> | ||
320 | </listitem> | ||
321 | |||
322 | <listitem> | ||
323 | <para><filename>playbook/installAndActivate.yml</filename></para> | ||
324 | </listitem> | ||
325 | |||
326 | <listitem> | ||
327 | <para><filename>playbook/deleteUpgradeFile.yml</filename></para> | ||
328 | </listitem> | ||
329 | |||
330 | <listitem> | ||
331 | <para><filename>playbook/clearCompletedUpgradesInfo.yml</filename></para> | ||
332 | </listitem> | ||
333 | |||
334 | <listitem> | ||
335 | <para><filename>playbook/removeDevice.yml</filename></para> | ||
336 | </listitem> | ||
337 | </itemizedlist></para> | ||
338 | </listitem> | ||
339 | </itemizedlist> | ||
340 | |||
341 | <para><emphasis role="bold">Precondition:</emphasis> A device JSON | ||
342 | configuration file must be created:<programlisting><AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json</programlisting></para> | ||
343 | |||
344 | <para><emphasis role="bold">Example:</emphasis></para> | ||
345 | |||
346 | <programlisting>ansible-playbook playbooks/installNFVAImage.yml -e \ | ||
347 | device="inteld1521-16" -e \ | ||
348 | image_path=/tmp/enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \ | ||
349 | image_name=enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \ | ||
350 | upgrade_type=xeon_d</programlisting> | ||
351 | |||
352 | <para><emphasis role="bold">Action:</emphasis> Run the | ||
353 | <filename>installNFVAImage.yml</filename> Ansible Playbook with the | ||
354 | <literal><Image-path></literal>, | ||
355 | <literal><Image-name></literal>, | ||
356 | <literal><Upgrade-type></literal>, and the | ||
357 | <literal><Device-name></literal> as extra-vars:<programlisting>ansible-playbook playbooks/installNFVAImage.yml -e \ | ||
358 | device="<Device-name>" -e image_path="<Image-path>" -e \ | ||
359 | image_name="<Image-name>" -e upgrade_type="<Upgrade-type>"</programlisting></para> | ||
360 | |||
361 | <para><emphasis role="bold">Result:</emphasis> Output of the test case | ||
362 | run using the Test Harness:<programlisting>localhost : ok=1 changed=1 unreachable=0 failed=0</programlisting> | ||
363 | <emphasis role="bold">Note:</emphasis> The test will fail if the one | ||
364 | imported playbook fails:<programlisting>ok=0 changed=0 unreachable=0 failed=1</programlisting></para> | ||
365 | </section> | ||
366 | |||
127 | <section id="remv_dev"> | 367 | <section id="remv_dev"> |
128 | <title>Device - Remove_Device</title> | 368 | <title>Device - Remove a Device</title> |
129 | 369 | ||
130 | <para><emphasis role="bold">Description:</emphasis> Removing a uCPE | 370 | <para><emphasis role="bold">Description:</emphasis> Removing a uCPE |
131 | device from the uCPE Manager. For details please refer to:</para> | 371 | device from the uCPE Manager. For details please refer to:</para> |
@@ -167,7 +407,7 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
167 | </section> | 407 | </section> |
168 | 408 | ||
169 | <section id="bind_nic"> | 409 | <section id="bind_nic"> |
170 | <title>Network - Bind_NIC</title> | 410 | <title>Network - Bind a NIC</title> |
171 | 411 | ||
172 | <para><emphasis role="bold">Description:</emphasis> Binding a physical | 412 | <para><emphasis role="bold">Description:</emphasis> Binding a physical |
173 | network interface (NIC) to a device. For details please refer to:</para> | 413 | network interface (NIC) to a device. For details please refer to:</para> |
@@ -212,7 +452,7 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
212 | </section> | 452 | </section> |
213 | 453 | ||
214 | <section id="unbind_nic"> | 454 | <section id="unbind_nic"> |
215 | <title>Network - Unbind_NIC</title> | 455 | <title>Network - Unbind a NIC</title> |
216 | 456 | ||
217 | <para><emphasis role="bold">Description:</emphasis> Unbinding a physical | 457 | <para><emphasis role="bold">Description:</emphasis> Unbinding a physical |
218 | network interface (NIC) from a device. For details please refer | 458 | network interface (NIC) from a device. For details please refer |
@@ -254,7 +494,7 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
254 | </section> | 494 | </section> |
255 | 495 | ||
256 | <section id="create_bri"> | 496 | <section id="create_bri"> |
257 | <title>Network - Create_Bridge</title> | 497 | <title>Network - Create a Bridge</title> |
258 | 498 | ||
259 | <para><emphasis role="bold">Description:</emphasis> Creating an OVS | 499 | <para><emphasis role="bold">Description:</emphasis> Creating an OVS |
260 | network bridge on a uCPE device. For details please refer to:</para> | 500 | network bridge on a uCPE device. For details please refer to:</para> |
@@ -297,7 +537,7 @@ vnfd=<VNF-Descriptor-name>"</programlisting></para> | |||
297 | </section> | 537 | </section> |
298 | 538 | ||
299 | <section id="remov_bri"> | 539 | <section id="remov_bri"> |
300 | <title>Network - Remove_Bridge</title> | 540 | <title>Network - Remove a Bridge</title> |
301 | 541 | ||
302 | <para><emphasis role="bold">Description:</emphasis> Removing an OVS | 542 | <para><emphasis role="bold">Description:</emphasis> Removing an OVS |
303 | network bridge from a uCPE device. For details please refer to:</para> | 543 | network bridge from a uCPE device. For details please refer to:</para> |
@@ -335,7 +575,7 @@ bridge=<Bridge-name>"</programlisting></para> | |||
335 | </section> | 575 | </section> |
336 | 576 | ||
337 | <section id="config_dpdk"> | 577 | <section id="config_dpdk"> |
338 | <title>Network - Configure_DPDK</title> | 578 | <title>Network - Configure a DPDK</title> |
339 | 579 | ||
340 | <para><emphasis role="bold">Description:</emphasis> Enabling or | 580 | <para><emphasis role="bold">Description:</emphasis> Enabling or |
341 | Disabling the DPDK support in OVS. For details please refer to:</para> | 581 | Disabling the DPDK support in OVS. For details please refer to:</para> |