47dd349f61
Initial integration of sriov-fec-operator application. - This change includes python k8s-app plugins for fluxcd integration. - Added docker images build script for operator. - Updated License headers. Test Status: - PASS: Build application rpm, generate tarball and build docker images, copy to stx active controller. - PASS: Verify that app is uploaded, applied and operator pods are created. - PASS: Configure ACC100 using config file to create 16 VFs. - PASS: Bringup test-pod, request FEC VFs and validate sample dpdk application test-bbdev. - PASS: App upload, apply, remove, delete verified in simplex mode. - PASS: Switch between classic method and operator method validated. - PASS: Reboot test with operator method validated. - PASS: Shellcheck tool test. - TBD: N3000 testing. Failure Tests: - PASS: Applying Clusterconfig shall fail when fec operator is not deployed. - PASS: Operator deployment shall fail when docker image download fails during system application-apply. - PASS: Applying Clusterconfig shall fail with Wrong values in clusterconfig yaml file: - set vfAmount to >16 or 0. - set wrong pci address. - set wrong hostname. - PASS: Removing the operator without deleting the clusterconfig fails to delete the FEC VFs and subsequent re-apply will also fail. - PASS: Modifying or Deleting sriovfecClusterconfig when test-pod is running with FEC VFs mapped, test-pod gets automatically deleted since FEC requested resources become unavailable. Story: 2009749 Task: 44657 Change-Id: I1eee9e48a10e86be32e59bb83852c7bc179f0b44 Signed-off-by: Nidhi Shivashankara Belur <nidhi.shivashankara.belur@intel.com>
18 lines
563 B
ReStructuredText
18 lines
563 B
ReStructuredText
StarlingX App-sriov-fec-operator Style Commandments
|
|
=========================================================
|
|
|
|
- Step 1: Read the OpenStack style commandments
|
|
https://docs.openstack.org/hacking/latest/
|
|
- Step 2: Read on
|
|
|
|
App-sriov-fec-operator Specific Commandments
|
|
---------------------------------------------------------
|
|
|
|
None so far
|
|
|
|
Running tests
|
|
-------------
|
|
The approach to running tests is to simply run the command ``tox``. This will
|
|
create virtual environments, populate them with dependencies and run all of
|
|
the tests that OpenStack CI systems run.
|