summaryrefslogtreecommitdiffstats
path: root/docs/testing/user/testspecification/tempest_ipv6/ipv6_scenario.rst
blob: 5871321d0f37a438f077404b36a614d8cfe40290 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
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
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV

----------------------------------------------------------------------------
Test Case 1 - IPv6 Address Assignment - Dual Stack, SLAAC, DHCPv6 Stateless
----------------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.dhcpv6_stateless

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless'.
In this case, guest instance obtains IPv6 address from OpenStack managed radvd
using SLAAC and optional info from dnsmasq using DHCPv6 stateless. This test case then
verifies the ping6 available VM can ping the other VM's v4 and v6 addresses
as well as the v6 subnet's gateway ip in the same network, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os

Test preconditions
------------------

There should exist a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create one IPv6 subnet of the network created in test action 1 in
  ipv6_ra_mode 'dhcpv6_stateless' and ipv6_address_mode 'dhcpv6_stateless',
  storing the "id" parameter returned in the response
* Test action 6: Connect the IPv6 subnet to the router, using the stored IPv6 subnet id
* Test action 7: Boot two VMs on this network, storing the "id" parameters returned in the response
* **Test assertion 1:** The vNIC of each VM gets one v4 address and one v6 address actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 address
  as well as the v6 subnet's gateway ip
* Test action 8: Delete the 2 VMs created in test action 7, using the stored ids
* Test action 9: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 10: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 11: Delete the IPv6 subnet created in test action 5, using the stored id
* Test action 12: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 13: Delete the network created in test action 1, using the stored id
* Test action 14: List all networks, verifying the id is no longer present
* **Test assertion 6:** The "id" parameter is not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode
'dhcpv6_stateless' and ipv6_address_mode 'dhcpv6_stateless',
and verify the ping6 available VM can ping the other VM's v4 and v6 addresses as well as
the v6 subnet's gateway ip in the same network. Specifically it verifies that:

* The IPv6 addresses in mode 'dhcpv6_stateless' assigned successfully
* The VM can ping the other VM's IPv4 and IPv6 private addresses as well as the v6 subnet's gateway ip
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

--------------------------------------------------------------------------------------
Test Case 2 - IPv6 Address Assignment - Dual Net, Dual Stack, SLAAC, DHCPv6 Stateless
--------------------------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.dualnet_dhcpv6_stateless

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless'.
In this case, guest instance obtains IPv6 address from OpenStack managed radvd
using SLAAC and optional info from dnsmasq using DHCPv6 stateless. This test case then
verifies the ping6 available VM can ping the other VM's v4 address in one network
and v6 address in another network as well as the v6 subnet's gateway ip, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_dhcp6_stateless_from_os

Test preconditions
------------------

There should exists a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create another network, storing the "id" parameter returned in the response
* Test action 6: Create one IPv6 subnet of network created in test action 5 in
  ipv6_ra_mode 'dhcpv6_stateless' and ipv6_address_mode 'dhcpv6_stateless',
  storing the "id" parameter returned in the response
* Test action 7: Connect the IPv6 subnet to the router, using the stored IPv6 subnet id
* Test action 8: Boot two VMs on these two networks, storing the "id" parameters returned in the response
* Test action 9: Turn on 2nd NIC of each VM for the network created in test action 5
* **Test assertion 1:** The 1st vNIC of each VM gets one v4 address assigned and
  the 2nd vNIC of each VM gets one v6 address actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 address
  as well as the v6 subnet's gateway ip
* Test action 10: Delete the 2 VMs created in test action 8, using the stored ids
* Test action 11: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 12: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 13: Delete the IPv6 subnet created in test action 6, using the stored id
* Test action 14: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 15: Delete the 2 networks created in test action 1 and 5, using the stored ids
* Test action 16: List all networks, verifying the ids are no longer present
* **Test assertion 6:** The two "id" parameters are not present in the network list

Pass / Fail criteria
''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless', and verify the ping6 available VM can ping
the other VM's v4 address in one network and v6 address in another network as well as
the v6 subnet's gateway ip. Specifically it verifies that:

* The IPv6 addresses in mode 'dhcpv6_stateless' assigned successfully
* The VM can ping the other VM's IPv4 address in one network and IPv6 address in another
  network as well as the v6 subnet's gateway ip
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

-----------------------------------------------------------------------------------------------
Test Case 3 - IPv6 Address Assignment - Multiple Prefixes, Dual Stack, SLAAC, DHCPv6 Stateless
-----------------------------------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.multiple_prefixes_dhcpv6_stateless

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless'.
In this case, guest instance obtains IPv6 addresses from OpenStack managed radvd
using SLAAC and optional info from dnsmasq using DHCPv6 stateless. This test case then
verifies the ping6 available VM can ping the other VM's one v4 address and two v6
addresses with different prefixes as well as the v6 subnets' gateway ips in the
same network, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_dhcpv6_stateless

Test preconditions
------------------

There should exist a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create two IPv6 subnets of the network created in test action 1 in
  ipv6_ra_mode 'dhcpv6_stateless' and ipv6_address_mode 'dhcpv6_stateless',
  storing the "id" parameters returned in the response
* Test action 6: Connect the two IPv6 subnets to the router, using the stored IPv6 subnet ids
* Test action 7: Boot two VMs on this network, storing the "id" parameters returned in the response
* **Test assertion 1:** The vNIC of each VM gets one v4 address and two v6 addresses with
  different prefixes actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 addresses
  as well as the v6 subnets' gateway ips
* Test action 8: Delete the 2 VMs created in test action 7, using the stored ids
* Test action 9: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 10: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 11: Delete two IPv6 subnets created in test action 5, using the stored ids
* Test action 12: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 13: Delete the network created in test action 1, using the stored id
* Test action 14: List all networks, verifying the id is no longer present
* **Test assertion 6:** The "id" parameter is not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless',
and verify the ping6 available VM can ping the other VM's v4 address and two
v6 addresses with different prefixes as well as the v6 subnets' gateway ips in the same network.
Specifically it verifies that:

* The different prefixes IPv6 addresses in mode 'dhcpv6_stateless' assigned successfully
* The VM can ping the other VM's IPv4 and IPv6 private addresses as well as the v6 subnets' gateway ips
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

---------------------------------------------------------------------------------------------------------
Test Case 4 - IPv6 Address Assignment - Dual Net, Multiple Prefixes, Dual Stack, SLAAC, DHCPv6 Stateless
---------------------------------------------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.dualnet_multiple_prefixes_dhcpv6_stateless

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless'.
In this case, guest instance obtains IPv6 addresses from OpenStack managed radvd
using SLAAC and optional info from dnsmasq using DHCPv6 stateless. This test case then
verifies the ping6 available VM can ping the other VM's v4 address in one network
and two v6 addresses with different prefixes in another network as well as the
v6 subnets' gateway ips, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless

Test preconditions
------------------

There should exist a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create another network, storing the "id" parameter returned in the response
* Test action 6: Create two IPv6 subnets of network created in test action 5 in
  ipv6_ra_mode 'dhcpv6_stateless' and ipv6_address_mode 'dhcpv6_stateless',
  storing the "id" parameters returned in the response
* Test action 7: Connect the two IPv6 subnets to the router, using the stored IPv6 subnet ids
* Test action 8: Boot two VMs on these two networks, storing the "id" parameters returned in the response
* Test action 9: Turn on 2nd NIC of each VM for the network created in test action 5
* **Test assertion 1:** The vNIC of each VM gets one v4 address and two v6 addresses
  with different prefixes actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 addresses
  as well as the v6 subnets' gateway ips
* Test action 10: Delete the 2 VMs created in test action 8, using the stored ids
* Test action 11: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 12: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 13: Delete two IPv6 subnets created in test action 6, using the stored ids
* Test action 14: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 15: Delete the 2 networks created in test action 1 and 5, using the stored ids
* Test action 16: List all networks, verifying the ids are no longer present
* **Test assertion 6:** The two "id" parameters are not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'dhcpv6_stateless'
and ipv6_address_mode 'dhcpv6_stateless',
and verify the ping6 available VM can ping the other VM's v4 address in one network and two
v6 addresses with different prefixes in another network as well as the v6 subnets'
gateway ips. Specifically it verifies that:

* The IPv6 addresses in mode 'dhcpv6_stateless' assigned successfully
* The VM can ping the other VM's IPv4 and IPv6 private addresses as well as the v6 subnets' gateway ips
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

----------------------------------------------------------
Test Case 5 - IPv6 Address Assignment - Dual Stack, SLAAC
----------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.slaac

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'slaac' and
ipv6_address_mode 'slaac'.
In this case, guest instance obtains IPv6 address from OpenStack managed radvd
using SLAAC. This test case then verifies the ping6 available VM can ping the other
VM's v4 and v6 addresses as well as the v6 subnet's gateway ip in the
same network, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os

Test preconditions
------------------

There should exist a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create one IPv6 subnet of the network created in test action 1 in
  ipv6_ra_mode 'slaac' and ipv6_address_mode 'slaac', storing the "id" parameter returned in the response
* Test action 6: Connect the IPv6 subnet to the router, using the stored IPv6 subnet id
* Test action 7: Boot two VMs on this network, storing the "id" parameters returned in the response
* **Test assertion 1:** The vNIC of each VM gets one v4 address and one v6 address actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 address
  as well as the v6 subnet's gateway ip
* Test action 8: Delete the 2 VMs created in test action 7, using the stored ids
* Test action 9: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 10: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 11: Delete the IPv6 subnet created in test action 5, using the stored id
* Test action 12: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 13: Delete the network created in test action 1, using the stored id
* Test action 14: List all networks, verifying the id is no longer present
* **Test assertion 6:** The "id" parameter is not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'slaac'
and ipv6_address_mode 'slaac',
and verify the ping6 available VM can ping the other VM's v4 and v6 addresses as well as
the v6 subnet's gateway ip in the same network. Specifically it verifies that:

* The IPv6 addresses in mode 'slaac' assigned successfully
* The VM can ping the other VM's IPv4 and IPv6 private addresses as well as the v6 subnet's gateway ip
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

--------------------------------------------------------------------
Test Case 6 - IPv6 Address Assignment - Dual Net, Dual Stack, SLAAC
--------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.dualnet_slaac

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'slaac' and
ipv6_address_mode 'slaac'.
In this case, guest instance obtains IPv6 address from OpenStack managed radvd
using SLAAC. This test case then verifies the ping6 available VM can ping the other
VM's v4 address in one network and v6 address in another network as well as the
v6 subnet's gateway ip, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_slaac_from_os

Test preconditions
------------------

There should exist a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create another network, storing the "id" parameter returned in the response
* Test action 6: Create one IPv6 subnet of network created in test action 5 in
  ipv6_ra_mode 'slaac' and ipv6_address_mode 'slaac', storing the "id" parameter returned in the response
* Test action 7: Connect the IPv6 subnet to the router, using the stored IPv6 subnet id
* Test action 8: Boot two VMs on these two networks, storing the "id" parameters returned in the response
* Test action 9: Turn on 2nd NIC of each VM for the network created in test action 5
* **Test assertion 1:** The 1st vNIC of each VM gets one v4 address assigned and
  the 2nd vNIC of each VM gets one v6 address actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 address
  as well as the v6 subnet's gateway ip
* Test action 10: Delete the 2 VMs created in test action 8, using the stored ids
* Test action 11: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 12: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 13: Delete the IPv6 subnet created in test action 6, using the stored id
* Test action 14: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 15: Delete the 2 networks created in test action 1 and 5, using the stored ids
* Test action 16: List all networks, verifying the ids are no longer present
* **Test assertion 6:** The two "id" parameters are not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'slaac'
and ipv6_address_mode 'slaac',
and verify the ping6 available VM can ping the other VM's v4 address in one network and
v6 address in another network as well as the v6 subnet's gateway ip. Specifically it verifies that:

* The IPv6 addresses in mode 'slaac' assigned successfully
* The VM can ping the other VM's IPv4 address in one network and IPv6 address
  in another network as well as the v6 subnet's gateway ip
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

-----------------------------------------------------------------------------
Test Case 7 - IPv6 Address Assignment - Multiple Prefixes, Dual Stack, SLAAC
-----------------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.multiple_prefixes_slaac

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'slaac' and
ipv6_address_mode 'slaac'.
In this case, guest instance obtains IPv6 addresses from OpenStack managed radvd
using SLAAC. This test case then verifies the ping6 available VM can ping the other
VM's one v4 address and two v6 addresses with different prefixes as well as the v6
subnets' gateway ips in the same network, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac

Test preconditions
------------------

There should exists a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create two IPv6 subnets of the network created in test action 1 in
  ipv6_ra_mode 'slaac' and ipv6_address_mode 'slaac', storing the "id" parameters returned in the response
* Test action 6: Connect the two IPv6 subnets to the router, using the stored IPv6 subnet ids
* Test action 7: Boot two VMs on this network, storing the "id" parameters returned in the response
* **Test assertion 1:** The vNIC of each VM gets one v4 address and two v6 addresses with
  different prefixes actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 addresses
  as well as the v6 subnets' gateway ips
* Test action 8: Delete the 2 VMs created in test action 7, using the stored ids
* Test action 9: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 10: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 11: Delete two IPv6 subnets created in test action 5, using the stored ids
* Test action 12: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 13: Delete the network created in test action 1, using the stored id
* Test action 14: List all networks, verifying the id is no longer present
* **Test assertion 6:** The "id" parameter is not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'slaac'
and ipv6_address_mode 'slaac',
and verify the ping6 available VM can ping the other VM's v4 address and two
v6 addresses with different prefixes as well as the v6 subnets' gateway ips in the same network.
Specifically it verifies that:

* The different prefixes IPv6 addresses in mode 'slaac' assigned successfully
* The VM can ping the other VM's IPv4 and IPv6 private addresses as well as the v6 subnets' gateway ips
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None

---------------------------------------------------------------------------------------
Test Case 8 - IPv6 Address Assignment - Dual Net, Dual Stack, Multiple Prefixes, SLAAC
---------------------------------------------------------------------------------------

Short name
----------

functest.tempest.ipv6_scenario.dualnet_multiple_prefixes_slaac

Use case specification
----------------------

This test case evaluates IPv6 address assignment in ipv6_ra_mode 'slaac' and
ipv6_address_mode 'slaac'.
In this case, guest instance obtains IPv6 addresses from OpenStack managed radvd
using SLAAC. This test case then verifies the ping6 available VM can ping the other
VM's v4 address in one network and two v6 addresses with different prefixes in another
network as well as the v6 subnets' gateway ips, the reference is

tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_slaac

Test preconditions
------------------

There should exist a public router or a public network.

Basic test flow execution description and pass/fail criteria
------------------------------------------------------------

Test execution
'''''''''''''''

* Test action 1: Create one network, storing the "id" parameter returned in the response
* Test action 2: Create one IPv4 subnet of the created network, storing the "id"
  parameter returned in the response
* Test action 3: If there exists a public router, use it as the router. Otherwise,
  use the public network to create a router
* Test action 4: Connect the IPv4 subnet to the router, using the stored IPv4 subnet id
* Test action 5: Create another network, storing the "id" parameter returned in the response
* Test action 6: Create two IPv6 subnets of network created in test action 5 in
  ipv6_ra_mode 'slaac' and ipv6_address_mode 'slaac', storing the "id" parameters returned in the response
* Test action 7: Connect the two IPv6 subnets to the router, using the stored IPv6 subnet ids
* Test action 8: Boot two VMs on these two networks, storing the "id" parameters returned in the response
* Test action 9: Turn on 2nd NIC of each VM for the network created in test action 5
* **Test assertion 1:** The vNIC of each VM gets one v4 address and two v6 addresses
  with different prefixes actually assigned
* **Test assertion 2:** Each VM can ping the other's v4 private address
* **Test assertion 3:** The ping6 available VM can ping the other's v6 addresses
  as well as the v6 subnets' gateway ips
* Test action 10: Delete the 2 VMs created in test action 8, using the stored ids
* Test action 11: List all VMs, verifying the ids are no longer present
* **Test assertion 4:** The two "id" parameters are not present in the VM list
* Test action 12: Delete the IPv4 subnet created in test action 2, using the stored id
* Test action 13: Delete two IPv6 subnets created in test action 6, using the stored ids
* Test action 14: List all subnets, verifying the ids are no longer present
* **Test assertion 5:** The "id" parameters of IPv4 and IPv6 are not present in the list
* Test action 15: Delete the 2 networks created in test action 1 and 5, using the stored ids
* Test action 16: List all networks, verifying the ids are no longer present
* **Test assertion 6:** The two "id" parameters are not present in the network list

Pass / Fail criteria
'''''''''''''''''''''

This test evaluates the ability to assign IPv6 addresses in ipv6_ra_mode 'slaac'
and ipv6_address_mode 'slaac',
and verify the ping6 available VM can ping the other VM's v4 address in one network and two
v6 addresses with different prefixes in another network as well as the v6 subnets' gateway ips.
Specifically it verifies that:

* The IPv6 addresses in mode 'slaac' assigned successfully
* The VM can ping the other VM's IPv4 and IPv6 private addresses as well as the v6 subnets' gateway ips
* All items created using create commands are able to be removed using the returned identifiers

Post conditions
---------------

None