c7815d83c8
* add kernel options for DPDK on VF * update sriov, failover, DPDK on VF test with new contrail-controller role Change-Id: Ic8065c29c1df8b55149d353852a0c51e52ed867c
12 KiB
System testing
Check no connectivity between VMs in different tenants via Contrail network
ID
contrail_vm_connection_in_different_tenants
Description
Check no connectivity between VMs in different tenants via Contrail network
Complexity
Advanced
Steps
- Login as admin to Openstack Horizon UI
- Create 2 new tenants (the tenant networks under test must have intersecting or the same IP address spaces and the must be no policy enabled, which allows the traffic between tenants)
- Launch 2 new instance in different tenants
- Check ping connectivity between instances
- Connect to Compute Node via SSH and check the VM's connections
- Verify on Contrail controller WebUI that networks are there and VMs are attached to different networks.
Expected results
Ping should not get a response, VM's connections should be in the different ethernet device, VMs are present in Contrail controller WebUI
Check connectivity via external Contrail network without floating IP
ID
contrail_vm_connection_without_floating_ip
Description
Check connectivity VMs with external network without floating IP via Contrail network
Complexity
Advanced
Steps
- Login as admin to Openstack Horizon UI
- Launch an instance using the default image, flavor and security group.
- Check that public IP 8.8.8.8 can be pinged from instance.
- Delete instance.
Expected results
Ping should get a response, VMs are present in Contrail controller WebUI
Create a new network via Contrail WebUI
ID
create_new_network_via_contrail
Description
Create a new network via Contrail WebUI
Complexity
Advanced
Steps
- Login as admin to Contrail WebUI
- Create a new network
- Login as admin to Openstack Horizon UI
- Launch 2 new instance in the network with default security group
- Check ping connectivity between instances
- Verify on Contrail controller WebUI that network is there and VMs are attached to it
Expected results
The network is created, ping should get a response, VMs are present in Contrail controller WebUI
Create and terminate networks and verify in Contrail UI
ID
create_networks
Description
Create and terminate networks and verify in Contrail UI
Complexity
Advanced
Steps
- Add 2 private networks via Horizon
- Verify that networks are present in Contrail UI
- Remove one of the private network via Horizon.
- Verify that the network is absent in Contrail UI
- Add a private network via Horizon.
- Verify that all networks are present in Contrail UI.
Expected results
All steps must be completed successfully, without any errors.
Verify traffic flow in jumbo-frames-enabled network
ID
traffic_flow_in_jumbo-frames-enabled_network
Description
Verify traffic flow in jumbo-frames-enabled network
Complexity
Advanced
Steps
- Verify jumbo-frame and MTU configuration on all slaves
- Launch 2 new instances with default parameters
- Check ping connectivity between instances
- Connect to Compute Node via SSH and check the VM's connections with flow's command (flow -l)
- Verify on Contrail controller WebUI that network is there and VMs are attached to it
Expected results
All steps must be completed successfully, without any errors.
Check connectivity on different nodes and different private networks
ID
contrail_vm_connect_on_diff_nodes
Description
Check connectivity between instances placed in different private networks and hosted on different nodes
Complexity
Advanced
Steps
- Login as admin to Openstack Horizon UI
- Create 2 networks
- Launch 2 instances in different network. Make sure that VMs were scheduled to different compute nodes. Otherwise, migrate an instance to another compute
- Connect the networks (create a router via horizon)
- Check ping connectivity between instances
- Remove the router
- Connect to Compute node via SSH and check the VM's connections with flow's command (flow -l)
- Ping not get response
- Login to Contrail WebUI
- Connect the networks via Contrail Network Policies
- Check ping connectivity between instances
- Connect to Compute node via SSH and check the VM's connections with flow's command (flow -l)Ping should get a response
- Verify on Contrail controller WebUI that networks is there and VMs are attached to it
Expected results
Ping should get a response, VMs are present in Contrail controller WebUI
Check ability to a create contrail-specific attributes heat template
ID
create_stacks_from_heat_template
Description
Check ability to create stacks with contrail-specific attributes from heat template.
Complexity
Advanced
Steps
- Create stack with heat template.
- Check that stack was created.
Expected results
Stack should be created.
Check that ceilometer collects contrail metrics.
ID
contrail_ceilometer_metrics
Description
Check that ceilometer collects contrail metrics.
Complexity
Core
Steps
- Deploy Contrail cluster with ceilometer.
- Create 2 instances in the default network.
- Send icpm packets from one instance to another.
- Check contrail ceilometer metrics: "*ip.floating.receive.bytes", "*ip.floating.receive.packets", "*ip.floating.transmit.bytes", "*ip.floating.transmit.packets".
Expected results
All contrail ceilometer metrics should be collected by ceilometer.
Verify HTTPS on Contrail with selected TLS for OpenStack public endpoints
ID
https_tls_selected
Description
Verify HTTPS on Contrail with selected TLS for OpenStack public endpoints
Complexity
advanced
Steps
- Deploy Contrail cluster with selected TLS for OPenStack public endpoints
- Get fingerprints from Openstack Horizon UI certificate
- Get fingerprints from Contrail UI certificate
- Get fingerprints from Contrail API certificate
- Verify that keys are identical
Expected results
All steps must be completed successfully, without any errors.
Verify that login and password can be changed
ID
contrail_login_password
Description
Verify that login and password can be changed
Complexity
advanced
Steps
- Deploy Contrail cluster
- Login as admin to Openstack Horizon UI
- Create new user
- Login as user to Openstack Horizon UI
- Change login and password for user
- Login to Openstack Horizon UI with new credentials
- Login to Contrail Ui with same credentials
Expected results
All steps must be completed successfully, without any errors.
Verify that RBAC works and can be changed
ID
contrail_rbac
Description
Verify that RBAC works and can be changed
Complexity
advanced
Steps
- Deploy Contrail cluster with RBAC enabled
- Create via ContrailUI API access for new member without delete permission
- Login as admin to Openstack Horizon UI
- Create new user with this access
- Verify via cli, that the permissions are applied
- Change in FuelUI AAA Mode to Admin cloud and apply it
- Verify via cli, that the RBAC permissions are not applied for the user
Expected results
All steps must be completed successfully, without any errors.
Check conection between instances in different availibility zones
ID
contrail_vmware_cross_az
Description
Check connectivity between VMs in different availability zones.
Complexity
advanced
Steps
- Login to Openstack Horizon UI
- Create net_1: net01__subnet, 192.168.1.0/24, and attach it to the default router.
- Launch instances with image TestVM and flavor m1.micro in nova availability zone.
- Launch instances with image TestVM-VMDK and flavor m1.micro in vcenter availability zone.
- Check that instances are displayed in Contrail UI.
- Verify that instances on different hypervisors should communicate between each other. Send icmp ping from instances of vCenter to instances from Qemu/KVM and vice versa.
Expected results
VMs from different AZ should communicate via the same network. ICMP traffic is observed.
Security group rules with remote group id simple.
ID
contrail_vmware_sg
Description
Verify that network traffic is allowed/prohibited to instances according security groups rules.
Complexity
core
Steps
- Login to Openstack Horizon UI
- Create net_1: net01__subnet, 192.168.1.0/24, and attach it to the router01.
- Create security groups: SG1 SG2
- Delete all defaults egress rules of SG1 and SG2.
- Add icmp rule to SG1: Ingress rule with ip protocol 'icmp ', port range any, SG group 'SG1' Egress rule with ip protocol 'icmp ', port range any, SG group 'SG1'
- Add icmp rule to SG2: Ingress rule with ip protocol 'icmp ', port range any, SG group 'SG2' Egress rule with ip protocol 'icmp ', port range any, SG group 'SG2'
- Launch few instance of vcenter az with SG1 in net1(on each ESXI).
- Launch few instance of vcenter az with SG2 in net1(on each ESXI).
- Verify that icmp ping is enabled between VMs from SG1.
- Verify that icmp ping is enabled between instances from SG2.
- Verify that icmp ping is not enabled between instances from SG1 and VMs from SG2.
Expected results
Network traffic is allowed/prohibited to instances according security groups rules.
Check creation instance of vcenter az in the one batch.
ID
contrail_vmware_one_batch
Description
Create a batch of instances.
Complexity
core
Steps
- Login to Openstack Horizon UI
- Launch few instances simultaneously with image TestVM-VMDK and flavor m1.micro in vcenter availability zone in default internal network.
- Check connection between instances (ping, ssh).
- Delete all instances from horizon simultaneously.
Expected results
All instances should be created and deleted without any error.
Check connectivity via external Contrail network with floating IP
ID
contrail_vmware_ping_with/without_fip
Description
Check connectivity VMs with external network with floating IP via Contrail network
Complexity
Advanced
Steps
- Login to Openstack Horizon UI
- Launch a new instance in the default network.
- Send ping from instance to 8.8.8.8 or any other IP outside the cloud
- Assign a Floating IP to the instance
- Send ping from instance to 8.8.8.8 or any other IP outside the cloud
- Allow incoming ICMP from any address in default security group.
- Send ping from external (HOST) machine to Floating IP (emulate external network)
Expected results
Instance should get ping responce from 8.8.8.8 or any other IP outside the cloud. External (HOST) machine should get rping responce from instance.