From be5114a3fd53ec3485e40a2b980c328ccd1cbd80 Mon Sep 17 00:00:00 2001 From: mrpa Date: Tue, 3 Mar 2020 20:15:17 +0100 Subject: Updated the AFTH user guide and Sys Test Harness. Change-Id: I1d8243ff08771364b59947def940503217c94751 --- .../doc/automation_framework_test_harness.xml | 370 +++++++++++++++++++-- .../doc/components.xml | 4 +- .../doc/getting_started.xml | 20 +- .../doc/overview.xml | 4 +- .../doc/sample_test_cases.xml | 258 +++++++++++++- 5 files changed, 607 insertions(+), 49 deletions(-) (limited to 'doc') 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 e1bab54..9f9930a 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 @@ -814,7 +814,8 @@ Events on device: intelc3850-2 and severity: 1000
Enabling or Disabling the DPDK - Steps and details on how to enable or disable the DPDK are explained below. + Steps and details on how to enable or disable the DPDK are + explained below.
Script Options @@ -1105,31 +1106,43 @@ Options: 2020-01-07 05:58:03,688 - DEBUG: Session token is: 93dd3cd0-313c-11ea-b0c7-525400b7889f 2020-01-07 05:58:03,715 - DEBUG: Found device with name 'intelc3850-2' 2020-01-07 05:58:03,717 - DEBUG: ------------------ External Network Interfaces for intelc3850-2----------------- -2020-01-07 05:58:07,622 - DEBUG: eno4 DpdkTypes: [u'igb_uio', u'vfio-pci'] MacAddress: 0c:c4:7a:fb:85:dfsriov(7) +----------------External Network Interfaces for intelc3850-2---------------- +2020-01-07 05:58:07,622 - DEBUG: eno4 DpdkTypes: [u'igb_uio', u'vfio-pci'] \ +MacAddress: 0c:c4:7a:fb:85:dfsriov(7) 2020-01-07 05:58:07,624 - DEBUG: 2020-01-07 05:58:07,656 - DEBUG: ------------------ Configured External Network Interfaces for intelc3850-2----------------- -2020-01-07 05:58:07,657 - DEBUG: eno3 DpdkType: vfio-pci ID: 47556b22-b5c2-4acb-b3cb-09b1f024b3a7 -2020-01-07 05:58:07,658 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: 2c06b4f7-6814-4432-8765-a9d0cd5303c1 -2020-01-07 05:58:07,659 - DEBUG: enp1s0f0 DpdkTypes: [u'igb_uio', u'vfio-pci'] MacAddress: ac:1f:6b:2d:ee:58sriov(63) +----------------Configured External Network Interfaces for intelc3850-2---------------- +2020-01-07 05:58:07,657 - DEBUG: eno3 DpdkType: vfio-pci ID: \ +47556b22-b5c2-4acb-b3cb-09b1f024b3a7 +2020-01-07 05:58:07,658 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \ +2c06b4f7-6814-4432-8765-a9d0cd5303c1 +2020-01-07 05:58:07,659 - DEBUG: enp1s0f0 DpdkTypes: [u'igb_uio', u'vfio-pci'] \ +MacAddress: ac:1f:6b:2d:ee:58sriov(63) 2020-01-07 05:58:07,660 - DEBUG: 2020-01-07 05:58:07,690 - DEBUG: ------------------ Configured External Network Interfaces for intelc3850-2----------------- -2020-01-07 05:58:07,691 - DEBUG: eno3 DpdkType: vfio-pci ID: 47556b22-b5c2-4acb-b3cb-09b1f024b3a7 -2020-01-07 05:58:07,692 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: 2c06b4f7-6814-4432-8765-a9d0cd5303c1 -2020-01-07 05:58:07,693 - DEBUG: eno2 DpdkTypes: [u'igb_uio', u'vfio-pci'] MacAddress: 0c:c4:7a:fb:85:ddsriov(7) +----------------Configured External Network Interfaces for intelc3850-2---------------- +2020-01-07 05:58:07,691 - DEBUG: eno3 DpdkType: vfio-pci ID: \ +47556b22-b5c2-4acb-b3cb-09b1f024b3a7 +2020-01-07 05:58:07,692 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \ +2c06b4f7-6814-4432-8765-a9d0cd5303c1 +2020-01-07 05:58:07,693 - DEBUG: eno2 DpdkTypes: [u'igb_uio', u'vfio-pci'] \ +MacAddress: 0c:c4:7a:fb:85:ddsriov(7) 2020-01-07 05:58:07,695 - DEBUG: 2020-01-07 05:58:07,724 - DEBUG: ------------------ Configured External Network Interfaces for intelc3850-2----------------- -2020-01-07 05:58:07,725 - DEBUG: eno3 DpdkType: vfio-pci ID: 47556b22-b5c2-4acb-b3cb-09b1f024b3a7 -2020-01-07 05:58:07,726 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: 2c06b4f7-6814-4432-8765-a9d0cd5303c1 -2020-01-07 05:58:07,727 - DEBUG: eno1 DpdkTypes: [u'igb_uio', u'vfio-pci'] MacAddress: 0c:c4:7a:fb:85:dcsriov(7) +----------------Configured External Network Interfaces for intelc3850-2---------------- +2020-01-07 05:58:07,725 - DEBUG: eno3 DpdkType: vfio-pci ID: \ +47556b22-b5c2-4acb-b3cb-09b1f024b3a7 +2020-01-07 05:58:07,726 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \ +2c06b4f7-6814-4432-8765-a9d0cd5303c1 +2020-01-07 05:58:07,727 - DEBUG: eno1 DpdkTypes: [u'igb_uio', u'vfio-pci'] \ +MacAddress: 0c:c4:7a:fb:85:dcsriov(7) 2020-01-07 05:58:07,728 - DEBUG: 2020-01-07 05:58:07,760 - DEBUG: ------------------ Configured External Network Interfaces for intelc3850-2----------------- -2020-01-07 05:58:07,761 - DEBUG: eno3 DpdkType: vfio-pci ID: 47556b22-b5c2-4acb-b3cb-09b1f024b3a7 -2020-01-07 05:58:07,761 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: 2c06b4f7-6814-4432-8765-a9d0cd5303c1 +----------------Configured External Network Interfaces for intelc3850-2---------------- +2020-01-07 05:58:07,761 - DEBUG: eno3 DpdkType: vfio-pci ID: \ +47556b22-b5c2-4acb-b3cb-09b1f024b3a7 +2020-01-07 05:58:07,761 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \ +2c06b4f7-6814-4432-8765-a9d0cd5303c1 2020-01-07 05:58:07,762 - DEBUG: 2020-01-07 05:58:07,763 - INFO: Done 2020-01-07 05:58:07,787 - DEBUG: Logging out and exiting... @@ -1137,7 +1150,7 @@ Options:
- Create an OVS Network Bridge + Creating an OVS Network Bridge Instructions on how to Create an OVS Bridge on a device are detailed below. @@ -1226,7 +1239,7 @@ Options:
- Delete an OVS Network Bridge + Deleting an OVS Network Bridge How to Delete an OVS Bridge from a device is detailed in the following. @@ -1313,7 +1326,7 @@ Options:
- Onboard a VNF Image + Onboarding a VNF Image The specifics of how to Onboard a VNF image onto the Enea uCPE Manager is detailed below. @@ -1385,7 +1398,7 @@ Options:
- Onboard a VNF Image Raw + Onboarding a VNF Image Raw How to Onboard a VNF image in the uCPE Manager based upon its raw constituents, is detailed in depth below. @@ -1502,7 +1515,7 @@ Options:
- Offboard a VNF + Offboarding a VNF Steps on how to Offboard a VNF from the uCPE Manager are detailed below. @@ -1568,7 +1581,7 @@ Options:
- Instantiate a VNF + Instantiating a VNF Instantiating a VNF via the uCPE Manager is detailed below. @@ -1647,7 +1660,7 @@ License("vnf_config/fortigateImage/fortigateLicense.lic")
- Control a VNF Instance + Controlling a VNF Instance How to Control a VNF instance from the Enea uCPE Manager is detailed below. @@ -1731,7 +1744,7 @@ fortigateFWInstance -c stop
- Destroy a VNF Instance + Destroying a VNF Instance Steps and options on how to Destroy a VNF instance from the Enea uCPE Manager are described below. @@ -1797,6 +1810,311 @@ fortigateFWInstance 2019-03-07 17:33:51,712 - DEBUG: Logging out and exiting...
+ +
+ 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. + +
+ Script Options + + $ python uploadImage.py -h +Upload NFVA image on uCPE Manager +Usage: uploadImage.py [options] + +Upload NFVA image on uCPE Manager. + +Options: + --version show program's version number and exit + -h, --help show this help message and exit + -u USERNAME, --username=USERNAME + Enea uCPE Manager login username + -p PASSWORD, --password=PASSWORD + Enea uCPE Manager login password + -H HOST, --host=HOST Enea uCPE Manager host name or IP address + -f FILENAME, --fileName=FILENAME + Path to NFVA image file name + -m MODULE, --module=MODULE + Module name (default is: VcpeAgent) + -t UPGRADETYPE, --upgradeType=UPGRADETYPE + Upgrade Type depends on architecture: xeon_d or + atom_c3000 + + Mandatory options: + -H/--host, -f/--fileName, -m/--module, -t/--upgradeType +
+ +
+ 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 + uploadImage Python module. + + Sample unit-test JSON file + format:[ + { + "name": "Upload NFVA image on uCPE Manager", + "args": "-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d" + } +] +
+ +
+ Running the Python Module + + The uploadImage Python module can be + executed individually by running the following command line: + + $ python uploadImage.py -u admin -p admin -H localhost \ +-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d +2020-02-28 11:38:42,754 - DEBUG: Started logging +2020-02-28 11:38:42,755 - INFO: Upload NFVA image on uCPE Manager +2020-02-28 11:38:43,307 - DEBUG: Login successful on host 'localhost' +2020-02-28 11:38:43,308 - DEBUG: Session token is: 7da3f960-5a16-11ea-a3de-5652b3ac1c30 +2020-02-28 11:41:29,148 - INFO: Verify image validation flag +2020-02-28 11:41:29,149 - INFO: Valid flag: True +2020-02-28 11:41:29,344 - INFO: The image \ +'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully uploaded +2020-02-28 11:41:29,344 - INFO: Done +2020-02-28 11:41:29,388 - DEBUG: Logging out and exiting... +
+
+ +
+ 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. + +
+ Script Options + + $ python deleteUpgradeFile.py -h +Delete NFVA image from uCPE Manager +Usage: deleteUpgradeFile.py [options] + +Delete NFVA image from uCPE Manager. + +Options: + --version show program's version number and exit + -h, --help show this help message and exit + -u USERNAME, --username=USERNAME + Enea uCPE Manager login username + -p PASSWORD, --password=PASSWORD + Enea uCPE Manager login password + -H HOST, --host=HOST Enea uCPE Manager host name or IP address + -i IMAGENAME, --imageName=IMAGENAME + NFVA Image name + -m MODULE, --module=MODULE + Module name - default is VcpeAgent + + Mandatory options: + -H/--host, -i/--imageName, -m/--module. +
+ +
+ 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 + deleteUpgradeFile Python module. + + Sample unit-test JSON file + format:[ + { + "name": "Delete NFVA image on uCPE Manager", + "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2" + } +] +
+ +
+ Running the Python Module + + The deleteUpgradeFile Python module can be + executed individually by running the following command line: + + $ python deleteUpgradeFile.py -u admin -p admin -H localhost -i \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 +2020-02-28 12:06:20,111 - DEBUG: Started logging +2020-02-28 12:06:20,112 - INFO: Delete NFVA image from uCPE Manager +2020-02-28 12:06:20,210 - DEBUG: Login successful on host 'localhost' +2020-02-28 12:06:20,211 - DEBUG: Session token is: 594b2d50-5a1a-11ea-a3de-5652b3ac1c30 +2020-02-28 12:06:20,255 - INFO: The image \ +'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully found +2020-02-28 12:06:20,256 - INFO: The oid for \ +'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' image name is as follows: \ +VcpeAgent/xeon_d/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 +2020-02-28 12:06:20,449 - INFO: The 'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' \ +image was successfully removed +2020-02-28 12:06:20,479 - INFO: Done +2020-02-28 12:06:20,517 - DEBUG: Logging out and exiting... +
+
+ +
+ 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. + +
+ Script Options + + $ python installAndActivate.py -h +Install and activate NFVA image from uCPE Manager +Usage: installAndActivate.py [options] + +Install and activate NFVA image from uCPE Manager. + +Options: + --version show program's version number and exit + -h, --help show this help message and exit + -u USERNAME, --username=USERNAME + Enea uCPE Manager login username + -p PASSWORD, --password=PASSWORD + Enea uCPE Manager login password + -H HOST, --host=HOST Enea uCPE Manager host name or IP address + -i IMAGENAME, --imageName=IMAGENAME + Image name + -m MODULE, --module=MODULE + Module name -- VcpeAgent + -t UPGRADETYPE, --upgradeType=UPGRADETYPE + Upgrade Type -- xeon_d or atom_c3000 + -d DEVICENAME, --deviceName=DEVICENAME + Device Name + + Mandatory options: + -H/--host, -i/--imageName, -t/--upgradeType, -d/--deviceName, + -m/--module +
+ +
+ 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 + installAndActivate Python module. + + Sample unit-test JSON file + format:[ + { + "name": "Install and activate NFVA image on uCPE device from uCPE Manager", + "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16" + } +] +
+ +
+ Running the Python Module + + The installAndActivate Python module can be + executed individually by running the following command line: + + $ python installAndActivate.py -u admin -p admin -H localhost -i \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16 +2020-02-28 12:36:46,137 - DEBUG: Started logging +2020-02-28 12:36:46,138 - INFO: Install and activate NFVA image from uCPE Manager +2020-02-28 12:36:46,288 - DEBUG: Login successful on host 'localhost' +2020-02-28 12:36:46,288 - DEBUG: Session token is: 99b7cde0-5a1e-11ea-a3de-5652b3ac1c30 +2020-02-28 12:36:46,325 - DEBUG: Found device with name 'inteld1521-16' +2020-02-28 12:36:46,459 - INFO: Display info about NFVA installation \ +[inteld1521-16:1001:172.24.12.152] Install Started +2020-02-28 12:36:46,492 - INFO: Transferring Image: \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 +2020-02-28 12:36:56,552 - INFO: Verifying Release [1] +2020-02-28 12:37:06,599 - INFO: Verifying Release [2] +2020-02-28 12:37:16,652 - INFO: Validating Upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 +2020-02-28 12:37:26,713 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [3] +2020-02-28 12:37:36,770 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [5] +2020-02-28 12:37:46,819 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [7] +2020-02-28 12:37:56,879 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [9] +2020-02-28 12:38:06,920 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [11] +2020-02-28 12:38:16,975 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [13] +2020-02-28 12:38:27,019 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [15] +2020-02-28 12:38:37,091 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [18] +2020-02-28 12:38:47,133 - INFO: Validating upgrade to \ +enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [20] +2020-02-28 12:38:57,186 - INFO: Waiting for release to become active +2020-02-28 12:39:07,231 - INFO: Upgrade Request Complete +2020-02-28 12:39:17,242 - INFO: Installation completed! +2020-02-28 12:39:17,243 - INFO: Done +2020-02-28 12:39:17,294 - DEBUG: Logging out and exiting... +
+
+ +
+ Clearing information about completed upgrades of uCPE devices + from the Enea uCPE Manager + + Steps and options on how to clear information about completed + upgrades of uCPE devices from the Enea uCPE Manager are described + below. + +
+ Script Options + + $ python clearCompletedUpgradesInfo.py -h +Clear info about completed upgrades +Usage: clearCompletedUpgradesInfo.py [options] + +Clear info about completed upgrades + +Options: + --version show program's version number and exit + -h, --help show this help message and exit + -u USERNAME, --username=USERNAME + Enea uCPE Manager login username + -p PASSWORD, --password=PASSWORD + Enea uCPE Manager login password + -H HOST, --host=HOST Enea uCPE Manager host name or IP address + + Mandatory options: + -H/--host +
+ +
+ Configuring the JSON File + + No JSON configuration file is needed to clear information about + completed upgrades of uCPE devices from the Enea uCPE Manager. The + clearCompletedUpgradesInfo Python module can be + run without a JSON file as a parameter. +
+ +
+ Running the Python Module + + The clearCompletedUpgradesInfo Python + module can be executed individually by running the following command + line: + + $ python clearCompletedUpgradesInfo.py -u admin -p admin -H localhost +2020-02-28 12:51:55,861 - DEBUG: Started logging +2020-02-28 12:51:55,862 - INFO: Clear info about completed upgrades +2020-02-28 12:51:55,950 - DEBUG: Login successful on host 'localhost' +2020-02-28 12:51:55,951 - DEBUG: Session token is: b7eb83e0-5a20-11ea-a3de-5652b3ac1c30 +2020-02-28 12:51:55,993 - INFO: Done +2020-02-28 12:51:56,025 - DEBUG: Logging out and exiting... +
+
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 28abdd3..3eefcfd 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 @@ -11,8 +11,8 @@ - + diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml index 2f430c3..a63dfda 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml @@ -44,8 +44,8 @@ - + The following enviroment setup is needed for running all tests @@ -122,9 +122,8 @@ - + @@ -159,8 +158,9 @@ - Unzip the nfvaccess<version>_af-th.zip archive - file, provided by Enea, on a supported host machine. + Unzip the + nfvaccess<version>_af-th.zip archive file, + provided by Enea, on a supported host machine. The directory in which the archive has been unpacked will be denoted as <AF-TH-installdir>. @@ -210,8 +210,8 @@ After the initial setup, each session ends by closing the Python - virtual environment through running deactivate - from the <AF-THinstall-dir> directory. + virtual environment through running deactivate from the + <AF-THinstall-dir> directory. Subsequent use of the installation requires activating the Python virtual enviroment before using the Automation Framework and Test Harness: @@ -223,4 +223,4 @@ setupuCPEManager.yml playbook with the corresponding JSON config for the new uCPE Manager instance.
- + \ No newline at end of file diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml index 69d5f0e..557495a 100644 --- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml +++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml @@ -27,7 +27,7 @@ Definitions - + @@ -52,7 +52,7 @@ Acronyms - + diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml index e3414f4..fb8ff8d 100644 --- a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml +++ b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml @@ -13,7 +13,7 @@ TH.
- VNF - Onboard_VNF_Image<remark>all titles are formated with + <title>VNF - Onboard a VNF Image<remark>all titles are formated with underscores can this be changed or should it be left as is?</remark> @@ -60,7 +60,7 @@ vnfd=<VNF-Descriptor-name>"
- VNF - Offboard_VNF + VNF - Offboard a VNF Description: Removing a VNF Descriptor from the uCPE Manager. For details please refer to: @@ -92,7 +92,7 @@ vnfd=<VNF-Descriptor-name>"
- Device - Add_Device + Device - Add a device Description: Adding a uCPE device to the uCPE Manager. For details please refer to: @@ -124,8 +124,248 @@ vnfd=<VNF-Descriptor-name>" <Device-name> device already exists!
+
+ Device - Upload a NFV Access image + + Description: Upload a NFV Access image + file onto the uCPE Manager. For details please refer to: + + + + <AF-TH-install-dir>/playbooks/uploadImage.yml + + + + <AF-TH-install-dir>/automation_framework/device/uploadImage.py + + + + Precondition: The image path must + already exist. + + Example: ansible-playbook playbooks/uploadImage.yml -e \ +image_path="/tmp/enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \ +upgrade_type="xeon_d" + + Action: Run the + uploadImage.yml Ansible playbook with the + <Image-path> and + <Upgrade-type> as extra-vars: + + ansible-playbook playbooks/deleteUpgradeFile.yml -e \ +image_path="<Image-path>" -e upgrade_type="<Upgrade-type>" + + Result: Output of the test case + run using the Test Harness: + + TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework] +localhost : ok=1 changed=1 unreachable=0 failed=0Note: The test will fail if the image file has + already been uploaded. + + TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework] +ok=0 changed=0 unreachable=0 failed=1 + +# debug +A file with the same name is already uploaded. +
+ +
+ Device - Delete Upgraded File + + Description: Deleting an uploaded + NFV Access image file from the uCPE Manager. For details please refer to: + + + + <AF-TH-install-dir>/playbooks/deleteUpgradeFile.yml + + + + <AF-TH-install-dir>/automation_framework/device/deleteUpgradeFile.py + + + + Preconditions: The image file + must already be uploaded onto the uCPE Manager. + + Example: + + ansible-playbook playbooks/deleteUpgradeFile.yml -e \ +image_name="enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2" + + Action: Run the + deleteUpgradeFile.yml Ansible Playbook with the + <Image-name> as extra-vars:ansible-playbook playbooks/deleteUpgradeFile.yml -e \ +image_name="<Image-name>" + + Result: Output of the test case + run using the Test Harness:TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework] +localhost : ok=1 changed=1 unreachable=0 failed=0 + Note: The test will fail if the image + file does not exist: TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework] +ok=0 changed=0 unreachable=0 failed=1 + +# debug +No oid found for '<image_name>' image name +
+ +
+ Device - Clear information about upgrades of uCPE devices + + Description: Clear information + about upgrades of uCPE devices. For details please refer to: + + + + <AF-TH-install-dir>/playbooks/clearCompletedUpgradesInfo.yml + + + + <AF-TH-install-dir>/automation_framework/device/clearCompletedUpgradesInfo.py + + + + Preconditions: No preconditions + needed. + + Action: Run the + clearCompletedUpgradesInfo.yml Ansible + Playbook:ansible-playbook playbooks/clearCompletedUpgradesInfo.yml + + Result: Output of the test case + run using the Test Harness:TASK [Clear completed info about upgrading -- Run \ +clearCompletedUpgradesInfo.py module from automation framework]] +localhost : ok=1 changed=1 unreachable=0 failed=0 +
+ +
+ Device - Install and Activate a NFV Access image + + Description: Installing and + Activating a NFV Access image on a uCPE device from the uCPE Manager. For + details please refer to: + + + + <AF-TH-install-dir>/playbooks/installAndActivate.yml + + + + <AF-TH-install-dir>/automation_framework/device/installAndActivate.py + + + + Preconditions: + + The device must be previously added to the uCPE Manager + instance. + + + + The image file must already be uploaded onto the uCPE + Manager. + + + + Example: + + ansible-playbook playbooks/installAndActivate.yml -e \ +image_name="enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \ +upgrade_type=xeon_d -e device=inteld1521-16" + + Action: Run the + installAndActivate.yml Ansible Playbook with the + <Image-name>, + <Upgrade-type>, and the + <Device-name> as extra-vars:ansible-playbook playbooks/installAndActivate.yml -e \ +image_name="<Image_name>" -e upgrade_type="<Upgrade_type>" -e \ +device="<Device-name>" + + Result: Output of the test case + run using the Test Harness:TASK \ +[Install And Activate -- Run installAndActivate.py module from automation_framework] +localhost : ok=1 changed=1 unreachable=0 failed=0 + Note: The test will fail if the image + has already been installed on the uCPE device:TASK \ +[Install And Activate -- Run installAndActivate.py module from automation_framework] +ok=0 changed=0 unreachable=0 failed=1 + +# debug +Duplicate entry - Release already installed +
+ +
+ Device - Upload, Install and Activate a NFV Access image on a uCPE + device + + Description: Upload, install and + activate a NFV Access image on a uCPE device from the uCPE Manager. For details + please refer to: + + + + <AF-TH-install-dir>/playbooks/installNFVAImage.yml + + + + The playbook imports the previously described + playbooks: + + playbook/addDevice.yml + + + + playbook/uploadImage.yml + + + + playbook/installAndActivate.yml + + + + playbook/deleteUpgradeFile.yml + + + + playbook/clearCompletedUpgradesInfo.yml + + + + playbook/removeDevice.yml + + + + + + Precondition: A device JSON + configuration file must be created:<AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json + + Example: + + ansible-playbook playbooks/installNFVAImage.yml -e \ +device="inteld1521-16" -e \ +image_path=/tmp/enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \ +image_name=enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \ +upgrade_type=xeon_d + + Action: Run the + installNFVAImage.yml Ansible Playbook with the + <Image-path>, + <Image-name>, + <Upgrade-type>, and the + <Device-name> as extra-vars:ansible-playbook playbooks/installNFVAImage.yml -e \ +device="<Device-name>" -e image_path="<Image-path>" -e \ +image_name="<Image-name>" -e upgrade_type="<Upgrade-type>" + + Result: Output of the test case + run using the Test Harness:localhost : ok=1 changed=1 unreachable=0 failed=0 + Note: The test will fail if the one + imported playbook fails:ok=0 changed=0 unreachable=0 failed=1 +
+
- Device - Remove_Device + Device - Remove a Device Description: Removing a uCPE device from the uCPE Manager. For details please refer to: @@ -167,7 +407,7 @@ vnfd=<VNF-Descriptor-name>"
- Network - Bind_NIC + Network - Bind a NIC Description: Binding a physical network interface (NIC) to a device. For details please refer to: @@ -212,7 +452,7 @@ vnfd=<VNF-Descriptor-name>"
- Network - Unbind_NIC + Network - Unbind a NIC Description: Unbinding a physical network interface (NIC) from a device. For details please refer @@ -254,7 +494,7 @@ vnfd=<VNF-Descriptor-name>"
- Network - Create_Bridge + Network - Create a Bridge Description: Creating an OVS network bridge on a uCPE device. For details please refer to: @@ -297,7 +537,7 @@ vnfd=<VNF-Descriptor-name>"
- Network - Remove_Bridge + Network - Remove a Bridge Description: Removing an OVS network bridge from a uCPE device. For details please refer to: @@ -335,7 +575,7 @@ bridge=<Bridge-name>"
- Network - Configure_DPDK + Network - Configure a DPDK Description: Enabling or Disabling the DPDK support in OVS. For details please refer to: -- cgit v1.2.3-54-g00ecf