Page tree
Skip to end of metadata
Go to start of metadata

WARNING: This page is not currently maintained. Test areas will be defined in the test strategy document (being developed in this Gerrit proposal and tracked in this JIRA ticket - see current draft document), and specific test cases will be discussed and included in the Dovetail JIRA and Gerrit repository

This is the list of candidate test areas which have been proposed by community members for addition to the Dovetail test suite. These test areas will be evaluated under the Dovetail test case requirements, proposed for inclusion as patches in Gerrit against Dovetail, and reviewed by the Dovetail maintainers. Once approved, they will become part of the Dovetail test suite.

Brainstorming

This section is intended to help us get to quick consensus on the test priorities for Danube. The rest of the content of this page will be updated to be aligned with this section.

This is intended to help us discuss and collaboratively edit a set of priorities for the dovetail program in OPNFV.
  • This is itself a strawman proposal for how we can discuss this important topic. Alternatives are welcome, although the basic goal is that we can come to collaborative consensus as quickly as possible, with minimal barriers to participation in the discussion.
Also see:
High
  • Component verification: leverage all available tests to validate functional/API/etc capabilities of component distros
  • NFVI+VIM: start with well-established aspects of NFVI+VIM
  • Reference VNF portability: demonstrate portability and consistent operation for an ever-expanding suite of reference VNFs, which have been verified for most/all OPNFV distros
  • vIMS
  
  • Cross-controller dependent OPNFV features: verify operation of features that depend upon coordinated use of multiple components
  • SFC
  • Broadly supported OPNFV features: focus on features that are support in many/most distros and hardware platforms
        
Medium
  • Reliability: operation/performance under stress e.g. load and chaos
  • Performance: benchmarking
  • Security: static scans (vulnerabilities, licenses) and response to threats in operation
  • Infra lifecycle: deployment and day-2 operations
  • MANO: MANO-stack interop
Low
  • Narrowly-supported features: any features that are distro or hardware platform specific
  • Application (e.g. VNF) compliance with standards: while we may leverage reference VNFs as typical use cases their use should focus entirely upon verifying that the NFVI etc implementations result in a consistent user experience. The "user" in this case is the service provider, and consistency does not extend to whether the VNF itself or how it is operated adheres to any standards-based expectation on functionality.

Details on Test Areas

VIM Operations on Compute

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27493

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1VIM operations on ComputeCreate and show root certificatesCreate and show root certificatesVIM: Openstack
Components: Keystone, Nova
  
2VIM operations on ComputeFlavors CRD opsCreate, delete, list and show flavorsVIM: Openstack
Components: Keystone, Nova
  
3VIM operations on ComputeFloating IPs CRUD opsAllocate, delete, associate, disassociate, show and list floating ipsVIM: Openstack
Components: Keystone, Nova, Neutron
  
4VIM operations on ComputeImage metadata CRUD opsList, set, update, show, delete image metadatasVIM: Openstack
Components: Keystone, Nova
  
5VIM operations on ComputeImages CRUD opsDelete, list, show and create imagesVIM: Openstack
Components: Keystone, Nova, Glance
  
6VIM operations on ComputeKeypairs CRUD opsCreate, list, delete and show keypairsVIM: Openstack
Components: Keystone, Nova
  
7VIM operations on ComputeShow absolute limitsShow absolute limitsVIM: Openstack
Components: Keystone, Nova
  
8VIM operations on ComputeSecurity group rules CRUD opsCreate, delete and list security group rulesVIM: Openstack
Components: Keystone, Nova
  
9VIM operations on ComputeSecurity group CRUD opsCreate, delete, show, update and list security groupsVIM: Openstack
Components: Keystone, Nova
  
10VIM operations on ComputeInterfaces CRUD opsCreate, delete, show and list interfaces; attach and deattach ports to serversVIM: Openstack
Components: Keystone, Nova, Neutron
  
11VIM operations on ComputeList availability zonesList of availability zones and available servicesVIM: Openstack
Components: Keystone, Nova
  
12VIM operations on ComputeServers CRD opsCreate, delete, list and get serversVIM: Openstack
Components: Keystone, Nova, Neutron
  
13VIM operations on ComputeRebuild, resize and update serverRebuild, resize and update serverVIM: Openstack
Components: Keystone, Nova
  
14VIM operations on ComputeList and show instance actionsList and show instance actionsVIM: Openstack
Components: Keystone, Nova
  
15VIM operations on ComputeMultiple create serversVerify whether reservation id is in the response body of creating serversVIM: Openstack
Components: Keystone, Nova
  
16VIM operations on ComputeServer actionsChange server passwords; reboot, rebuild, resize, pause, unpause, suspend, resume, shelve, unshelve, stop, start, lock, unlock server; create backup; get console oupt; show vnc console;VIM: Openstack
Components: Keystone, Nova, Glance
  
17VIM operations on ComputeList server addressesList server addressesVIM: Openstack
Components: Keystone, Nova, Neutron
  
18VIM operations on ComputeServer groupCreate/delete server-groups with different policies.
policies = affinity/anti-affinity
It also adds the tests for list and get details of server-groups
VIM: Openstack
Components: Keystone, Nova
  
19VIM operations on ComputeServer metadata CRUD opsList, set, update, show, delete server metadataVIM: Openstack
Components: Keystone, Nova
  
20VIM operations on ComputeDelete and get server passwordDelete and get server passwordVIM: Openstack
Components: Keystone, Nova
  
21VIM operations on ComputeServer personality opsCreate and rebuild servers with personalityVIM: Openstack
Components: Keystone, Nova
  
22VIM operations on ComputeRescue and unrescue serversRescue and unrescue serversVIM: Openstack
Components: Keystone, Nova
  
23VIM operations on ComputeCreate server with special metadataCreate server with admin password; create server with existing server name; create specify keypair; update server name; create server with IPv6 onlyVIM: Openstack
Components: Keystone, Nova
  
24VIM operations on ComputeList virtual interfacesList virtual interfacesVIM: Openstack
Components: Keystone, Nova, Neutron
  
25VIM operations on ComputeAttach and deattach volumeAttach and deattach volume; list and show volume attachments; delete attached volumeVIM: Openstack
Components: Keystone, Nova, Cinder
  
26VIM operations on ComputeVolume snapshot CRD operationsCreate, show, list and delete volume snapshotsVIM: Openstack
Components: Keystone, Nova, Cinder
  
27VIM operations on ComputeVolumes CRUD opsCreate, show, list, update and delete volumesVIM: Openstack
Components: Keystone, Nova, Cinder
  
28VIM operations on ComputeShow and list extensionsShow and list extensionsVIM: Openstack
Components: Keystone, Nova
  
29VIM operations on ComputeLive block migrationMigrating to an invalid host should not change the statusVIM: Openstack
Components: Keystone, Nova
  
30VIM operations on ComputeList networksList networksVIM: Openstack
Components: Keystone, Nova, Neutron
  
31VIM operations on ComputeQuotas CRUD opsShow, create, update and delete quotasVIM: Openstack
Components: Keystone, Nova
  
32VIM operations on ComputeList and show tenant networksList and show tenant networksVIM: Openstack
Components: Keystone, Nova, Neutron
  
33VIM operations on ComputeList and show API versionsList and show API versionsVIM: Openstack
Components: Keystone, Nova
  
34VIM operations on ComputeAgents CRUDCreate, update, delete and list agentsVIM: Openstack
Components: Keystone, Nova
  
35VIM operations on ComputeAggregate CRUDCreate, update, delete, show and list agentsVIM: Openstack
Components: Keystone, Nova
  
36VIM operations on ComputeAuto-allocating networksTests auto-allocating networks with the v2.37 microversion.

The tenant must not have any network resources available to it so we can make sure that Nova calls to Neutron to automatically allocate the network topology.
VIM: Openstack
Components: Keystone, Nova, Neutron
  
37VIM operations on ComputeFixed ipsList, reserve and unreserve fixed ipsVIM: Openstack
Components: Keystone, Nova
  
38VIM operations on ComputeFlavors accessAdd and remove Flavor Access require admin privilegesVIM: Openstack
Components: Keystone, Nova
  
39VIM operations on ComputeFlavor Extra Spec API extensionSET, UNSET, UPDATE Flavor Extra specs require admin privileges.
GET Flavor Extra specs can be performed even by without admin privileges.
VIM: Openstack
Components: Keystone, Nova
  
40VIM operations on ComputeFloating IPs Bulk CRUDCreate, update, delete, and list Floating IPs Bulk that require admin privilegesVIM: Openstack
Components: Keystone, Nova, Neutron
  
41VIM operations on ComputeHost CRUD opsCreate, update, delete, show and list hosts using admin privilegesVIM: Openstack
Components: Keystone, Nova
  
42VIM operations on ComputeList and show hypervisorsList and show hypervisors using admin privilegesVIM: Openstack
Components: Keystone, Nova
  
43VIM operations on ComputeInstance usage audit logShow and list instance usage audit logVIM: Openstack
Components: Keystone, Nova
  
44VIM operations on ComputeLive block migrationLive migration between two hostsVIM: Openstack
Components: Keystone, Nova
  
45VIM operations on ComputeMigrations adminLive migrations and cold migrationsVIM: Openstack
Components: Keystone, Nova
  
46VIM operations on ComputeNova network APIList and show networkVIM: Openstack
Components: Keystone, Nova
  
47VIM operations on ComputeServers create ops on multinodesCreate servers on same host; create servers on different hostsVIM: Openstack
Components: Keystone, Nova
  
48VIM operations on ComputeList and show servicesList and show servicesVIM: Openstack
Components: Keystone, Nova
  
49VIM operations on ComputeList and show tenant usageList and show usage for tenantsVIM: Openstack
Components: Keystone, Nova
  

 

VIM Operations on Network

The Gerrit reference for this test area:  https://gerrit.opnfv.org/gerrit/#/c/27497

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1VIM operations on NetworkPorts CRU ops with allowed address pairCreate, list, update and show ports with allowed address pairVIM: Openstack
Components: Keystone, Neutron
  
2VIM operations on NetworkDHCP + IPv6 serviceTest DHCPv6 specific features using SLAAC, stateless and stateful settings for subnets. Also it shall check dual-stack functionality (IPv4 + IPv6 together).
The tests include:
generating of SLAAC EUI-64 address in subnets with various settings
receiving SLAAC addresses in combinations of various subnets
receiving stateful IPv6 addresses
addressing in subnets with router
VIM: Openstack
Components: Keystone, Neutron
  
3VIM operations on NetworkList all available extensionsList available extensions for the projectVIM: Openstack
Components: Keystone, Neutron
  
4VIM operations on NetworkPorts CRU ops with extra DHCP optionsCreate, list, show and update ports with the Extra DHCP optionsVIM: Openstack
Components: Keystone, Neutron
  
5VIM operations on NetworkFloating IPs CRUD opsCreate, update, delete, list, show and associate Floating IPsVIM: Openstack
Components: Keystone, Neutron
  
6VIM operations on NetworkMetering extensions CRD opsList, Show, Create, Delete Metering labels
List, Show, Create, Delete Metering labels rules
VIM: Openstack
Components: Keystone, Neutron
  
7VIM operations on NetworkNetworks and subnets CRUD opscreate a network for a project
list project's networks
show a project network details
create a subnet for a project
list project's subnets
show a project subnet details
network update
subnet update
delete a network also deletes its subnets
list external networks

All subnet tests are run once with ipv4 and once with ipv6.;
VIM: Openstack
Components: Keystone, Neutron
  
8VIM operations on NetworkPorts CRUD opsCreate, delete, list, show and update portsVIM: Openstack
Components: Keystone, Neutron
  
9VIM operations on NetworkRouters CRUD opsCreate, delete, list, show and update routers; add and remove router interfaceVIM: Openstack
Components: Keystone, Neutron
  
10VIM operations on NetworkSecurity groups CRUD opsCreate, delete, list, show and update security groups;Create, delete, show security group rules;VIM: Openstack
Components: Keystone, Neutron
  
11VIM operations on NetworkList service providersList service providersVIM: Openstack
Components: Keystone, Neutron
  
12VIM operations on NetworkSubnet pools CRUD opsCreate, delete, list, show and update subnet poolsVIM: Openstack
Components: Keystone, Neutron
  
13VIM operations on NetworkList API versionsList API versionsVIM: Openstack
Components: Keystone, Neutron
  
14VIM operations on NetworkAgents managementList, show and update agentsVIM: Openstack
Components: Keystone, Neutron
  
15VIM operations on NetworkDHCP agent schedulerList DHCP agents on hosting network; List networks hosted by one DHCP; Add and remove networks from DHCP agentsVIM: Openstack
Components: Keystone, Neutron
  
16VIM operations on NetworkExternal network CRUD opsCreate, delete, list, show and update external networksVIM: Openstack
Components: Keystone, Neutron
  
17VIM operations on NetworkL3 agent schedulerList routers that the given L3 agent is hosting.
List L3 agents hosting the given router.
Add and Remove Router to L3 agent
VIM: Openstack
Components: Keystone, Neutron
  
18VIM operations on NetworkQuotas CRU opsList, show, update, set, reset quotasVIM: Openstack
Components: Keystone, Neutron
  
19VIM operations on NetworkRouter DVRCreate Distributed Virtual Routing (DVR) router; create a centralized router; update a centralized router to DVR routerVIM: Openstack
Components: Keystone, Neutron
  

 

VIM Operations on Volume

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27499

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1VIM operations on VolumeList availability zonesList availability zonesVIM: Openstack
Components: Keystone, Nova, Cinder
  
2VIM operations on VolumeList extensionsList of all extensionsVIM: Openstack
Components: Keystone, Nova, Cinder
  
3VIM operations on VolumeSnapshot metadata CRUD opsCreate, show, update, delete metadata; Create, show, update, delete metadata items;VIM: Openstack
Components: Keystone, Nova, Cinder
  
4VIM operations on VolumeVolume metadata CRUD opsCreate, show, update, delete volume metadataVIM: Openstack
Components: Keystone, Cinder
  
5VIM operations on VolumeVolume transfer CRUD opsCreate, show, update, delete and list volume transfersVIM: Openstack
Components: Keystone, Cinder
  
6VIM operations on VolumeVolume actionsAttach and deattach volume to an instance; Verify that a volume bootable flag is retrieved; Verify that a volume's attachment information is retrieved; upload volume; reserve and unreserve volumes; update volume; Reset volume status; force delete volumesVIM: Openstack
Components: Keystone, Cinder, Glance
  
7VIM operations on VolumeVolume backup CRUD opsCreate, show, list, restore, delete volume backups;export and import volume backups; reset backup statusVIM: Openstack
Components: Keystone, Cinder
  
8VIM operations on VolumeVolumes cloneCreates a volume from another volume passing a size different from the source volume; Create a volume from the bootable volumeVIM: Openstack
Components: Keystone, Cinder
  
9VIM operations on VolumeExtend volumeExtend volumeVIM: Openstack
Components: Keystone, Cinder
  
10VIM operations on VolumeVolumes CRUD opsCreate, show, update, list and delete volumesVIM: Openstack
Components: Keystone, Cinder, Glance
  
11VIM operations on VolumeVolumes snapshot CRUD opsCreate a snapshot when volume status is in-use; Create, show, list, update and delete snapshots;VIM: Openstack
Components: Keystone, Cinder
  
12VIM operations on VolumeImage metadata RUD opsUpdate and show, delete image metadataVIM: Openstack
Components: Keystone, Nova, Cinder, Glance
  
13VIM operations on VolumeCreate and show volume with Mutil backendShow volume id which created by type without prefix;Show volume id which created by type wit prefixVIM: Openstack
Components: Keystone, Cinder
  
14VIM operations on VolumeQos specs CRUD opsCreate, list, delete, show, associate, disassociate, set/unset qos-specsVIM: Openstack
Components: Keystone, Cinder
  
15VIM operations on VolumeSnapshot actionsReset and update snapshot status; force delete snapshot;VIM: Openstack
Components: Keystone, Cinder
  
16VIM operations on VolumeList hostsList hostsVIM: Openstack
Components: Keystone, Nova, Cinder
  
17VIM operations on VolumeShow volume poolsShow volume poolsVIM: Openstack
Components: Keystone, Nova, Cinder
  
18VIM operations on VolumeVolume quotas RUD opsList, show,update and delete volume quotasVIM: Openstack
Components: Keystone, Cinder
  
19VIM operations on VolumeList volume servicesVolume service list requires admin privilegesVIM: Openstack
Components: Keystone, Cinder
  
20VIM operations on VolumeCreate and update volume snapshot quotasCreate and update volume snapshot quotasVIM: Openstack
Components: Keystone, Cinder
  
21VIM operations on VolumeVolume types extra specs CRUD opsCreate, show, delete, list and update volume types extra specsVIM: Openstack
Components: Keystone, Cinder
  
22VIM operations on VolumeVolume types CRUD opsCreate, update, show, delete and list volume typesVIM: Openstack
Components: Keystone, Cinder
  
23VIM operations on VolumeUser messages RD opsList, show and delete user messsagesVIM: Openstack
Components: Keystone, Cinder
  
24VIM operations on VolumeList and show backends capabilitiesList and show backends capabilitiesVIM: Openstack
Components: Keystone, Cinder
  
25VIM operations on VolumeAdd and list volume type accessAdd and list volume type accessVIM: Openstack
Components: Keystone, Cinder
  

 

VIM Operations on Image

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27219

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1VIM operations on ImageImages member CRUD opsCreate, show, delete, update, list images memberVIM: Openstack
Components: Keystone, Glance
 https://gerrit.opnfv.org/gerrit/#/c/27221
2VIM operations on ImageMetadata definition Namespaces basic functionalityCreate, show, update, delete and list metadata definition namespaceVIM: Openstack
Components: Keystone, Glance
 https://gerrit.opnfv.org/gerrit/#/c/27223
3VIM operations on ImageMetadata definition resource types basic functionalityCreate, show, update, delete and list metadata definition resource typesVIM: Openstack
Components: Keystone, Glance
 https://gerrit.opnfv.org/gerrit/#/c/27225
4VIM operations on ImageImages CRUD opsRegister, show , delete, update and list images; upload and show the image fileVIM: Openstack
Components: Keystone, Glance
 https://gerrit.opnfv.org/gerrit/#/c/27227
5VIM operations on ImageCreate and delete image tagsCreate and delete image tagsVIM: Openstack
Components: Keystone, Glance
 https://gerrit.opnfv.org/gerrit/#/c/27231


VIM Operations on Identity

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27501

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1VIM operations on IdentityList extensionsList all the extensionsVIM: Openstack
Components: Keystone
  
2VIM operations on IdentityAPI discovery featuresShow API version; show API media types; show API statusVIM: Openstack
Components: Keystone
  
3VIM operations on IdentityProjects CRUD opsList, create, delete and update projects; associate a user to a projectVIM: Openstack
Components: Keystone
  
4VIM operations on IdentityToken CRUD opsCreate, show, delete, rescope token; Note: An unscoped token can be requested, that token can be used to request a scoped token. The scoped token can be revoked, and the original token used to get a token in a different project.VIM: Openstack
Components: Keystone
  
5VIM operations on IdentityUpdate passwordUser update own passwordVIM: Openstack
Components: Keystone
  
6VIM operations on IdentityUser ec2 credentials CRD opsCreate, show, list and delete user ec2 credentialsVIM: Openstack
Components: Keystone
  
7VIM operations on IdentityCredentials CRUD opsCreate, show, update, delete and list credentialsVIM: Openstack
Components: Keystone
  
8VIM operations on IdentityDefault project id1. create a domain
2. create a project in the domain
3. create a user in the domain, with the previous project as his default project
4. get roles and find the admin role
5. grant the admin role to the user on his project
6. create a new client with user's credentials
7. verify the user's token and see that it is scoped to the project
VIM: Openstack
Components: Keystone
  
9VIM operations on IdentityDomains CRUD opsCreate, update, delete and list domainsVIM: Openstack
Components: Keystone
  
10VIM operations on IdentityEndpoint CRUD opsCreate, update, delete, show and list endpointsVIM: Openstack
Components: Keystone
  
11VIM operations on IdentityGroups CRUD opsCreate, update, delete, show and list groups; add, list and delete users in groups;VIM: Openstack
Components: Keystone
  
12VIM operations on IdentityInherits CRUD opsCreate, assign, list, check, revoke roles on domains user/domains group/projects user/projects group/domains/ project treesVIM: Openstack
Components: Keystone
  
13VIM operations on IdentityPolicy CRUD opsList, create, update and delete policiesVIM: Openstack
Components: Keystone
  
14VIM operations on IdentityRegions CRUD opsCreate, show, update, delete and list regionsVIM: Openstack
Components: Keystone
  
15VIM operations on IdentityRoles CRUD opsCreate, show, update, delete and list roles; grant ,list and revoke role to user/group on project/domain/VIM: Openstack
Components: Keystone
  
16VIM operations on IdentityServices CRUD opsCreate, show, update, delete and list servicesVIM: Openstack
Components: Keystone
  
17VIM operations on IdentityTrusts CRU opsCreate, show, delete and list trusts; updates are not supported for trustsVIM: Openstack
Components: Keystone
  
18VIM operations on IdentityUsers CRUD opsCreate, update, show, delete and list users; Request for token authentication with/without a valid token in headerVIM: Openstack
Components: Keystone
  

NFVI

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27503

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1NetworkvPingtwo vms setup in the same subnet and can ping each other (ssh, userdata, IPv4, IPv6(afraid not support now MatthewLi))VIM: Openstack
Components: Keystone, Nova, Neutron, Glance
  
2NetworkvRouterTwo VMs in two different subnets, connected by a Neutron virtual router, can ping each otherVIM: Openstack
Components: Keystone, Nova, Neutron, Glance
  
3NetworkSecurity rulesVerify that a security rule prevents a type of traffic, remove rule, verify that traffic passes, add it back, test that traffic is stoppedVIM: Openstack
Components: Keystone, Nova, Neutron, Glance
  
4NetworkExternal routingVerify that a VM can access hosts external to the VIMVIM: Openstack
Components: Keystone, Nova, Neutron, Glance
  
5Network ...fill out CRUD operations for "network/subnet/router/port" operationsVIM: Openstack
Components: Keystone, Nova, Neutron, Glance
  
6NetworkNetwork advanced server opsCheck VM connectivity after some advanced instance operations executed:

* Stop/Start an instance
* Reboot an instance
* Rebuild an instance
* Pause/Unpause an instance
* Suspend/Resume an instance
* Resize an instance
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
7NetworkNetwork basic operationsThis smoke test suite assumes that Nova has been configured to
boot VM's with Neutron-managed networking, and attempts to
verify network connectivity as follows:

There are presumed to be two types of networks: tenant and
public. A tenant network may or may not be reachable from the
Tempest host. A public network is assumed to be reachable from
the Tempest host, and it should be possible to associate a public
('floating') IP address with a tenant ('fixed') IP address to
facilitate external connectivity to a potentially unroutable
tenant IP address.
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
8NetworkNetwork v61. Create network with subnets:
1.1. one IPv4 and
1.2. one or more IPv6 in a given address mode
2. Boot 2 VMs on this network
3. Allocate and assign 2 FIP4
4. Check that vNICs of all VMs gets all addresses actually assigned
5. Each VM will ping the other's v4 private address
6. If ping6 available in VM, each VM will ping all of the other's v6
addresses as well as the router's
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
9NetworkSecurity groups basic opsThis test case assumes that Nova has been configured to boot VM's with Neutron-managed networking, and attempts to verify cross tenant connectivity as follows
ssh:
in order to overcome "ip namespace", each tenant has an "access point"
VM with floating-ip open to incoming ssh connection allowing network
commands (ping/ssh) to be executed from within the
tenant-network-namespace
Tempest host performs key-based authentication to the ssh server via
floating IP address
connectivity test is done by pinging destination server via source server
ssh connection.
success - ping returns
failure - ping_timeout reached
multi-node:
Multi-Node mode is enabled when CONF.compute.min_compute_nodes > 1.
Tests connectivity between servers on different compute nodes.
When enabled, test will boot each new server to different
compute nodes.
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
10NFVIBasic minimum scenario test1. Create image
2. Create keypair
3. Boot instance with keypair and get list of instances
4. Create volume and show list of volumes
5. Attach volume to instance and getlist of volumes
6. Add IP to instance
7. Create and add security group to instance
8. Check SSH connection to instance
9. Reboot instance
10. Check SSH connection to instance after reboot
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
11ComputeOPNFV_YARDSTICK_TC010Measure the memory read latency for varying memory sizes and strides. Whole memory hierarchy is measured including all levels of cache.Colorado Scenario:due to floating IP,not support odl_l2, bgnvpn
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder, Heat
  
12ComputeOPNFV_YARDSTICK_TC012Measure the rate at which data can be read from and written to the memory (this includes all levels of memory).Colorado Scenario: due to floating IP,not support odl_l2, bgnvpn
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder, Heat
  
13ComputeOPNFV_YARDSTICK_TC014To evaluate the IaaS processing speed with regards to score of single cpu running and parallel running The purpose is also to be able to spot trends. Test results, graphs and similar shall be stored for comparison reasons and product evolution understanding between different OPNFV versions and/or configurations.Colorado Scenario: due to floating IP,not support odl_l2, bgnvpn
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder, Heat
  
14ComputeOPNFV_YARDSTICK_TC055To evaluate the IaaS compute capacity with regards to hardware specification, including number of cpus, number of cores, number of threads, available memory size and total cache size. Test results, graphs and similar shall be stored for comparison reasons and product evolution understanding between different OPNFV versions and/or configurations.Colorado Scenario:due to floating IP,not support odl_l2, bgnvpn
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder, Heat
  
15ComputeAggregates basic opsCreates an aggregate within an availability zone
1. Adds a host to the aggregate
2. Checks aggregate details
3. Updates aggregate's name
4. Removes host from aggregate
5. Deletes aggregate
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
16ComputeServer advanced operationsThis test case stresses some advanced server instance operations:
* Resizing a volume-backed instance
* Sequence suspend resume
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
17ComputeServer basic operationsThis smoke test case follows this basic set of operations:
* Create a keypair for use in launching an instance
* Create a security group to control network access in instance
* Add simple permissive rules to the security group
* Launch an instance
* Perform ssh to instance
* Verify metadata service
* Verify metadata on config_drive
* Terminate the instance
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
18ComputeServer multinodeThis is a set of tests specific to multinode testingVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
19ComputeShelve instanceThe following is the scenario outline:
* boot an instance and create a timestamp file in it
* shelve the instance
* unshelve the instance
* check the existence of the timestamp file in the unshelved instance
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
20ComputeSnapshot patternThe following is the outline:
* boot an instance and create a timestamp file in it
* snapshot the instance
* boot a second instance from the snapshot
* check the existence of the timestamp file in the second instance
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
21ComputeStamp patternThis test is for snapshotting an instance/volume and attaching the volume
created from snapshot to the instance booted from snapshot.
The following is the scenario outline:
1. Boot an instance "instance1"
2. Create a volume "volume1"
3. Attach volume1 to instance1
4. Create a filesystem on volume1
5. Mount volume1
6. Create a file which timestamp is written in volume1
7. Unmount volume1
8. Detach volume1 from instance1
9. Get a snapshot "snapshot_from_volume" of volume1
10. Get a snapshot "snapshot_from_instance" of instance1
11. Boot an instance "instance2" from snapshot_from_instance
12. Create a volume "volume2" from snapshot_from_volume
13. Attach volume2 to instance2
14. Check the existence of a file which created at 6. in volume2
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
22ComputeVolume boot patternThis test case attempts to reproduce the following steps:

* Create some bootable volume importing a image
* Boot an instance from the bootable volume
* Write content to the volume
* Delete an instance and Boot a new instance from the volume
* Check written content in the instance
* Create a volume snapshot while the instance is running
* Boot an additional instance from the new snapshot based volume
* Check written content in the instance booted from snapshot
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
23Storageyardstick_tc005Fio test is invoked in a host VM on a compute blade, a job file as well as parameters are passed to fio and fio will start doing what the job file tells it to do.Colorado Scenario: due to floating IP,not support odl_l2, bgnvpn
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder, Heat
  
24StorageEncrypted volumesThis test is for verifying the functionality of encrypted volumes.

For both LUKS and cryptsetup encryption types, this test performs
the following:
* Creates an image
* Boots an instance from the image
* Creates an encryption type (as admin)
* Creates a volume of that encryption type (as a regular user)
* Attaches and detaches the encrypted volume to the instance
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  

High Availability (HA)  

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27505

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1HAOPNFV_YARDSTICK_TC019This test case will verify the high availability of the service provided by compute on control node.VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  
2HAOPNFV_YARDSTICK_TC045This test case will verify the high availability of the network service provided by network on control nodeVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  
3HAOPNFV_YARDSTICK_TC046This test case will verify the high availability of the user service provided by Identity on control nodeVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
4HAOPNFV_YARDSTICK_TC047This test case will verify the high availability of the image service provided by image on control nodeVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
5HAOPNFV_YARDSTICK_TC048This test case will verify the high availability of the volume service provided by network on control nodeVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
  
6HAOPNFV_YARDSTICK_TC049This test case will verify the high availability of the storage service provided by object storage on control nodeVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
Additional Components: Swift
  
7HAOPNFV_YARDSTICK_TC050This test case will verify the high availability of control node. When one of the controller failed to connect the network, which breaks down the Openstack services on this node. These Openstack service should able to be accessed by other controller nodes, and the services on failed controller node should be isolatedVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  
8HAOPNFV_YARDSTICK_TC051This test case will verify the high availability of control node. When the CPU usage of a specified controller node is stressed to 100%, which breaks down the Openstack services on this node. These Openstack service should able to be accessed by other controller nodes, and the services on failed controller node should be isolatedVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  
9HAOPNFV_YARDSTICK_TC052This test case will verify the high availability of control node. When the disk I/O of a specified disk is blocked, which breaks down the Openstack services on this node. Read and write services should still be accessed by other controller nodes, and the services on failed controller node should be isolatedVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  
10HAOPNFV_YARDSTICK_TC053This test case will verify the high availability of the load balance service(current is HAProxy) that supports OpenStack on controller node. When the load balance service of a specified controller node is killed, whether other load balancers on other controller nodes will work, and whether the controller node will restart the load balancer are checkedVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  
11HAOPNFV_YARDSTICK_TC054This test case will verify the high availability for virtual ip in the environment. When master node of virtual ip is abnormally shutdown, connection to virtual ip and the services binded to the virtual IP it should be OKVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
SDN: not support SDN
Sepcial requirements: 3 control nodes with HA
  

IPv6

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27509

Link to the introduction of IPv6 test cases status: Ipv6 Test Cases Status

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1IPv6Test Case 1: Create and Delete an IPv6 Network, Port and SubnetTo test if Create and Delete an IPv6 Network, Port and Subnet is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
2IPv6Test Case 2: Create, Update and Delete an IPv6 Network and SubnetTo test if Create, Update and Delete an IPv6 Network and Subnet is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
3IPv6Test Case 3: Check External Network VisibilityTo test if Check External Network Visibility is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
4IPv6Test Case 4: List IPv6 Networks and Subnets of a TenantTo test if List IPv6 Networks and Subnets of a Tenant is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
5IPv6Test Case 5: Show Information of an IPv6 Network and SubnetTo test if Show Information of an IPv6 Network and Subnet is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
6IPv6Test Case 6: Create an IPv6 Port in Allowed Allocation PoolsTo test if Create an IPv6 Port in Allowed Allocation Pools is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
7IPv6Test Case 7: Create an IPv6 Port without Security GroupsTo test if Create an IPv6 Port without Security Groups is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
8IPv6Test Case 8: Create, Update and Delete an IPv6 PortTo test if Create, Update and Delete an IPv6 Port is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
9IPv6Test Case 9: List IPv6 Ports of a TenantTo test if List IPv6 Ports of a Tenant is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
10IPv6Test Case 10: Show Information of an IPv6 PortTo test if Show Information of an IPv6 Port is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
11IPv6Test Case 11: Add Multiple Interfaces for an IPv6 RouterTo test if Add Multiple Interfaces for an IPv6 Router is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
12IPv6Test Case 12: Add and Remove an IPv6 Router Interface with port_idTo test if Add and Remove an IPv6 Router Interface with port_id is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
13IPv6Test Case 13: Add and Remove an IPv6 Router Interface with subnet_idTo test if Add and Remove an IPv6 Router Interface with subnet_id is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
14IPv6Test Case 14: Create, Update, Delete, List and Show an IPv6 RouterTo test if Create, Update, Delete, List and Show an IPv6 Router is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
15IPv6Test Case 15: Create, Update, Delete, List and Show an IPv6 Security GroupTo test if Create, Update, Delete, List and Show an IPv6 Security Group is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
16IPv6Test Case 16: Create, Delete and Show Security Group RulesTo test if Create, Delete and Show Security Group Rules is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
17IPv6Test Case 17: List All Security GroupsTo test if List All Security Groups is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
18IPv6Test Case 18: IPv6 Address Assignment - DHCPv6 StatelessTo test if IPv6 Address Assignment - DHCPv6 Stateless is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
19IPv6Test Case 19: IPv6 Address Assignment - Dual Stack, DHCPv6 StatelessTo test if IPv6 Address Assignment - Dual Stack, DHCPv6 Stateless is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
20IPv6Test Case 20: IPv6 Address Assignment - Multiple Prefixes, DHCPv6 StatelessTo test if IPv6 Address Assignment - Multiple Prefixes, DHCPv6 Stateless is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
21IPv6Test Case 21: IPv6 Address Assignment - Dual Stack, Multiple Prefixes, DHCPv6 StatelessTo test if IPv6 Address Assignment - Dual Stack, Multiple Prefixes, DHCPv6 Stateless is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
22IPv6Test Case 22: IPv6 Address Assignment - SLAACTo test if IPv6 Address Assignment - SLAAC is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
23IPv6Test Case 23: IPv6 Address Assignment - Dual Stack, SLAACTo test if IPv6 Address Assignment - Dual Stack, SLAAC is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
24IPv6Test Case 24: IPv6 Address Assignment - Multiple Prefixes, SLAACTo test if IPv6 Address Assignment - Multiple Prefixes, SLAAC is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
25IPv6Test Case 25: IPv6 Address Assignment - Dual Stack, Multiple Prefixes, SLAACTo test if IPv6 Address Assignment - Dual Stack, Multiple Prefixes, SLAAC is OK.VIM: Openstack Components: Keystone, Nova, Neutron, Glance Special Requirements: ipv6 network configuration  
26IPv6Test Case 26: Service VM as an IPv6 vRouterOPNFV_YARDSTICK_TC027
To do a basic verification that IPv6 connectivity is within acceptable boundaries when ipv6 packets travel between hosts located on same or different compute blades.
Colorado Scenario: nosdn, nofeature
VIM: Openstack
Components: Keystone, Nova, Neutron, Glance
SDN: not support SDN
  

 

VPN

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27511

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1VPNVPN CRUD
1. Create VPN instance and check command return code
2. Check if VPN instance is present
3. Create IETF VM interface and check return code
4. Verify IETF VM interface
5. Create VPN interface for IETF interface
6. Verify VPN interface
7. Verify FIB entry after create
8. Delete VM VPN interface
9. Verify after deleting VM VPN interface
10. Delete VPN instance
11. Verify after deleting VPN instance
12. Delete VM IETF interface
13. Verify after deleting VM IETF interface
14. Verify FIB entry after delete
   
2VPNBGP VPN CRUD1. Create BGPVPN 
2. Create BGPVPN with malformatted route target (e.g. ASN:NN) should fail.
3. Create BGPVPN with invalid route target (e.g. 65536:0) should fail.
4. Getting the VPN list works without producing an error.
5. Updating an existing BGPVPN works.
6. Displaying parameters of an existing BGPVPN works.
7. Deleting a BGPVPN works.
8. Associating an existing BGPVPN with a Neutron network works
9. Getting the associated Neutron network works.
10. Deleting the network association works.
11. Associating an existing BGPVPN with a Neutron Router works
12. Getting the associated Neutron router works.
13. Deleting the router association works
   
3VPNData Center Gateway integrationData Center Gateway integration, check if routes are correctly exchanged between SDN controller and datacenter gateway   
4VPNInter-DC communicationInter-DC communication, Check if communication between two data centers connected through an MPLS backbone works.   
5VPNSubnet connectivityVPN provides connectivity between subnets. different subnets cannot reach each other unless they are connected to the same Router.Colorado Scenario: odl_l2, bgpvpn
VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
SDN: ODL
Feature: no feature needed
  
6VPNTenant separationVPNs enable using the same IP address ranges in different VPNs, which is an important feature for tenant separation in the DC. This test verifies if the correct VM is reached under a given IP address when IP addresses are used multiple times in the same DC.Colorado Scenario: odl_l2, bgpvpn
VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
SDN: ODL
Feature: no feature needed
  
7VPNVPN provides connectivity between subnets using router associationVPN provides connectivity between subnets using router associationColorado Scenario: odl_l2, bgpvpn
VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
SDN: ODL
Feature: no feature needed
  
8VPNA subnet with a router attached can be associated to a VPN with network association and given a floating IPA subnet with a router attached can be associated to a VPN with network association and given a floating IPColorado Scenario: odl_l2, bgpvpn
VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
SDN: ODL
Feature: no feature needed
  


Fault Management(Doctor)

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27513

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1Fault managementRelaunch instance ?When an instance fails, can the platform restart the instance automatically?   
2Fault managementScale-up ?Can a new instance of a given type be launched when a certain load is hit?   
3Fault managementSubscribe to a fault eventListen for an instance fault , and verify that when the instance is killed we hear about it   
4Fault managementfailure notificationTo test VM failure notification time. Boot a VM and create an alarm event in Ceilometer using the consumer ip. Once Doctor components are started, a failure is injected to the system, then the consumer receives a failure notification.VIM: Openstack
Components: Keystone, Nova, Neutron, Glance
Additional component: Cinder, Ceilometer, Aodh, Congress, Vitrage
Feature: Doctor
  

KVM

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27515

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1KvmTimer Test without workloadMeasure system high resolution by using Cyclictest, getting latencies as results.VIM: Openstack
Components: Keystone, Nova, Neutron, Glance
Special Requirments:
1. BIOS setup
2. kernel configuration
3. run time environment setup
refer to https://wiki.opnfv.org/display/kvm/KVM4NFV+Test++Environment
  

Parser

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27517

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1Parserverify the function of Yang-to-Tosca in ParserOffers the capability to translate yang based scriptors to tosca formate templatesVIM: Openstack not necessary, run in jumpserver
Feature: no feature needed
  
2Parserverify the function of Policy-to-Tosca in ParserEnables policy related fields in tosca could be translated into heat orchestration template correctlyVIM: Openstack not necessary, run in jumpserver
Feature: no feature needed
  
3Parserverify the function of Tosca-to-Heat in ParserHeat-translator call class of ToscaTemplate in tosca-parser firstly to validate and parse input yaml file, then tranlate the file into hot fileVIM: Openstack not necessary, run in jumpserver
Feature: no feature needed
  

virtual Traffic Classifier

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27519

IDTypeTest CaseDescriptionPre-condition & requirementsStatusReferences
1VTCopnfv_yardstick_tc020To verify that a newly instantiated vTC is ‘alive’ and functional and its instantiation is correctly supported by the infrastructureVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
Additional Components: Heat
Special:
Hardware:
1. physical node hosting the packet generator must have 2 NICs which are DPDK compatible
2. The switch used must support multicast traffic and IGMP snooping
3. The corresponding ports to which the cables are connected need to be configured as VLAN trunks using two of the VLAN IDs available for Neutron.
Software: vtc, DPDK_pktgen, python-dev, python-pip, python-mock, tcpreplay, libpcap-dev, smcroute
  
2VTCopnfv_yardstick_tc021To verify that a newly instantiated vTC is ‘alive’ and functional and its instantiation is correctly supported by the infrastructure in the presence of noisy neighbours.VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
Additional Components: Heat
Special:
Hardware:
1. physical node hosting the packet generator must have 2 NICs which are DPDK compatible
2. The switch used must support multicast traffic and IGMP snooping
3. The corresponding ports to which the cables are connected need to be configured as VLAN trunks using two of the VLAN IDs available for Neutron.
Software: vtc, DPDK_pktgen, python-dev, python-pip, python-mock, tcpreplay, libpcap-dev, smcroute
  

Copper

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27521

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1CopperDMZ PlacementPause VMs running in a DMZ zone, if the image running is not allowed to run in that zoneVIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
Additional Components: Ceilometer
Feature: no feature needed
  
2CopperSMTP IngressIdentify VMs that have TCP port 25 open for ingressVIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
Additional Components: Ceilometer
Feature: no feature needed
  
3CopperReserved SubnetDelete any subnets created in restricted network rangesVIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone
Additional Components: Ceilometer
Feature: no feature needed
  

Promise

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27523

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1PromiseCapacity ManagementIncluding add providers, update the capacity, and query the current capacity and utilization of a providerVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
Feature: no feature needed
  
2PromiseReservation ManagementAllows a Consumer to request reservations for resource capacity (create, update, cancel, query reservations)VIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
Feature: no feature needed
  
3PromiseAllocation ManagementCreate an instance of specified resource(s) for immediate use utilizing capacity from the pool and destroy an existing server instance and release it back to the poolVIM: Openstack
Components: Keystone, Nova, Neutron, Glance, Cinder
Feature: no feature needed
  

Multisite

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27525

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1MultisiteQuota Management APIThis testcase includes 9 functions:
1. Update global limit for a tenant
2. Get global limit for a tenant
3. A tenant can also get the global limit by himself
4. Get defaults limits
5. Get total usage for a tenant
6. A tenant can also get the total usage by himself
7. On demand quota sync
8. Delete specific global limit for a tenant
9. Delete all kingbird global limit for a tenant
Colorado Scenario: os-nosdn-multisite-ha
VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone, Glance, ceilometer
SDN: not support SDN
Feature: no feature needed
  
2MultisiteQuota Class APIThis testcase includes 3 functions:
1. Update default quota class
2. Get default quota class
3. Delete default quota class
Colorado Scenario:os-nosdn-multisite-ha
VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone, Glance, ceilometer
SDN: not support SDN
Feature: no feature needed
  


SDN controller(ODL)

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27533

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1ODLrestconf modulesverify Restconf is OKColorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
2ODLneutron reachabilityGet the complete list of networks
Get the complete list of subnets
Get the complete list of ports
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
3ODLneutron networksChecking Network created in OpenStack are pushed
to OpenDaylight
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
4ODLneutron subnetsChecking Subnets created in OpenStack are pushed
to OpenDaylight
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
5ODLneutron portsChecking Port created in OpenStack are pushed
to OpenDaylight
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
6ODLneutron delete portsChecking Port deleted in OpenStack are deleted
also in OpenDaylight
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
7ODLneutron delete subnetsChecking Subnets deleted in OpenStack are deleted
also in OpenDaylight
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  
8ODLneutron delete networksChecking Network deleted in OpenStack are deleted
also in OpenDaylight
Colorado Scenario: odl_l2 or odl_l3
VIM: Openstack
Components: Neutron, ODL
Feature: no feature needed
  

SDN controller(ONOS)

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27535

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1ONOSVirtual Network NBI Test -Network PostBelonged to tier FUNCvirNetNB, this is create Network northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Data via HTTP,
3) Get Data via HTTP,
4) Compare Send Id and Get Id
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
2ONOSNetwork UpdateBelonged to tier FUNCvirNetNB, this is update Network northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Data via HTTP,
3) Update Data via HTTP,
4) Get Data via HTTP,
5) Compare Update data
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
3ONOSNetwork DeleteBelonged to tier FUNCvirNetNB, this is delete Network northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Data via HTTP,
3) Delete Data via HTTP,
4) Get Data is NULL
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
4ONOSSubnet PostBelonged to tier FUNCvirNetNB, this is create Subnet northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Network Data via HTTP(Post Subnet need post network),
3) Post Subnet Data via HTTP,
4) Get Subnet Data via HTTP,
5) Compare Post Subnet Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
5ONOSSubnet UpdateBelonged to tier FUNCvirNetNB, this is update Subnet northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Network Data via HTTP(Post Subnet need post network),
3) Post Subnet Data via HTTP,
4) Update Subnet Data via HTTP,
5) Get Subnet Data via HTTP,
6) Compare Subnet Data,
7) Delete Subnet via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
6ONOSSubnet DeleteBelonged to tier FUNCvirNetNB, this is delete Subnet northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Network Data via HTTP(Post Subnet need post network),
3) Post Subnet Data via HTTP,
4) Delete Subnet Data via HTTP,
5) Get Subnet Data is NULL
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
7ONOSPort PostBelonged to tier FUNCvirNetNB, this is create Virtualport northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Network Data via HTTP(Post Subnet need post network),
3) Post Subnet Data via HTTP(Post port need post subnet),
4) Post Port Data via HTTP,
5) Get Port Data via HTTP,
6) Compare Post Port Data,
7) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
8ONOSPort UpdateBelonged to tier FUNCvirNetNB, this is update Virtualport northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Network Data via HTTP(Post Subnet need post network),
3) Post Subnet Data via HTTP(Post port need post subnet),
4) Post Port Data via HTTP,
5) Update Port Data via HTTP, 6) Get Port Data via HTTP,
7) Compare Post Port Data,
8) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
9ONOSPort DeleteBelonged to tier FUNCvirNetNB, this is delete Virtualport northbound test, in order to determine if North bound can handle the request, including steps:
1) Generate Post Data,
2) Post Network Data via HTTP(Post Subnet need post network),
3) Post Subnet Data via HTTP(Post port need post subnet),
4) Post Port Data via HTTP,
5) Delete Port Data via HTTP,
6) Get Port Data via HTTP,
7) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
10ONOSRouter PostBelonged to tier FUNCvirNetNBL3, this is create Router northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post Router need post network),
2) Post Router Data via HTTP,
3) Get Router Data via HTTP,
4) Compare Post Router Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
11ONOSRouter UpdateBelonged to tier FUNCvirNetNBL3, this is update Router northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post Router need post network),
2) Post Router Data via HTTP,
3) Update Router Data via HTTP,
4) Get Router Data via HTTP,
5) Compare Router Data,
6) Delete Router via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
12ONOSRouter DeleteBelonged to tier FUNCvirNetNBL3, this is delete Router northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post Router need post network),
2) Post Router Data via HTTP,
3) Delete Router Data via HTTP,
4) Get Router Data is NULL
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
13ONOSRouterInterface PostBelonged to tier FUNCvirNetNBL3, this is create RouterInterface northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network),
2) Post Subnet Data via HTTP(Post port need post subnet),
3) Post Port Data via HTTP,
4) Post Router Data via HTTP,
5) Put RouterInterface Data via HTTP,
6) Get RouterInterface Data via HTTP,
7) Compare Post Port Data,
8) Del RouterInterface Data via HTTP,
9) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
14ONOSRouterInterface DeleteBelonged to tier FUNCvirNetNBL3, this is delete RouterInterface northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network),
2) Post Subnet Data via HTTP(Post port need post subnet),
3) Post Port Data via HTTP,
4) Post Router Data via HTTP,
5) Post RouterInterface Data via HTTP,
6) Del RouterInterface Data via HTTP,
7) Delete Port Data via HTTP,
8) Get Port Data is NULL,
9) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
15ONOSFloatingIp PostBelonged to tier FUNCvirNetNBL3, this is create Floatingip northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network)
2) Post Subnet Data via HTTP(Post port need post subnet)
3) Post Port Data via HTTP
4) Post Router Data via HTTP
5) Get Port Data via HTTP
6) Post FloatingIp Data via HTTP
7) Get Port Data via HTTP
8) Get FloatingIp Data via HTTP
9) Get FloatingIp Data via HTTP
10) Compare Post FloatingIp Data
11) Post FloatingIp Clean Data via HTTP
12) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
16ONOSFloatingIp UpdateBelonged to tier FUNCvirNetNBL3, this is updateFloatingip northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network)
2) Post Subnet Data via HTTP(Post port need post subnet)
3) Post Port Data via HTTP
4) Post Router Data via HTTP
5) Post FloatingIp Data via HTTP
6) Post Delete Data via HTTP
7) Post NewPort Data via HTTP
8) Post NewFloatingIp Data via HTTP
9) Get NewFloatingIp Data via HTTP
10) Compare Post FloatingIp Data
11) Post FloatingIp Clean Data via HTTP
12) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
17ONOSFloatingIp DeleteBelonged to tier FUNCvirNetNBL3, this is delete Floatingip northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network)
2) Post Subnet Data via HTTP(Post port need post subnet)
3) Post Port Data via HTTP
4) Post Router Data via HTTP
5) Post FloatingIp Data via HTTP
6) Post FloatingIp Clean Data via HTTP
7) Get FloatingIp Data is NULL
8) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
18ONOSGateway PostBelonged to tier FUNCvirNetNBL3, this is create Gateway northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network)
2) Post Subnet Data via HTTP(Post port need post subnet)
3) Post Port Data via HTTP
4) Post Router Data via HTTP
5) Get Gateway Data via HTTP
6) Compare Post Gateway Data
7) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
19ONOSGateway UpdateBelonged to tier FUNCvirNetNBL3, this is update Gateway northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network)
2) Post Subnet Data via HTTP(Post port need post subnet)
3) Post Port Data via HTTP
4) Post Router Data via HTTP
5) Post New Router Data via HTTP
6) Get Gateway Data via HTTP
7) Compare Post Gateway Data
8) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  
20ONOSGateway DeleteBelonged to tier FUNCvirNetNBL3, this is delete Gateway northbound test, in order to determine if North bound can handle the request, including steps:
1) Post Network Data via HTTP(Post port need post network)
2) Post Subnet Data via HTTP(Post port need post subnet)
3) Post Port Data via HTTP
4) Post Router Data via HTTP
5) Post Del Gateway Data via HTTP
6) Get Gateway Data via HTTP
7) If Gateway Data is NULL
8) Clean Data via HTTP
Colorado Scenario: ONOS
VIM: Openstack
Components: Neutron, ONOSrest
Feature: no feature needed
  


Open source VNF running on NFVI

The Gerrit reference for this test area: https://gerrit.opnfv.org/gerrit/#/c/27539

IDTypeTest CaseDescriptionPre-condition & requirementsStatusGerrit References
1Open Source VNFcloudify_imsThis test case deploys an OpenSource vIMS solution from Clearwater using the Cloudify orchestrator. It also runs some signaling traffic.VIM: Openstack
Components: Nova, Cinder, Neutron, KeyStone, Glance
Special Requirements: Cloudify
  

 

 

  • No labels

4 Comments

  1. Based on today's Dovetail meeting tried summarize the category Basic VIM Operations (vim-ops) summary to carry forward to link to test cases. Have not removed the details as listed by vim-ops details and we will keep revising till we get a relation between test design, testcases and tie them back to gerrit for test-sutie and test cases. So please feel free to continue adding test cases while we work with IPv6 test templates to co-relate the two. Like Mathew to review and correct the summary. Thanks Prakash

    1. hi  Prakash, looks good to see progress. Actually, I don't know the test case selection criteria, searched in Obsolete: high level topics (to be removed), however, it's empty, anyway, if it's brain storm here, it's good. 

      from test case technical area, some experience are given here. 1) for vimops, if the sub-testcases of each test case can be found out in tempest repo(further, the version is very important, different version tag is suitable to different openstack versions, Mitaka, Newton, etc, test case can be changed as the version goes on), maybe a useful reference is defcore, such as http://git.openstack.org/cgit/openstack/defcore/tree/2016.08.json I wound't say that we are the same, it can be good input and reference added by OPNFV requirement. 2) for ipv6, it seems we are at a right way 3) for networking/compute/storage, also HA, functest/yardstick can provide test cases here and we have people who are familiar with them, some gaps are needed, such as ipv6 vPing 

  2. Please, read carefully doctor requirement docs. Test cases in "Fault Management - test cases" seems not aligned with doctor project's objectives/deliverable. Or, may I edit this page?