- Modify the checksum in the VNF descriptor (using the UI VNF catalog) to add a wrong but format-valid checksum (e.g.: “aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa”). Same images are used.
- Deploy the same NS as in test1
- Check that the system refuses to deploy the NS due to a checksum error (“VIM Exception vimconnException Image not found at VIM with filter…”)
- Modify the checksum in the VNF descriptor (using the UI VNF catalog) to add a wrong but format-valid checksum (e.g.: "00000000000000000000000000000000"). Same images are used.
- Deploy the same NS as in "Test 1"
- Check that the system refuses to deploy the NS due to a checksum error ("VIM Exception vimconnException Image not found at VIM with filter")
- Modify the checksum in the VNF descriptor (using the UI VNF catalog) to add the valid checksum for the image (“ee1eca47dc88f4879d8a229cc70a07c6” for the cirros034 image).
- Deploy the same NS as in test1
- Modify the checksum in the VNF descriptor (using the UI VNF catalog) to add the valid checksum for the image ("ee1eca47dc88f4879d8a229cc70a07c6" for the cirros034 image).
- Deploy the same NS as in "Test 1"
- Check that the NS is successfully instantiated.
- Access the console via OSM UI (user: “`cirros`”, pwd: “`cubswin:)`”)
- Access the console via OSM UI (user: "`cirros`", pwd: "`cubswin:)`")
- Check that the VMs are up and running and connected via the common link.
## Test 3b. Instantiation time of large NS based on Cirros images using IP profiles
@@ -103,29 +103,28 @@ Objective:
- Check that instantiation time is bounded to avoid spurious timeouts.
- Measure delay in the deployment, and evaluate potential issues in the connector.
- Check that IP profiles work properly in a large NS
Steps:
- Onboard a “large NS” consisting of:
- Onboard a "large NS" consisting of:
- 2 types of VNFs based on Cirros VM. VNF#1 should have 5 interfaces (+management), while VNF#2 would only require 1 interface (+management)
- Star topology, with 1 VNF in the middle and 5 instances of the other VNF connected to that one (+ the corresponding management interfaces)
- Networks will have an IP profile so that DHCP is enabled
- Launch NS instantiation, specifying the right mgmt network to be used
- Check that the UI reports a successful deployment
- Connect to each VNF via SSH (user: “`cirros`”, pwd: “`cubswin:)`”) and configure the interfaces to use DHCP, e.g. by changing /etc/network/interfaces and running “ifup ethX”
- Connect to each VNF via SSH (user: "`cirros`", pwd: "`cubswin:)`") and configure the interfaces to use DHCP, e.g. by changing /etc/network/interfaces and running "ifup ethX"
- Check that connectivity is appropriate via ping from the different VMs
- Onboard a the variant of the NS of Test #4a (test4b_ns), where the NS includes a user “osm” and SSH public key to be injected to every VNF.
- Onboard a the variant of the NS of Test #4a (test4b_ns), where the NS includes a user "osm" and SSH public key to be injected to every VNF.
- Launch NS instantiation via UI, specifying the right mgmt network to be used.
- Check that the UI reports a successful deployment.
- Check that the VMs are accessible from the management network via the new user “osm” using its private SSH key (the private key is stored in the folder "test4b_ns/keys" inside the NS package).
- Check that the VMs are accessible from the management network via the new user "osm" using its private SSH key (the private key is stored in the folder "test4b_ns/keys" inside the NS package).
- Onboard a variant of the NS of Test #4 (test5_ns), but with a VNF whose single interface has port security disabled.
- Launch NS instantiation via UI, specifying the right mgmt network to be used
- Check that the UI reports a successful deployment.
- Connect to each VNF via SSH (user: “`osm`”, pwd: “`osm4u`”).
- Connect to each VNF via SSH (user: "`osm`", pwd: "`osm4u`").
- Configure both VNFs with an additional IP address of the same subnet, e.g.: 192.168.50.X/24
- Do not remove the mgmt IP address.
- Add an additional IP address to the single interfaces using the command "ip addr add 192.168.50.X/24 dev eth0" and ping from one VNF to the other one.
## Test 6a. Assignment of public IP addresses to management interfaces of single-interface VNFs
@@ -258,24 +256,24 @@ Objective:
Prerequisites:
- Configure the VIM to allow the dynamic assignment of public addresses from a pool
- Configure a VIM network (e.g. “public”) to use the appropriate pool, to allow external access via “public” IP addresses.
- Configure a VIM network (e.g. "public") to use the appropriate pool, to allow external access via "public" IP addresses.
- Configure the datacenter in the RO to assign public IP addresses to VNF management interfaces (use_floating_ip: true)
Steps:
- Onboard and deploy a NS consisting of 2 Ubuntu VNFs interconnected by a single network (mgmt).
- Instantiate the NS via UI, specifying that the NS network “mgmt” must be mapped to the VIM network name “public”, so that a “public” IP address will be assigned from the pool.
- Instantiate the NS via UI, specifying that the NS network "mgmt" must be mapped to the VIM network name "public", so that a "public" IP address will be assigned from the pool.
- Check that the UI reports a successful deployment.
- Connect to each VNF via SSH (user: “`osm`”, pwd: “`osm4u`”) using the public IP address.
- Connect to each VNF via SSH (user: "`osm`", pwd: "`osm4u`") using the public IP address.
## Test 6b. Assignment of public IP addresses to management interfaces of multi-interface VNFs
@@ -286,24 +284,24 @@ Objective:
Prerequisites:
- Configure the VIM to allow the dynamic assignment of public addresses from a pool
- Configure a VIM network (e.g. “public”) to use the appropriate pool, to allow external access via “public” IP addresses.
- Configure a VIM network (e.g. "public") to use the appropriate pool, to allow external access via "public" IP addresses.
- Configure the datacenter in the RO to assign public IP addresses to VNF management interfaces (use_floating_ip: true)
Steps:
- Onboard and deploy a NS consisting of 2 Ubuntu VNFs interconnected by two networks (management and data).
- Instantiate the NS via UI, specifying that the NS network “mgmt” must be mapped to the VIM network name “public”, so that a “public” IP address will be assigned from the pool.
- Instantiate the NS via UI, specifying that the NS network "mgmt" must be mapped to the VIM network name "public", so that a "public" IP address will be assigned from the pool.
- Check that the UI reports a successful deployment.
- Connect to each VNF via SSH (user: “`osm`”, pwd: “`osm4u`”) using the public IP address.
- Connect to each VNF via SSH (user: "`osm`", pwd: "`osm4u`") using the public IP address.
## Test 6c. Assignment of public IP addresses to management interfaces of multi-interface VNFs even when IP profiles are used
@@ -314,25 +312,25 @@ Objective:
Prerequisites:
- Configure the VIM to allow the dynamic assignment of public addresses from a pool
- Configure a VIM network (e.g. “public”) to use the appropriate pool, to allow external access via “public” IP addresses.
- Configure a VIM network (e.g. "public") to use the appropriate pool, to allow external access via "public" IP addresses.
- Configure the datacenter in the RO to assign public IP addresses to VNF management interfaces (use_floating_ip: true)
Steps:
- Onboard and deploy the NS used in Test 3c, consisting of a star topology, with 1 VNF in the middle and 5 instances of the other VNF connected to that one (+ the corresponding management interfaces), where all the inter-VNF networks have an IP profile so that DHCP is enabled, but with no default gateway.
- Instantiate the NS via UI, specifying that the NS network “mgmt” must be mapped to the VIM network name “public”, so that a “public” IP address will be assigned from the pool. This is the only change with respect to Test 3c.
- Instantiate the NS via UI, specifying that the NS network "mgmt" must be mapped to the VIM network name "public", so that a "public" IP address will be assigned from the pool. This is the only change with respect to Test 3c.
- Check that the UI reports a successful deployment.
- Connect to each VNF via SSH (user: “`osm`”, pwd: “`osm4u`”) using the public IP address.
- Connect to each VNF via SSH (user: "`osm`", pwd: "`osm4u`") using the public IP address.
Felipe Vicens <felipe.vicens@atos.net>