You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Test Case ID

Test Case Name

Steps to be performed to test

Verification steps

Priority

Status

Comments

1

Deploy vm with newly created secuirty group

1) Try to bring a fresh setup of CS
2) Add Zone -> Basic mode
3) Create a Security Group
4) Try to deploy a VM. Select the newly created security group during deployment selections on "Add Instance" Wizard

Should be able to deply VM with newly created security group.Verify vm_instance table output in cloud db:
mysql> select * from vm_instance;
sql quiery output should show the vm in running state.

P1

PASS

 

2

Basic zone without SecurityGroups

1. Install a basic zone with a CSP enabled host
2. Verify SSVM and console proxy are created
3. Disable secuirty Groups
4. Verify ping to default gateway from SSVM/guestVM

1.Verify ebtables rules on the host. Make sure that dropping all traffic on FORWARD chain by default should not be present when Security Groups is disabled :   ebtables -l | grep FORWARD  Bridge chain: FORWARD, entries: 2, policy: ACCEPT
-j DEFAULT_EBTABLES
2.Verify traffic flow from any VM , network connectivity should be there

P1

 

 

3

Add a security group.

 

Addition of SG should succeed. Output should be in the following format:
GROUP <group-name> <description>

P1

PASS

 

4

Delete  an existing security group.

 

Deletion of SG should succeed. Output should be in the following format:
GROUP <group-name>

P1

 

 

5

Delete  an existing security group when there are security-ingress rules associated with this Security Group.

 

Deletion of SG should succeed.
This should result in all the SG ingress rules associated with this SG also get deleted.

P1

 

 

6

Add a TCP ingress rule for a SG to an existing Security Group.

 

All the Vms in this group should be accessible using TCP protocol on the port range from all the Vms in the Security group.

P1

PASS

 

7

Add a TCP ingress rule  SG to an existing Security Group - Check for the API response.

 

 

P1

 

 

8

Add a UDP ingress rule for a SG  to an existing Security Group.

 

All the Vms in this group should be accessible using UDP protocol on the port range from all the Vms in the Security group.

P1

 

 

9

Add a ICMP ingress rule  for a SG to an existing Security Group.

 

All the Vms in this group should be able to ping all the Vms in the Security group.

P1

 

 

10

Add TCP ingress rule for multiple SG to an existing Security Group.

 

 

P1

 

 

11

Revoke an ingress rule for a CIDR  from an existing Security Group.

 

 

P2

 

 

12

Revoke an ingress rule for a CIDR  from an existing Security Group - Check for the API response.

 

 

P2

 

 

13

Revoke an ingress rule for a SG  from an existing Security Group.

 

 

P2

 

 

14

Add a TCP ingress rule for a SG to an existing Security Group.

 

All the Vms in this group should be accessible using TCP protocol on the port range from all the Vms in the Security group.

P2

 

 

15

Add a UDP ingress rule for a SG  to an existing Security Group.

 

 

P2

 

 

16

Add a ICMP ingress rule  for a SG to an existing Security Group.

 

 

P2

 

 

17

Add TCP ingress rule for multiple SG to an existing Security Group.

 

 

P2

 

 

  • No labels