From 271eb7ecd0699949a9e1c6771d1205869573f05a Mon Sep 17 00:00:00 2001 From: mrpa Date: Tue, 14 Apr 2020 14:15:40 +0200 Subject: Made minor updates to the AFTH programlistings etc. Added two limitations to the Known Limitations xml in Rel Notes. Change-Id: I52e59a39465c7f891b24008d0f0d700a62933829 Signed-off-by: mrpa --- .../doc/automation_framework_test_harness.xml | 230 ++++++++++----------- .../doc/components.xml | 2 +- .../doc/known_bugs_and_limitations.xml | 4 + 3 files changed, 115 insertions(+), 121 deletions(-) diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml index f32e5b7..888db4a 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml @@ -95,8 +95,7 @@ Options: Fortigate deployment scenario fortigateDeploy.json: - -[ + [ { "config": "config/waitDeviceUp.json", "module": "../device/waitDeviceUp.py" @@ -121,15 +120,13 @@ Options: "config": "config/controlVNFI.json", "module": "../vnf/controlVNFI.py" } -] - +] Below is a sample unit-test configuration file, describing the Fortigate cleanup scenario fortigateCleanup.json: - -[ + [ { "config": "config/destroyVNFI.json", "module": "../vnf/destroyVNFI.py" @@ -146,8 +143,7 @@ Options: "config": "config/offboardVNF.json", "module": "../vnf/offboardVNF.py" } -] - +] The config key contains the path to the test case's configuration file. @@ -162,9 +158,8 @@ Options: Unit-test behavior can be tweaked through setting any of the following options. This is done through the eneaUcpeMgr.py file: - - -# Defaults for the framework + + # Defaults for the framework username = "admin" password = "admin" host = None @@ -189,105 +184,105 @@ consoleLoggingLevel = logging.INFO - eneaUcpeMgr.py Options + eneaUcpeMgr.py Options - - + + - + - + - - - Option + + + Option - Description - - + Description + + - - - username + + + username - The user authentication used to log into the uCPE - Manager. This can be overwritten by setting the Python - unit-test suite command line option - -u. - + The user authentication used to log into the uCPE + Manager. This can be overwritten by setting the Python + unit-test suite command line option + -u. + - - password + + password - The password used to log into the uCPE Manager. This - can be overwritten by setting the Python unit-test suite - command line option -p. - + The password used to log into the uCPE Manager. This + can be overwritten by setting the Python unit-test suite + command line option -p. + - - host + + host - The IP address of the uCPE Manager host. This can be - overwritten by setting the Python unit-test suite command - line option -H. - + The IP address of the uCPE Manager host. This can be + overwritten by setting the Python unit-test suite command line + option -H. + - - devicename + + devicename - The name of the vCPE agent against which tests will - be performed. This can be overwritten by setting the Python - unit-test suite command line option - -n. - + The name of the vCPE agent against which tests will be + performed. This can be overwritten by setting the Python + unit-test suite command line option + -n. + - - ftpUsername + + ftpUsername - The user authentication used for the FTP connection - when onboarding a VNF image. This can be overwritten by - setting the Python script command line option - -f. - + The user authentication used for the FTP connection + when onboarding a VNF image. This can be overwritten by + setting the Python script command line option + -f. + - - ftpPassword + + ftpPassword - The password used for the FTP connection when - onboarding a VNF image. This can be overwritten by setting - the Python script command line option - -w. - + The password used for the FTP connection when + onboarding a VNF image. This can be overwritten by setting the + Python script command line option + -w. + - - ftpPort + + ftpPort - The port used for the FTP connection when onboarding - a VNF image. This can be overwritten by setting the Python - script command line option -P. - + The port used for the FTP connection when onboarding a + VNF image. This can be overwritten by setting the Python + script command line option -P. + - - failfast + + failfast - Describes the unit-test execution behavior on the - first error or failure encountered. - + Describes the unit-test execution behavior on the first + error or failure encountered. + - - fileLoggingLevel + + fileLoggingLevel - Sets the file logging level. - + Sets the file logging level. + - - consoleLoggingLevel + + consoleLoggingLevel - Sets the console logging level. - - - -
+ Sets the console logging level. + + + +
@@ -323,18 +318,14 @@ NOTSET 0 running the Fortigate deployment scenario: - -$ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s + $ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s fortigateDeploy.json -d "Fortigate deployment scenario" -Setting the console logging level to DEBUG: + Setting the console logging level to DEBUG: -consoleLoggingLevel = logging.DEBUG -Expected Output: - - -2019-03-07 18:03:20,791 - DEBUG: Started logging + consoleLoggingLevel = logging.DEBUG + Expected Output: 2019-03-07 18:03:20,791 - DEBUG: Started logging Running Fortigate deployment scenario... @@ -468,9 +459,8 @@ OK Below you'll find sample unit-test command line options for running the Fortigate cleanup scenario: - - -$ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s + + $ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s fortigateCleanup.json -d "Fortigate cleanup scenario" @@ -802,8 +792,7 @@ Mandatory options: The getEventsForUcpe Python module can be executed individually by running the following command: - -$ python getEventsForUcpe.py -H localhost -f \ + $ python getEventsForUcpe.py -H localhost -f \ ../../lab_config/intelc3850-2/intelc3850-2.json 2019-07-04 13:48:31,289 - DEBUG: Started logging @@ -818,8 +807,7 @@ Events on device: intelc3850-2 and severity: 1000 2019-07-04 09:57:40.042 2019-07-04 13:48:31,469 - DEBUG: Dumping 0 events 2019-07-04 13:48:31,469 - INFO: Done -2019-07-04 13:48:31,488 - DEBUG: Logging out and exiting... - +2019-07-04 13:48:31,488 - DEBUG: Logging out and exiting...
@@ -1826,8 +1814,8 @@ fortigateFWInstance
Uploading a NFV Access image onto the Enea uCPE Manager - Steps and options on how to Upload a NFV Access image onto the Enea uCPE - Manager are described below. + Steps and options on how to Upload a NFV Access image onto the + Enea uCPE Manager are described below.
Script Options @@ -1861,9 +1849,9 @@ Options:
Configuring the JSON File - The JSON configuration file needed to upload a NFV Access image should - contain a list of dictionaries. Each dictionary indicates the test - case name and the test case arguments passed to the + The JSON configuration file needed to upload a NFV Access image + should contain a list of dictionaries. Each dictionary indicates the + test case name and the test case arguments passed to the uploadImage Python module. Sample unit-test JSON file @@ -1897,10 +1885,11 @@ Options:
- Deleting a NFV Access image file from the Enea uCPE Manager + Deleting a NFV Access image file from the Enea uCPE + Manager - Steps and options on how to Delete a NFV Access image from the Enea uCPE - Manager are described below. + Steps and options on how to Delete a NFV Access image from the + Enea uCPE Manager are described below.
Script Options @@ -1931,9 +1920,9 @@ Options:
Configuring the JSON File - The JSON configuration file needed to delete a NFV Access image should - contain a list of dictionaries. Each dictionary indicates the test - case name and the test case arguments passed to the + The JSON configuration file needed to delete a NFV Access image + should contain a list of dictionaries. Each dictionary indicates the + test case name and the test case arguments passed to the deleteUpgradeFile Python module. Sample unit-test JSON file @@ -1970,11 +1959,12 @@ image was successfully removed
- Installing and activating a NFV Access image on an uCPE device from the - Enea uCPE Manager + Installing and activating a NFV Access image on an uCPE device + from the Enea uCPE Manager - Steps and options on how to Install and Activate a NFV Access image on an - uCPE device from the Enea uCPE Manager are described below. + Steps and options on how to Install and Activate a NFV Access + image on an uCPE device from the Enea uCPE Manager are described + below.
Script Options @@ -2010,10 +2000,10 @@ Options:
Configuring the JSON File - The JSON configuration file needed to install and activate a NFV Access - image on a uCPE device from the Enea uCPE Manager should contain a - list of dictionaries. Each dictionary indicates the test case name and - the test case arguments passed to the + The JSON configuration file needed to install and activate a NFV + Access image on a uCPE device from the Enea uCPE Manager should + contain a list of dictionaries. Each dictionary indicates the test + case name and the test case arguments passed to the installAndActivate Python module. Sample unit-test JSON file @@ -2193,4 +2183,4 @@ Options: ansible.log and debug.log files, respectively.
- + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml index 1de8454..2917b1a 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml @@ -49,7 +49,7 @@ Before running any use case with the Automation Framework or the Test Harness, make sure the uCPE device(s) have been added to - the uCPE Manager, as needed. + the uCPE Manager. Adding a VcpeAgent device can be done via two methods: diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml index 9c1828d..961a281 100644 --- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml +++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml @@ -43,6 +43,8 @@ fail and some resources will not be removed from the machine. Reverting resources in the case of a failed uninstall is not implemented. + + ELCCR-454Only the default database is supported, any requests for alternative databases are custom adaptations. ELCCR-371A software image for NFV Access runs @@ -64,6 +66,8 @@ one of the OVS bridges it is connected to, the VNF instance cannot be deleted before removing the appropriate flows. + + ELCCR-527When uploading a file, if the user cancels the upload, the upload window must be closed and reopened in order for the next upload to work. LXCR-9088Automation Framework and Test Harness -- cgit v1.2.3-54-g00ecf