OSM E2E tests - Revision history

Ramonsalguer at 17:24, 17 February 2021

2021-02-17T17:24:16Z

← Older revision		Revision as of 17:24, 17 February 2021
Line 1:		Line 1:
			'''THIS PAGE IS DEPRECATED'''. OSM Tester Guide has been moved to a new location: '''https://osm.etsi.org/gitlab/osm-doc/osm-tester-guide'''

			---

	__TOC__		__TOC__

2017-09-08T12:36:03Z

Test 3b. Instantiation time of large NS based on Cirros images using IP profiles

2017-09-08T12:35:55Z

Test 3a. Instantiation time of large NS based on Cirros images

2017-09-08T12:35:48Z

Test 2b. Successful deployment of scenario when the descriptor has a checksum

2017-09-08T12:35:39Z

Test 2a. Failed deployment of scenario when the checksum is invalid

2017-09-08T12:35:28Z

Test 1. Sanity check with simple NS

2017-09-08T12:32:11Z

← Older revision		Revision as of 12:32, 8 September 2017
Line 1:		Line 1:
	__TOC__		__TOC__

	~~'''Note:~~ VNF and NS packages, as well as VM images required for the tests can be found here: [http://osm-download.etsi.org/ftp/e2e-tests/ http://osm-download.etsi.org/ftp/e2e-tests/]'''		= OSM packages and images for E2E tests =

			All VNF and NS packages as well as VM images required for the tests can be found here: '''[http://osm-download.etsi.org/ftp/e2e-tests/ http://osm-download.etsi.org/ftp/e2e-tests/]'''

	= Test 1. Sanity check with simple NS =		= Test 1. Sanity check with simple NS =

2017-09-05T15:23:34Z

Test 5. Port security disabled

← Older revision		Revision as of 15:23, 5 September 2017
Line 227:		Line 227:
	** Do not remove the mgmt IP address.		** 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.		** 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.
	** If port security and security groups have been properly disabled, the ping should work.		* If port security and security groups have been properly disabled, the ping between both VNFs using the added IP addresses should work.

	Images:		Images:

2017-09-05T15:23:04Z

Test 5. Port security disabled

← Older revision		Revision as of 15:23, 5 September 2017
Line 224:		Line 224:
	* Check that the UI reports a successful deployment.		* Check that the UI reports a successful deployment.
	* Connect to each VNF via SSH (user: “<tt>osm</tt>”, pwd: “<tt>osm4u</tt>”).		* Connect to each VNF via SSH (user: “<tt>osm</tt>”, pwd: “<tt>osm4u</tt>”).
	* ~~Check that port security is disabled between~~ both VNFs, ~~using netcat~~:		* Configure both VNFs with an additional IP address of the same subnet, e.g.: 192.168.50.X/24
	** ~~In one side (server): nc -l 3333~~		** Do not remove the mgmt IP address.
	** ~~<nowiki>In~~ the other ~~side (client): nc <IP_SERVER> 3333</nowiki>~~		** 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.
	** ~~Then~~, ~~write something in~~ the ~~client and you~~ should ~~see it in the server~~		** If port security and security groups have been properly disabled, the ping should work.

	Images:		Images:

2017-09-05T15:17:54Z

Test 4c. Day 0 configuration: custom user script with cloud-init

← Older revision		Revision as of 15:17, 5 September 2017
Line 202:		Line 202:
	* Launch NS instantiation via UI, specifying the right mgmt network to be used		* Launch NS instantiation via UI, specifying the right mgmt network to be used
	* Check that the UI reports a successful deployment.		* Check that the UI reports a successful deployment.
	* Access the VM via SSH and check that the file has been successfully created.		* Access the VM via SSH and check that the file has been successfully created. The private key is "test4.pem", stored in the folder "ubuntu_1iface_cloudinit_newfile_vnf/keys" inside the VNF package.

	Images:		Images: