L4-L7 network services in shared network test execution

Name

Steps

Verification

Priority

Type

XEN

KVM

VMWare

1

Creation of shared n/w offering without L4-L7 services

1. create a shared n/w offering with following services** DNS
   • DHCP
   • userdata

(i.) Network offering should be created successfully.

P1

Sanity

2

DB verification for shared n/w offering without L4-L7 services

1. verify DB that the selected services are present

(i.) Check the following tables to ensure that the selected services are the ones enabled

• select * from network_offerings;
• select * from select * from network_offerings;
  

P1

Functional

3

createNetwork using shared n/w offering without L4-L7 services

1. As an admin, create a network using shared n/w offering without L4-L7 services.

(i.) Create n/w should take a custom CIDR and VLAN info from admin
(ii.) It should get created successfully.
DB Verification :
verify cloud.networks table especially for the fields state, account_id.

P1

Functional

4

Creation of shared n/w offering with L4-L7 services

1. create a shared n/w offering with following services** DNS => VR
   • DHCP => VR
   • userdata => VR
   • Firewall => Juniper SRX
   • SourceNAT=> Juniper SRX
   • StaticNAt=> Juniper SRX
   • PortForwarding=>JuniperSRX
   • LB => NetScaler

(i.) Network offering should be created successfully.

P1

Sanity

5

DB verification for shared n/w offering with L4-L7 services

• verify DB that the selected services are present

(i.) Check the following tables to ensure that the selected services are the ones enabled

• select * from network_offerings;
• select * from select * from network_offerings;

P1

Functional

6

connect at least one NIC to a shared n/w without L4-L7 services

1. As a non-ROOT admin, deploy a VM using a shared n/w that has no L4-L7 services

(i.) VM deployment should happen without any issues
(ii.) connectivity should be fine
DB Verification :
Verify that cloud.networks table especially for the fields like state, account_id

P1

Functional

7

connect more than one NIC to shared n/w without L4-L7 services from multiple accounts

1. Have at least two accounts and deploy a VM using a shared n/w that has no L4-L7 services

(i.) VM deployment should happen without any issues
(ii.) connectivity should be fine
DB Verification :
(i.) Verify that cloud.networks table especially for the fields like state, account_id
(ii.) Verify that cloud.nics table is updated with all required values.

P1

Functional

8

Verify GC for shared n/w without L4-L7 services

1. Have at least two accounts and an undeployed VM using a shared n/w that has no L4-L7 services

(i.) wait till the GC period based on the settings
                network.gc.interval
                network.gc.wait
(ii.) verify that GC doesn’t effec the VR (shared networks should not be GC'ed)
DB Verification :
(i.) Verify that cloud.networks table especially for the fields like state, account_id
(ii.) Verify that cloud.nics table is updated with all required values.
(iii.) verify cloud.op_networks and check nics_count

P1

Functional

9

createNetwork using shared n/w offering with L4-L7 services

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
2. As an admin, create a network using the above shared n/w offering.

(i.) Create n/w should take a custom CIDR and VLAN info from admin

DB Verification :
(i.) select * from select * from network_offerings;
(ii.) verify cloud.networks table especially for the fields state, account_id

P1

Functional

10

connect more than one NIC to shared n/w with L4-L7 services from multiple accounts

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
2.  Have at least two accounts and deploy a VM using a shared n/w that has no L4-L7 services

(i.) VM deployment should happen without any issues
(ii.) connectivity should be fine
DB Verification :
(i.) Verify that cloud.networks table especially for the fields like state, account_id
(ii.) Verify that cloud.nics table is updated with all required values.

P1

Functional

11

Acquire IP for a shared Network that has L4-L7 services enabled using UI

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Deploy a VM using this n/w.
3. acquire an additional IP using UI

(i.) IP should be associated with account and network successfully.

DB Verification :
(i.) verify user_ip_addresses table and make sure that fields like network_id, account are set to right values.

P1

Functional

12

Acquire IP for a shared Network that has L4-L7 services enabled using API

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Deploy a VM using this n/w.
3. acquire an additional IP using API

(i.) IP should be associated with account and network successfully.

DB Verification :
(i.) verify user_ip_addresses table and make sure that fields like network_id, account are set to right values.

P1

Functional

13

Release IP for a shared Network that has L4-L7 services enabled using UI

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Deploy a VM using this n/w.
3. acquire an additional IP using UI
4. release IP using UI

(i.) IP should be released and given back to pool successfully.

DB Verification :
(i.) verify user_ip_addresses table and make sure that fields like network_id, account are set to right values.

P1

Functional

14

Release IP for a shared Network that has L4-L7 services enabled using API

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Deploy a VM using this n/w.
3. acquire an additional IP using UI
4. release IP using API

(i.) IP should be released and given back to pool successfully.

DB Verification :
(i.) verify user_ip_addresses table and make sure that fields like network_id, account are set to right values.

P1

Functional

15

listPublicIpAddresses with listAll=true

1. Have at least 2 accounts (ACC1) with shared n/w with L4-L7 services enabled and available to user.
2. deploy VMs in each account connected to the above shared n/w.
3. listPublicIPAddresses with listAll=true using both ACC1/ ACC2

(i.) When listAll API parameter is set to true, API will return list of the public IP's associated with the network which caller is authorized to see.

P1

Functional

16

listPublicIpAddresses with listAll=false

1. Have at least 2 accounts (ACC1) with shared n/w with L4-L7 services enabled and available to user.
2. deploy VMs in each account connected to the above shared n/w.
3. listPublicIPAddresses with listAll=true using both ACC1/ ACC2

(i.) When listAll API parameter is set to false then API shall return the list of public IP's owned by the caller and associated with the network.

P1

Functional

17

listPublicIPAddress on a n/w that is not used by the account.

1. Have at least 2 accounts (ACC1) with 2  shared n/ws where L4-L7 services enabled and available to user.
2. deploy VMs in each account connected to the above shared n/w (N1).
3. listPublicIPAddresses with listAll=true/false using both ACC1/ ACC2

P2

Negative

18

listPublicIPAddress on a n/w that is not owned by the account.

1. Have 2 different domains (d1 & d2)
2. create accounts in each domain (d1 -> ACC1 , d2 -> ACC2)
3. create a shared n/w that is scoped to a domain d1
4. deploy VMs in account ACC1 connected to the above shared n/w.
5. listPublicIPAddresses with listAll=true/false using both ACC1/ ACC2

listPublicIpaddress should not list anything for a n/w that is not owned / scoped to d2->ACC2

P2

Negative

19

Release IP for a shared Network that has L4-L7 services enabled and there are existing rules

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Deploy a VM using this n/w.
3. acquire an additional IP using UI and create some rules like PF, LB etc..,
4. release IP using API

(i.) IP should be released and given back to pool successfully.

DB Verification :
(i.) verify user_ip_addresses table and make sure that fields like network_id, account are set to right values.

P1

Functional

20

verify the functionality of services for a shared n/w with L4-L7 services from multiple accounts

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
2.  Have at least two accounts and deploy a VM using a shared n/w that has no L4-L7 services.
3.  Try the following operations
createPortForwardingRule
deletePortForwardingRule
listPortForwardingRules
createFirewallRule
deleteFirewallRule
listFirewallRules
enableStaticNat
disableStaticNat
createIpForwardingRule
deleteIpForwardingRule

(i.) All the rules should work fine without any issues.

P1

Functional

21

createNetwork using shared n/w offering with L4-L7 services where scope=ALL

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
2. As an admin, create a network using the above shared n/w offering where scope=ALL
3. Have at least 2 domains with at least 1 account in each domain
4. deploy a VM using the above accounts that has a NIC connected to shared n/w

(i.) verify that every account is able to deploy VMs using the shared n/w and the connectivity is fine.

DB Verification :
(i.) select * from select * from network_offerings;
(ii.) verify cloud.networks table especially for the fields state, account_id

P1

Functional

22

createNetwork using shared n/w offering with L4-L7 services where scope=domain

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
2. As an admin, create a network using the above shared n/w offering where scope=ALL
3. Have at least 2 domains with at least 1 account in each domain
4. deploy a VM using the above accounts that has a NIC connected to shared n/w

(i.) verify that the only account from a domain which is defined in the scope is able to deploy VMs using the shared n/w and the connectivity is fine.

(ii.) Other accounts from other domains must not be able to use this shared n/w if the scope of shared n/w is not set to thier domain.

DB Verification :
(i.) select * from select * from network_offerings;
(ii.) verify cloud.networks table especially for the fields state, account_id

P1

Functional

23

createNetwork using shared n/w offering with L4-L7 services where scope=project

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
2. As an admin, create a network using the above shared n/w offering where scope=ALL
3. Have at least 2 projects with at least 2 account in each project
4. deploy a VM using the above accounts that has a NIC connected to shared n/w

(i.) verify that the only accounts that are part of project s able to deploy VMs using the shared n/w and the connectivity is fine.

(ii.) Other accounts from other projects must not be able to use this shared n/w if the scope of shared n/w is not set to thier project

DB Verification :
(i.) select * from select * from network_offerings;
(ii.) verify cloud.networks table especially for the fields state, account_id

P1

Functional

24

createNetwork using shared n/w offering that has some of L4-L7 services enabled

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
2. As an admin, create a network using the above shared n/w offering.
3. create a Network using the above offering
4. deploy a VM using this network.

(i.) VM should be deployed without any issues and connectivity must be there as expected.

P1

Functional

25

createNetwork using shared n/w offering that has L4-L7 services enabled along with VPN

1. As an admin, ensure that there is a shared network using shared n/w offering with following L4-L7 services.
        DNS => VR
        DHCP => VR
        userdata => VR
        Firewall => Juniper SRX
        SourceNAT=> Juniper SRX
        StaticNAt=> Juniper SRX
        PortForwarding=>JuniperSRX
        LB => NetScaler
       VPN

This should fail as we don’t support it

P2

Negative

26

Verify GC for shared n/w with L4-L7 services

1. Have at least two accounts and an undeployed VM using a shared n/w that has L4-L7 services

(i.) wait till the GC period based on the settings
                network.gc.interval
                network.gc.wait
(ii.) verify that GC doesn’t effec the VR (shared networks should not be GC'ed)
DB Verification :
(i.) Verify that cloud.networks table especially for the fields like state, account_id
(ii.) Verify that cloud.nics table is updated with all required values.
(iii.) verify cloud.op_networks and check nics_count

P1

Functional

27

restart a shared n/w with L4-L7 service using cleanup=false

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Have multiple accounts in different domains and deploy a VMs using this n/w.
3. Have different rules created by different accounts in this n/w
4. invoke restartNetwork with cleanup set to false

(i) It should implement n/w elements again and re-apply all the rules

DB Verification :

(i.) verify firewall_rules, pf rules tables
(ii.) verify user_ip_addresses
(iii.) check cloud.networks tables especially for the fields like state,account_id.

P1

Functional

28

restart a shared n/w with L4-L7 service using cleanup=true

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Have multiple accounts in different domains and deploy a VMs using this n/w.
3. Have different rules created by different accounts in this n/w
4. invoke restartNetwork with cleanup set to true

Following actions should happen

* delete current network rules
* shutdown network elements
* implement network elements
* re-apply the rules


DB Verification :

(i.) verify firewall_rules, pf rules tables
(ii.) verify user_ip_addresses
(iii.) check cloud.networks tables especially for the fields like state,account_id.

P1

Functional

29

External device allocation for shared n/ws with L4-L7 services enabled

1. check external device allocation for shared n/ws with L4-L7 services enabled for the following cases
* when shared n/w scope is set to "ALL"
* when shared n/w scope is set to "Domain"
* when shared n/w scope is set to "Project"
* when shared n/w scope is set to "Account"

P1

Functional

30

destroy a shared n/w that is created using an offering with L4-L7 services enabled while in use

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Have multiple accounts in different domains and deploy a VMs using this n/w.
3. Have different rules created by different accounts in this n/w
4. Destroy/Delete Network

It should not happen since there are VMs/Nics connected to it

P2

Negarive

31

destroy a shared n/w that is created using an offering with L4-L7 services enabled which doesn’t have active NICs

1. Make sure that there is a shared n/w with L4-L7 services enabled and available to user
2. Have multiple accounts in different domains and deploy a VMs using this n/w.
3. Have different rules created by different accounts in this n/w
4. power-OFF/ delete VMs
5. destroy n/w

Network should be deleted successfully.

DB Verification :

(i.) verify firewall_rules, pf rules tables
(ii.) verify user_ip_addresses
(iii.) check cloud.networks tables especially for the fields like state,account_id.

P2

Negative

32

Have VMs with multiple shared n/ws where L4-L7 features enabled

1. Make sure that there are at least 2 shared n/ws with L4-L7 services enabled and available to users
2. Have multiple accounts in different domains and deploy a VMs using above n/ws.
3. Have different rules created by different accounts in this n/w

Everything should go fine without any issues.

P1

Functional

33

Have VMs with multiple shared n/ws where L4-L7 features enabled as well as isolated without sourceNAT

1. Make sure that there are at least 2 shared n/ws with L4-L7 services enabled as well as isolate without sourceNAT available users.
2. Have multiple accounts in different domains and deploy a VMs using above n/ws.
3. Have different rules created by different accounts in this n/w

Everything should go fine without any issues.

P1

Functional

34

Have VMs with multiple shared n/ws where L4-L7 features enabled as well as isolated with all services enabled

1. Make sure that there are at least 2 shared n/ws with L4-L7 services enabled as well as isolate with all sevices enabled
2. Have multiple accounts in different domains and deploy a VMs using above n/ws.
3. Have different rules created by different accounts in this n/w

Everything should go fine without any issues.

P1

Functional

35

Verify the default gateway functionality with VMs connected to multiple n/ws (both shared and isolated)

1. Make sure that there are at least 2 shared n/ws with L4-L7 services enabled as well as isolate with all sevices enabled
2. Have multiple accounts in different domains and deploy a VMs using above n/ws.
3. Deploy VMs with default GW set to isolated/shared etc..,

Default GW must be set to the user defined one and functionality

P1

Functional

36

Create different rules on an IP that is owned by one account to a VM in different account

1. Have at least 1 shared n/w with L4-L7 services enabled
2. Have at least 2 different accounts (ACC1, ACC2) where at least one VM deployed by each account using above shared n/w.
3. Acquire an IP in ACC1 and create a PF/LB/StaticNAT rule that points to VMs owned by ACC2

All the rule creation should fail with graceful error messages

P1

Functional

37

Create different rules on an IP that is mapped to one shared n/w to a VM connected to different shared n/w

1. Have at least 2 shared n/w's  (N1 & N2) with L4-L7 services enabled
2. Have at least 1 account and deploy at least 2 VMs (VM1, VM2)
3. VM1 connected to N1 & VM2 connected to N2
4. Acquire an IP in ACC1 for N1 and create a PF/LB/StaticNAT rule that points to VMs connected to N1

All the rule creation should fail with graceful error messages

P1

Functional

38

Create different rules on an IP that is mapped to one shared n/w to a VM connected to isolated network

1. Have at least 1 shared n/w & 1 isolated n/w  (N1 & N2) with L4-L7 services enabled
2. Have at least 1 account and deploy at least 2 VMs (VM1, VM2)
3. VM1 connected to N1 & VM2 connected to N2
4. Acquire an IP in ACC1 for N1 and create a PF/LB/StaticNAT rule that points to VMs connected to N1

All the rule creation should fail with graceful error messages

P1

Functional