diff options
| author |   Michal Jagiello <michal.jagiello@t-mobile.pl> | 2022-04-14 11:48:05 +0000 |
|---|---|---|
| committer |   Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | 2022-05-31 10:39:47 +0000 |
| commit | e36348ba8b69938b53bb054e5d6e41cd1f801d9f (patch) | |
| tree | 6c97735cdd5bf3d291c3110e41a43c8435753abb | |
| parent | 7ef41a7e6ef53ad377ff470c554722ce093541ba (diff) | |
[DOC] Jakarta release doc
Integration doc for Jakarta release
Issue-ID: INT-2102
Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>
Change-Id: I0e8f29d9ff27702d663e721f2492f6fa8a23778d
33 files changed, 288 insertions, 410 deletions
diff --git a/docs/docs_5G_Configuration_over_NETCONF.rst b/docs/docs_5G_Configuration_over_NETCONF.rst index 4b737d04f..d8701a655 100644 --- a/docs/docs_5G_Configuration_over_NETCONF.rst +++ b/docs/docs_5G_Configuration_over_NETCONF.rst @@ -24,7 +24,7 @@ This use case is intended to be applicable for 5G base stations and other nodes How to Use ~~~~~~~~~~ -Set up certificate in SDNC using <https://docs.onap.org/en/dublin/submodules/sdnc/oam.git/docs/cert_installation.html?highlight=SDNC> +Set up certificate in SDNC using <https://docs.onap.org/projects/onap-sdnc-oam/en/latest/cert_installation.html> As this usecase is extention of PnP PNF flow so run PnP usecase following running this usecase follow link <https://wiki.onap.org/display/DW/5G+-+PNF+Plug+and+Play> diff --git a/docs/docs_5G_oof_son.rst b/docs/docs_5G_oof_son.rst index 034d4c2d9..0af1218c9 100644 --- a/docs/docs_5G_oof_son.rst +++ b/docs/docs_5G_oof_son.rst @@ -65,26 +65,25 @@ As part of Istanbul release work, progress was made towards the goal of transiti Jakarta Release ~~~~~~~~~~~~~~~~~ -In the Jakarta release, the SON Use Case work was impacted by the fact RAN-Sim needed the following enhancements: - -- Update of the yang model to the O1 yang models (similar to the models used by the Slicing Use Case) -- Implementation of an A1 termination with an abstracted xApp and Near-RT RIC which would accept an A1 message and update the CU/DU configuration -- Planning for a replacement of the Honeycomb netconf engine (project is archived) - The following are the enhancements in the Jakarta release: - Update of SDN-R netconf code to use the new O1 yang models - Update of RAN-Sim to use the new O1 yang models -We have also made progress in the following areas in planning for the Kohn release. +In the Jakarta release, the SON Use Case work was impacted by the fact RAN-Sim needed enhancements to implement new features. We have made progress in the following areas in planning for future releases. - Convergence on the VES message formats to be used for FM/PM/CM - Inclusion of A1 based actions for the end-to-end SON Use Case -- Enhancement of RAN-Sim to include abstraction of xApp and Near-RT RIC which would process an A1 message and update of a CU/DU +- Enhancement of RAN-Sim to include abstraction of RAN App and A1 Termination which would process an A1 message and update of a CU/DU +- Planning for replacement of Honeycomb netconf engine (project is archived) + +For more information, please see: -Please see also `OOF (SON) wiki page <https://wiki.onap.org/display/DW/5G+-+OOF+%28ONAP+Optimization+Framework%29+and+PCI+%28Physical+Cell+ID%29+Optimization>`_. -Additional information are available related to previous releases can be found -in `El Alto & Frankfurt OOF (SON) wiki page <https://wiki.onap.org/display/DW/OOF+%28SON%29+in+R5+El+Alto%2C+OOF+%28SON%29+in+R6+Frankfurt>`_. +- `OOF-SON Jakarta wiki page <https://wiki.onap.org/display/DW/R10+5G+SON+use+case>`_. + +- `OOF-SON Base wiki page <https://wiki.onap.org/display/DW/5G+-+OOF+%28ONAP+Optimization+Framework%29+and+PCI+%28Physical+Cell+ID%29+Optimization>`_. + +- `OOD-SON El Alto & Frankfurt OOF (SON) wiki page <https://wiki.onap.org/display/DW/OOF+%28SON%29+in+R5+El+Alto%2C+OOF+%28SON%29+in+R6+Frankfurt>`_. How to Use @@ -99,14 +98,14 @@ This page includes instructions for access to the lab. Setup and testing is done For all instructions about installing the components, please see: - `Wiki Installation page <https://wiki.onap.org/display/DW/Demo+setup+steps+for+Frankfurt>`_ -- `Son-Handler installation <https://docs.onap.org/projects/onap-dcaegen2/en/frankfurt/sections/services/son-handler/installation.html?highlight=dcaegen2>`_ + Test Status and Plans ~~~~~~~~~~~~~~~~~~~~~ OOF was enhanced with handling cells with fixed PCI values during the optimization, SON-Handler MS was functionally enhanced for adaptive SON functionality, SDN-C (R) was enhanced to include handling of DMaaP message for config changes in the RAN, and Policy was also enhanced with Control Loop Co-ordination function. -See `test plans <https://wiki.onap.org/display/DW/Testing>`_ for details. +See `test plans <https://wiki.onap.org/display/DW/Integration+Tests>`_ for details. Known Issues and Resolutions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/docs_E2E_network_slicing.rst b/docs/docs_E2E_network_slicing.rst index 4058d9c4a..2de9719c8 100644 --- a/docs/docs_E2E_network_slicing.rst +++ b/docs/docs_E2E_network_slicing.rst @@ -95,10 +95,11 @@ Network Slice Instance (NSI) Life Cycle View -------------------------------------------- 3GPP Specification (3GPP TS 28.530) describes management aspects of a Network Slice Instance, which can be described by the four phases: -Preparation: The preparation phase includes network slice design, network slice capacity planning, on-boarding and evaluation of the network functions, preparing the network environment and other necessary preparations required to be done before the creation of an NSI -Commisioning: NSI provisioning in the commissioning phase includes creation of the NSI. During NSI creation all needed resources are allocated and configured to satisfy the network slice requirements. The creation of an NSI can include creation and/or modification of the NSI constituents -Operation:The Operation phase includes the activation, supervision, performance reporting (e.g. for KPI monitoring), resource capacity planning, modification,and de-activation of an NSI. -Decommissioning: Network slice instance provisioning in the decommissioning phase includes decommissioning of non-shared constituents if required and removing the NSI specific configuration from the shared constituents. After the decommissioning phase, the NSI is terminated and does not exist anymore. +- Preparation: The preparation phase includes network slice design, network slice capacity planning, on-boarding and evaluation of the network functions, preparing the network environment and other necessary preparations required to be done before the creation of an NSI. +- Commissioning: NSI provisioning in the commissioning phase includes creation of the NSI. During NSI creation all needed resources are allocated and configured to satisfy the network slice requirements. The creation of an NSI can include creation and/or modification of the NSI constituents. +- Operation: The Operation phase includes the activation, supervision, performance reporting (e.g. for KPI monitoring), resource capacity planning, modification and de-activation of an NSI. +- Decommissioning: Network slice instance provisioning in the decommissioning phase includes decommissioning of non-shared constituents if required and removing the NSI specific configuration from the shared constituents. After the decommissioning phase, the NSI is terminated and does not exist anymore. + The ONAP-based NSI lifecycle management will finally provide the demonstration of all these phases. Abbreviations @@ -161,7 +162,7 @@ Recap of Guilin functionality ----------------------------- From the architecture point of view, in Guilin release, besides the continuation of NSMF which was implemented in Frankfurt release, the RAN NSSMF, TN NSSMF, CORE NSSMF have been implemented within ONAP, apart from interacting with -ezternal RAN NSSMF and external CORE NSSMF. +external RAN NSSMF and external CORE NSSMF. The following provides an overview of the enhancements done in Guilin release: @@ -173,7 +174,7 @@ The following provides an overview of the enhancements done in Guilin release: deactivation, deletion and modification (in case of reuse of NSSI). - **Enable NSMF interaction with RAN NSSMF, TN NSSMF, CN NSSMF**: Implement generic NSSMF adaptor for three domain NSSMFs, - alignment with standard intefaces (3GPP, IETF), enable the connection to external RAN NSSMF. + alignment with standard interfaces (3GPP, IETF), enable the connection to external RAN NSSMF. - **Design of RAN NSST, TN NSST, CN NSST and Slice Profiles, TN information models**: Basic E2E Slicing model was provided all the related templates designed from SDC, TN related information models. @@ -255,7 +256,7 @@ The code-impacted modules of E2E Network Slicing in Honolulu release are: (b) ‘Vpn-binding’is used to store ACTN OTN Tunnel model’s parameters. - **OOF**: Updates include: - + (a) NST selection is enhanced by fetching the templates from SDC directly. (b) coverageArea to coverageAreaTAList mapping is done by OOF (as part of Slice Profile generation) by accessing CPS. @@ -358,9 +359,9 @@ Below aspects are covered in Istanbul release: 3. **NSMF based TN Slices** - Support for interacting with TN NSSMF directly from NSMF for front haul and mid haul slice subnets. There will be separate SDC template for this scenario. NST will have 5 NSSTs - CN NSST, AN NSST, TN FH NSST, TN MH NSST, TN BH NSST. -4. **KPI Monitoring** - Implementation is done in KPI Computation MS to configure the required KPIs and the KPI computaion formula based on policies. +4. **KPI Monitoring** - Implementation is done in KPI Computation MS to configure the required KPIs and the KPI computation formula based on policies. -5. **Closed Loop** - Closed Loop updates are sent over A1 interface to NearRT-RIC. This is done at the POC level. This will be further enhanced in Jakarta release to make use of the A1-Policy Management Service in CCSDK. +5. **Closed Loop** - Closed Loop updates are sent over A1 interface to Near-RT RIC. This is done at the POC level. This will be further enhanced in Jakarta release to make use of the A1-Policy Management Service in CCSDK. 6. **Intelligent Slicing** - End to end intelligent slicing - closed loop flow is tested with the initial version of Machine Learning MS. @@ -374,7 +375,7 @@ Below aspects are covered in Istanbul release: (a) Service instantiation for non-shared and shared scenario and fixes to support option 1 are done (b) NSI selection process support for shared NSI is tested - + Impacted Modules for Istanbul Release ------------------------------------- - **SO** @@ -385,9 +386,9 @@ Impacted Modules for Istanbul Release - **NSMF**: Fixes in NSI termination issues to support OOF interaction for NSI termination query and added subnet Type support for respective TN Domain - **AN NSSMF**: Fixes for different termination scenarios in Option 1 - **CN NSSMF**: Bug fixes in shared allocate flow, modify flow and terminate flow - - Slice Profile alignement with NSSMF + - Slice Profile alignment with NSSMF (d) NSMF based TN Slices (TN-FH, TN-MH are created by NSMF) - Work flow changes to support this approach - + - **OOF** (a) Integration with CPS for coverage area to coverage area TA list (b) Bug fixes in NxI termination @@ -403,9 +404,9 @@ Impacted Modules for Istanbul Release - **CPS-TBDMT** (a) This component is enhanced to support different type of queries based on templates - + - **CPS** - (a) Bug fixes and support for GET, POST, PATCH and DELETE type of queries. + (a) Bug fixes and support for GET, POST, PATCH and DELETE type of queries. Istanbul Release - Functional Test cases ---------------------------------------- @@ -419,7 +420,7 @@ Istanbul Release - Functional Test cases (b) NSMF driven TN-FH and TN-MH slices creation is tested (c) CPS impacts in closed loop scenario is validated and few test cases are deferred to Jakarta release - Integration test plan is available at `Integration Testing in Instanbul Release <https://wiki.onap.org/display/DW/R9+Integration+Test+for+E2E+Network+Slicing>`_ + Integration test plan is available at `Integration Testing in Istanbul Release <https://wiki.onap.org/display/DW/R9+Integration+Test+for+E2E+Network+Slicing>`_ Istanbul Release - Operation Guidance ------------------------------------- @@ -434,13 +435,13 @@ The ONAP TSC approved on July 9th, 2020 to change the status of ESR GUI Module to an 'unmaintained' project. Further information about 'Unmaintained Projects' can be found in the `ONAP Developer Wiki. <https://wiki.onap.org/x/Pw_LBQ>`__ -But excluding the ESR GUI module from ONAP does not mean that the “external -system registration” mechanism is excluded; i.e. only the GUI is not available +But excluding the ESR GUI module from ONAP does not mean that the "external +system registration" mechanism is excluded; i.e. only the GUI is not available anymore. Nevertheless, in order to register the 3rd party controllers (like it is done -in E2E network slicing use case and recently in Cloud Leased Line “CLL” use -case as part of Intent-Based Networking), AAI’s API are invoked manually. +in E2E network slicing use case and recently in Cloud Leased Line "CLL" use +case as part of Intent-Based Networking), AAI's API are invoked manually. To do so, please send the following CURL command (PUT) to your AAI, with the attached xml payload. In the payload, please adjust the controller name (in @@ -489,5 +490,69 @@ PAYLOAD (esr-registration-controller-1.xml): </esr-thirdparty-sdnc> -Additional issues occured during the deployment and integration testing will be -listed in the ONAP Developer Wiki at `Network Slicing - Issues and Solutions <https://wiki.onap.org/display/DW/Network+Slicing+-+Issues+and+Solutions>`_
\ No newline at end of file +Additional issues occurred during the deployment and integration testing will be +listed in the ONAP Developer Wiki at `Network Slicing - Issues and Solutions <https://wiki.onap.org/display/DW/Network+Slicing+-+Issues+and+Solutions>`_ + +Jakarta Release Updates +----------------------- +In Jakarta release, the following aspects are covered: + +1. **E2E Network Slicing Solution** + - Slice selection based on resource occupancy level. With this enhancement, NSMF/NSSMF is able to monitor and update resource levels at NSI/NSSI level. OOF returns the solution for NSI/NSSI selection based on the criteria. In case of shared scenario, NSI/NSSI can be shareable only if sufficient resources are available in the network. RAN NSSMF’s resource occupancy is considered for this release. Resource occupancy of Core and TN NSSMFs will be considered in future releases. + - Activate, Deactivate scenarios support in external RAN NSSMF - Option2. Note that instantiation and termination are supported in Istanbul release. + +2. **RAN Slicing** + - Optimization of cm-handle registration with CPS-DMI Plugin for RAN NF instances to upload yang model. + - CPS integration with SDN-R for RAN slice allocation and reconfiguration scenarios + - CPS integration stabilization for RAN slice activate/deactivate and terminate scenarios. Validation and bug fix for CPS integration of RAN slice lifecycle. + - CSIT for RAN slicing +3. **Transport Slicing** + - OOF involvement in TN slice reuse and terminate scenarios + - Implementation of the call to OOF for allocateNSSI to enable TN NSSI reuse in TN NSSMF + - Implementation of the call to OOF for terminateNxi API to deallocate TN NSSI (which may not be terminated even when NSI is terminated) in TN NSSMF + - Closed-loop enhancement in CCVPN to support Transport Slicing’s closed-loop (Covered in CCVPN use case). +4. **Closed Loop** + - IBN based Closed loop for Network Slicing. This enhancement makes use of intents and Machine Learning models for closed loop. ML prediction microservice enhancement is done as a POC work in Jakarta release. + - CPS integration stabilization, which validates and enhances CPS integration for closed loop. +5. **Carryover tests from Istanbul release** + - Option-1 (internal NSMF, NSMF and NSSMF) + - E2E testing for activate/deactivate scenario + - Pending test cases for E2E Slice termination + - NSMF driven TN slicing + - Pending testing for activate/deactivate and terminate scenarios + - Bug fixes and testing for Core slicing + - NF instantiation issue with same NSST + - Multiple non-share Core slice creation issue + +Impacted Modules for Jakarta Release +------------------------------------ +- **SO**: Requirements below are identified for Jakarta release and have impacts in SO component: + (1) Use of Optimization solution (OOF) in allocateNSSI, deallocateNSSI in TN NSSMF + (2) Activate, Deactivate flows support in external RAN NSSMF for option 2 + (3) Bug fixes/enhancements of carryover test cases from Istanbul release + +- **OOF**: OOF component has an impact for the requirement below: + (1) NSI/NSSI Selection enhancements based on resource occupancy levels + +- **DCAE**: The requirements below are identified for Jakarta release and have impacts in DCAE component: + (1) Slice selection taking into consideration of resource occupancy levels + (2) CPS integration in closed loop – This was done in I-release. Expecting minor enhancements in Slice Analysis MS once after the other components impacts w.r.t CPS integration and E2E testing are completed. + (3) IBN based Closed loop for Network Slicing - This will have impact in E2E Slicing closed loop and TN Slicing closed loop. + +- **CCSDK**: The requirements below are identified for network slicing use case in Jakarta release and have impacts in CCSDK component. Most of these requirements fall under the category of CPS integration. + (1) Optimizing cm-handle registration with CPS-DMI Plugin to upload yang model + (2) CPS Integration with SDN-R for RAN Slice allocate and reconfigure scenarios + (3) CPS Integration Stabilization - RAN Slice activate/deactivate and terminate scenarios + (4) CSIT for RAN slicing + +Jakarta Release - Functional Test cases +--------------------------------------- +The functional testing of this use case covers CSMF/NSMF, RAN/CN/TN NSSMFs and Closed Loop functionality. Test cases are classified into 5 tracks: E2E network slicing, RAN NSSMF, TN NSSMF, Closed Loop and carryover testing. Details of the test cases can be found at: `E2E Network Slicing Tests for Jakarta Release <https://wiki.onap.org/display/DW/E2E+Network+Slicing+Integration+Tests+for+Jakarta+Release>`_ and its child wiki pages. + +Jakarta Release - Operation Guidance +------------------------------------ +The setup and operation details for E2E network slicing use case are available at `User Operation Guidance - Jakarta Release <https://wiki.onap.org/display/DW/User+Operation+Guidance+-+Jakarta+Release>`_. + +Jakarta Release - Known issues and Solutions +-------------------------------------------- +Details of up to date manual configurations, known issues, solutions and work-arounds can be found in the following wiki page: `Jakarta Release - Issues and Solutions <https://wiki.onap.org/display/DW/Jakarta+Release+-+Issues+and+Solutions>`_. diff --git a/docs/docs_scaleout.rst b/docs/docs_scaleout.rst index 42b0eb59b..7c1c4f3f9 100644 --- a/docs/docs_scaleout.rst +++ b/docs/docs_scaleout.rst @@ -79,9 +79,8 @@ A section like that is required in that override file openStackKeystoneVersion: "KEYSTONE_V3" The values that must be changed according to your lab are all "openStack******" parameters + dcaeCollectorIp + nfsIpAddress -To know how to encrypt the openstack passwords, please look at these guides: -https://docs.onap.org/en/dublin/submodules/oom.git/docs/oom_quickstart_guide.html -https://docs.onap.org/en/elalto/submodules/oom.git/docs/oom_quickstart_guide.html +To know how to encrypt the openstack passwords, please look at the guide here: +https://docs.onap.org/projects/onap-oom/en/latest/oom_quickstart_guide.html Initialize the Customer and Owning entities =========================================== diff --git a/docs/docs_usecases_release.rst b/docs/docs_usecases_release.rst index 25d0dcef6..7cecf8c21 100644 --- a/docs/docs_usecases_release.rst +++ b/docs/docs_usecases_release.rst @@ -5,14 +5,14 @@ :orphan: -Istanbul Use Cases and Requirements -=================================== +Jakarta Use Cases and Requirements +================================== Description ----------- This session includes use cases and functional requirements which have been -officially verified in Istanbul release by the ONAP community. +officially verified in Jakarta release by the ONAP community. For each use case or functional requirement, you can find contact names and a link to the associated documentation. diff --git a/docs/docs_vFW_CNF_CDS.rst b/docs/docs_vFW_CNF_CDS.rst index e6d4249a4..4ac979e35 100644 --- a/docs/docs_vFW_CNF_CDS.rst +++ b/docs/docs_vFW_CNF_CDS.rst @@ -73,9 +73,9 @@ Since Honolulu release vFW CNF use case supports three different scenarios where - Scenario 1: simple deployment of vFW CNF instance - Scenario 2: deployment of vFW CNF instance with enrichment of the Helm deployment with profiling mechanism -- Scenario 3: deployment of vFW CNF instance with Day2 configuration applied and CNF status checked as a part of a config-deploy operation +- Scenario 3: deployment of vFW CNF instance with Day2 configuration applied and CNF status checked as a part of a config-deploy operation -The 3rd scenario presents the most comprehensive way of managing the CNF in ONAP, including Day 0/1/2 operations. It shows also how to combine in the Day2 operation information for the AAI and SDNC MDSAL. All scenarios can be supported by execution of the dedicated Healthcheck workflow `3-5 Verification of the CNF Status`_. +The 3rd scenario presents the most comprehensive way of managing the CNF in ONAP, including Day 0/1/2 operations. It shows also how to combine in the Day2 operation information for the AAI and SDNC MDSAL. All scenarios can be supported by execution of the dedicated Healthcheck workflow `3-5 Verification of the CNF Status`_. Modeling of Onboarding Package/Helm ................................... @@ -1618,7 +1618,7 @@ where <COMPONENT_NAME> and <CONTAINER> should be replaced with following keyword - cds-blueprints-processor, cds-blueprints-processor - multicloud-k8s, multicloud-k8s -- network-name-gen, network-name-gen, +- network-name-gen, network-name-gen, **Debug log** @@ -1733,7 +1733,7 @@ Examplary output of Status API is shown below (full result of test vFW CNF helm **<AUTOMATED>** -Since Honolulu release vFW CNF Use Case is equipped with dedicated mechanisms for verification of the CNF status automatically, during the instantiation. The process utilizes the k8sPlugin Status and Healthcheck APIs that both are natively exposed in the CDS and can be executed from the script execution functionality in the CDS. +Since Honolulu release vFW CNF Use Case is equipped with dedicated mechanisms for verification of the CNF status automatically, during the instantiation. The process utilizes the k8sPlugin Status and Healthcheck APIs that both are natively exposed in the CDS and can be executed from the script execution functionality in the CDS. .. figure:: files/vFW_CNF_CDS/healthcheck.png :scale: 60 % @@ -1862,11 +1862,11 @@ Future development areas for CNF support: - Upgrade of the vFW CNF similar to Helm Upgrade through the SDC and SO - Use multicloud/k8S API v2 (EMCO) -Some of the features from the list above are covered by the Jakarta roadmap described in `REQ-890`_. +Some of the features from the list above are covered by the Jakarta roadmap described in `REQ-890`_. -.. _ONAP Deployment Guide: https://docs.onap.org/projects/onap-oom/en/guilin/oom_quickstart_guide.html -.. _CDS Documentation: https://docs.onap.org/projects/onap-ccsdk-cds/en/guilin/index.html +.. _ONAP Deployment Guide: https://docs.onap.org/projects/onap-oom/en/latest/oom_quickstart_guide.html +.. _CDS Documentation: https://docs.onap.org/projects/onap-ccsdk-cds/en/latest/ .. _vLB use-case: https://wiki.onap.org/pages/viewpage.action?pageId=71838898 .. _vFW_CNF_CDS Model: https://git.onap.org/demo/tree/heat/vFW_CNF_CDS/templates?h=guilin .. _vFW_CNF_CDS Automation: https://git.onap.org/demo/tree/heat/vFW_CNF_CDS/automation?h=guilin @@ -1874,7 +1874,7 @@ Some of the features from the list above are covered by the Jakarta roadmap desc .. _vFW CBA Model: https://git.onap.org/ccsdk/cds/tree/components/model-catalog/blueprint-model/service-blueprint/vFW?h=elalto .. _vFW_Helm Model: https://git.onap.org/multicloud/k8s/tree/kud/demo/firewall?h=elalto .. _vFW_NextGen: https://git.onap.org/demo/tree/heat/vFW_NextGen?h=elalto -.. _vFW EDGEX K8S: https://docs.onap.org/en/elalto/submodules/integration.git/docs/docs_vfw_edgex_k8s.html +.. _vFW EDGEX K8S: https://docs.onap.org/projects/onap-integration/en/latest/docs_vfw_edgex_k8s.html .. _vFW EDGEX K8S In ONAP Wiki: https://wiki.onap.org/display/DW/Deploying+vFw+and+EdgeXFoundry+Services+on+Kubernets+Cluster+with+ONAP .. _KUD github: https://github.com/onap/multicloud-k8s/tree/honolulu/kud/hosting_providers/baremetal .. _KUD in Wiki: https://wiki.onap.org/display/DW/Kubernetes+Baremetal+deployment+setup+instructions @@ -1890,10 +1890,10 @@ Some of the features from the list above are covered by the Jakarta roadmap desc .. _REQ-458: https://jira.onap.org/browse/REQ-458 .. _REQ-627: https://jira.onap.org/browse/REQ-627 .. _REQ-890: https://jira.onap.org/browse/REQ-890 -.. _Python SDK: https://docs.onap.org/projects/onap-integration/en/guilin/integration-tooling.html?highlight=python-sdk#python-onapsdk +.. _Python SDK: https://docs.onap.org/projects/onap-integration/en/latest/integration-tooling.html#python-onapsdk .. _KUD Jenkins ci/cd verification: https://jenkins.onap.org/job/multicloud-k8s-master-kud-deployment-verify-shell/ -.. _K8s cloud site config: https://docs.onap.org/en/guilin/guides/onap-operator/cloud_site/k8s/index.html -.. _SO Monitoring: https://docs.onap.org/projects/onap-so/en/guilin/developer_info/Working_with_so_monitoring.html +.. _K8s cloud site config: https://docs.onap.org/en/latest/guides/onap-operator/cloud_site/k8s/index.html +.. _SO Monitoring: https://docs.onap.org/projects/onap-so/en/latest/developer_info/Working_with_so_monitoring.html .. _Data Dictionary: https://git.onap.org/demo/tree/heat/vFW_CNF_CDS/templates/cba-dd.json?h=guilin .. _Helm Healer: https://git.onap.org/oom/offline-installer/tree/tools/helm-healer.sh?h=frankfurt .. _infra_workload: https://docs.onap.org/projects/onap-multicloud-framework/en/latest/specs/multicloud_infra_workload.html?highlight=multicloud diff --git a/docs/docs_vfwHPA.rst b/docs/docs_vfwHPA.rst index c37754d55..737b4fd5d 100644 --- a/docs/docs_vfwHPA.rst +++ b/docs/docs_vfwHPA.rst @@ -29,11 +29,8 @@ This tutorial covers enhancements 1 to 5 in Background of https://wiki.onap.org/ Setting Up and Installation ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Some fixes for HPA support were made subsequent to the release of the Casablanca images. Several updated docker images need to be used to utilize the fixes. The details of the docker images that need to be used and the issues that are fixed are described at this link https://wiki.onap.org/display/DW/Docker+image+updates+for+HPA+vFW+testing -Instructions for updating the manifest of ONAP docker images can be found here: https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/#deploying-an-updated-docker-manifest - -Install OOM ONAP using the deploy script in the integration repo. Instructions for this can be found in this link https://wiki.onap.org/display/DW/OOM+Component. When the installation is complete (all the pods are either in running or completed state) Do the following; +Install OOM ONAP using the deploy script in the integration repo. Instructions for this can be found in this link https://docs.onap.org/projects/onap-oom/en/latest/oom_quickstart_guide.html. When the installation is complete (all the pods are either in running or completed state) Do the following; 1. Check that all the required components were deployed; diff --git a/docs/docs_vfw_edgex_k8s.rst b/docs/docs_vfw_edgex_k8s.rst index 2a8c42372..256d65948 100644 --- a/docs/docs_vfw_edgex_k8s.rst +++ b/docs/docs_vfw_edgex_k8s.rst @@ -274,7 +274,7 @@ the lab where we tested). This will cause multicloud to add the tenant to the k8s cloud region and then, similarly to #10 in the -`vFW HPA casablanca official documentation <https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/docs_vfwHPA.html#docs-vfw-hpa>`_, +`vFW HPA casablanca official documentation <https://docs.onap.org/projects/onap-integration/en/latest/docs_vfwHPA.html>`_, the service-subscription can be added to that object. **NOTE:** use same name cloud-region and cloud-owner name diff --git a/docs/docs_vipsec.rst b/docs/docs_vipsec.rst index f50326f60..db9e894ad 100644 --- a/docs/docs_vipsec.rst +++ b/docs/docs_vipsec.rst @@ -24,8 +24,6 @@ The deploy steps look just alike the one for vFW with HPA use case. It is also u Setting Up and Installation ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Instructions for updating the manifest of ONAP docker images can be found here: https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/#deploying-an-updated-docker-manifest - Install OOM ONAP using the deploy script in the integration repo. Instructions for this can be found in this link https://wiki.onap.org/display/DW/OOM+Component. When the installation is complete (all the pods are either in running or completed state) Do the following; diff --git a/docs/files/CI/ONAP_CI_8.png b/docs/files/CI/ONAP_CI_8.png Binary files differindex 2182c7123..3263e93f8 100644..100755 --- a/docs/files/CI/ONAP_CI_8.png +++ b/docs/files/CI/ONAP_CI_8.png diff --git a/docs/files/csv/release-demo-features.csv b/docs/files/csv/release-demo-features.csv index e61cde6a6..22bc99eaa 100644 --- a/docs/files/csv/release-demo-features.csv +++ b/docs/files/csv/release-demo-features.csv @@ -1,9 +1,5 @@ Issue-ID;Description -INT-1960;vFW CNF CDS Change Blueprint to BluePrint -INT-1960;vFW CNF CDS usecase automation scripts update -INT-1899;[vFW_CNF_CDS] Improve logging and fix tests typo -INT-1899;[vFW_CNF_CDS] Add workflow health-check and K8sHealthCheck.kt script -INT-1899;[vFW_CNF_CDS] Sort generated json files -INT-1899;[vFW_CNF_CDS] Add Healthcheck automation -INT-1899;[vFW_CNF_CDS] Provide Helm Tests for CNF -INT-1899;[vFW_CNF_CDS] Correct Makefile target +INT-2094;[APACHE] Add Apache CNF use case files +INT-2069;Make Network Slicing usecase more user friendly +INT-1960;[vFW CNF CDS] Fix issue with multiple tenants creation for k8s region +INT-1960;[vFW CNF CDS] vf_module and vnf name generation improvment in CBA diff --git a/docs/files/csv/release-integration-features.csv b/docs/files/csv/release-integration-features.csv index f2f385f4d..00575b2da 100644 --- a/docs/files/csv/release-integration-features.csv +++ b/docs/files/csv/release-integration-features.csv @@ -1,39 +1,30 @@ Issue-ID;Description -INT-2010;Release data-provider -INT-1979;E2E Network slicing - Istanbul Release Documentation -INT-1976;Updating release notes for CCVPN - Intent Based Networking and Cloud Leased Line Service. -DOC-765;Remove indirect deps -DOC-765;Make funcparserlib + lfdocs-conf work on RTD -DOC-765;Adds 2 upper-constraints to pin all the dependencies. -REQ-910;Update docs for OOF-SON use case -INT-1966;[DOC] Remove direct gating link -DCAEGEN2-2692;Fix problem with expired certs in FTPES tests -DCAEGEN2-2692;Update DFC tests to use file based conifg -TEST-360;[SECURITY] Fix waiver management of check_for_nonssl_ports test -INT-1735;Update Vagrantfile for tern -INT-1601;Enable VID -INT-1601;noheat: deploy ONAP -INT-1601;noheat: deploy MetalLB, cert-manager and prometheus -INT-1601;noheat: deploy helm with plugins & chartmuseum -INT-1601;noheat: install Ansible kubernetes collection -INT-1601;noheat: use Python 3 as Ansible interpreter -INT-1601;noheat: clone OOM repository -INT-1601;noheat: deploy kubernetes -INT-1601;noheat: deploy Docker -INT-1601;noheat deployment: use nfs0 as nexus3 bastion -INT-1601;noheat deployment: setup NFS server and clients -INT-1601;noheat deployment: add operator0 key to itself -INT-1601;noheat deployment: loosen security groups constraints -INT-1601;noheat deployment: Add groups to dynamic inventory -INT-1601;Update requirements of OpenStack noheat deployment -INT-1940;[CODESEARCH] Update documentation -INT-1940;[CODESEARCH] Always run the 'run_codesearch' provisioner -INT-1940;[CODESEARCH] Rework the nameserver provisioning -INT-1940;[CODESEARCH] Drop ssh authentication for Gerrit endpoint -INT-1940;[CODESEARCH] Rework how --git option works -INT-1942;[CODESEARCH] Add option to define custom polling interval -INT-1941;[CODESEARCH] Upgrade Vagrant box to utilise newest 20.04 LTS -INT-1922;Standard defined schema files in VES Collector -INT-1601;Set up network for in-cluster deployment stage -INT-1601;Add missing dependencies and artifacts for in-cluster deployment stage -INT-1601;Prepare operation machine for in-cluster deployment stage +INT-2097;[STRIMZI-CA] Add strimzi ca to cert checks +INT-2095;Broken URL to 5gbulkpm test case. +INT-2094;Upstream Apache use case into demo repository +INT-2093;Disable healtcheck for DCAE platform components +TEST-383;Fix HVVES test case in Jakarta release +INT-2078;smoke tests not more run due to jinja2 upstream lib bug +INT-2077;Add missing INFO.yaml files in integration/simulators/nf-simulator repository (and related repositories) +INT-2057;Use the latest Python 3.10.2 +INT-2051;Add cert manager support to netconf simulator +INT-2049;Release data-provider image +INT-2043;Update SDK version in data-provider +TEST-379;Integrate basic_cnf_macro test +INT-2040;Reset security waivers for jakarta +INT-2015;Create python baseline image +INT-2014;Create Java baseline image for Jakarta +INT-2009;Automate the committers management in INFO.yaml files +TEST-368;"No execution start time saved for..." error log in tests +INT-1998;A1 Policy Enforcement PoC documentation improvments +INT-1980;CNF/CBA - DayOneConfig.kt throw java.io.FileNotFoundException +INT-1974;Build pythonsdk-tests docker image for every change +INT-1971;Add gating mechanism on integration test changes +INT-1956;DT tests results should be available to check to the community +TEST-356;Create tests resources not in ONAP namespace +INT-1952;Run gating tests on selected pythonsdk-tests version/change +TEST-354;PNF macro failing due to: services "pnf-macro-test-simulator-mongo" +INT-1925;Issues during stability instantiation tests on weekly master +TEST-297;Include testuite/cds in a xtesting dockers +TEST-294;Integrate CDS regression tests in End to End CI/CD chain +INT-1665;Setup CI jobs, functional/unit tests, tests runners to automate Python tools testing diff --git a/docs/files/csv/release-integration-ref.csv b/docs/files/csv/release-integration-ref.csv index 4f6f4b4a0..c47a0046a 100644 --- a/docs/files/csv/release-integration-ref.csv +++ b/docs/files/csv/release-integration-ref.csv @@ -1,30 +1,33 @@ Repository;Revision -demo;129d553d323653461d14f248cb9e8b6f266eb5e3 -integration;81ef97d2e7f8bf1d50f590447725efd05ba9014b -integration/csit;85321a52e56422c1bb552c10387d27066decee84 -integration/docker/onap-java11;ad17a4087baaefb1adf9ad0dde3029b1da7dfc7d -integration/docker/onap-python;a0588db586ae626b4fadcfde450039ab69ed4171 -integration/ietf-actn-tools;2770f33536cfb828b7416adff8eafdd0a141a0b4 -integration/seccom;538d7faf46a58fdf8ff857770a9e65aa9c312913 -integration/simulators/5G-core-nf-simulator;ef3045db013ce7826c0c6f2a3597f7a1d1033106 -integration/simulators/nf-simulator;f739bd6b7e48edad36966a00894dc08de0c4de21 -integration/simulators/nf-simulator/avcn-manager;8be57ab7523dc201a54cf4f5b0251159af1fda38 -integration/simulators/nf-simulator/netconf-server;2cf18a71ceccf0ae6508a4ffabd1adef90772211 -integration/simulators/nf-simulator/pm-https-server;3f7d8d756e0951c95b894cdbec785ed4f24052e4 -integration/simulators/nf-simulator/ves-client;7397ac984b69f7605e6ccb0b5ab02a74b73e818b -integration/simulators/pnf-simulator;20fbea02fedad63770a5a7e3958adb71992a7878 -integration/simulators/ran-nssmf-simulator;85ccf7677389c9bd3f43c31d220347e9ebd4d404 -integration/simulators/ran-simulator;a3165afba7f422e61fecdce5c5c24d8b91d8bd40 -integration/usecases/A1-policy-enforcement;ada51c6695b785865eea3ccea45a13026bd03518 -integration/usecases/A1-policy-enforcement-r-apps;3ac3f212d7127e887625a344c3e4846269a01df0 -integration/xtesting;a93cdb28c8e9e05f8d794556dce52bca11b59028 -oparent;c6044f697e3345c8b907a4f8d5f0cfa3d4069071 -testsuite;b4680596e5c876b12dc416c305de69371d5aedd5 -testsuite/cds;9f83b04496cd16ae280af1e939eff20ff7195fc6 -testsuite/cds-mock-odl;ae2aebead9224fb0bbbe6aaf0b782b27a501dee9 +demo;a112ebd160d3acc20e6766d8550d757a0581797d +integration;fd5b23e8ff35aff3eacf0d20b6910b0257bcced0 +integration/csit;8f88f01b9fbbdd2af363a747ecf43b9de15a9b6e +integration/data-provider;a5d76c710471e8c6819a8d5963ee73349a48013c +integration/docker/onap-java11;1a12b2560c0b168c64e1b38a25d8284904b8ef01 +integration/docker/onap-python;5fb8770183d2bef14d47124b100dc4dec4ee1999 +integration/ietf-actn-tools;2e7a9a57f2610268002badc23748d483b653042e +integration/seccom;687008f10b08ded20cb222d732523fea270b9c8e +integration/simulators/5G-core-nf-simulator;7ee6ee299f53e226663645010b9467860a656c07 +integration/simulators/A1-policy-enforcement-simulator;a1408cfc73163ed209049b47098d86e2f94a538a +integration/simulators/core-nssmf-simulator;c3bbe92494ba80d10628dbe102eddaadaac9d421 +integration/simulators/nf-simulator;745a7b4c9bc5606a342f5fcb250b606836f73627 +integration/simulators/nf-simulator/avcn-manager;0e280f888bcc42909eee1aefe65a5a8b79a7477b +integration/simulators/nf-simulator/netconf-server;c7bd72db1a290848fdad94c2b3688c790b4e778f +integration/simulators/nf-simulator/pm-https-server;98b44a558e1993f0ceafbf22b250ba0975042229 +integration/simulators/nf-simulator/ves-client;4ac8f0ad9b5f627697f2d3a67bb47c3315737528 +integration/simulators/pnf-simulator;c942281da3cc77db1aee06ef69398fd57b970f31 +integration/simulators/ran-nssmf-simulator;220120e53977d6df4eda174dca710320a2bcba8f +integration/simulators/ran-simulator;b395e82cedb969d392fd4a1a2b13cfa8cf64cce7 +integration/usecases/A1-policy-enforcement;f29388582dc68a8f1cfdff4aa65f3839e9e1aaac +integration/usecases/A1-policy-enforcement-r-apps;3fc8bbb9080cd637318fb920056f5a51014e5c1f +integration/xtesting;1b5b1a3dc73431c671971a22abd875cd292c1692 +oparent;f95bafef87324b634305e1b98cf17838aa998d26 +testsuite;898230f3ead89797c4e4f774ccef38f7c23c0b7e +testsuite/cds;b1f769130a6abe8ac67f42fe74b834eb25f33c07 +testsuite/cds-mock-odl;4784fbe07e25a6894d6dfccf76f78e8710f20f11 testsuite/cds-mock-server;7db71adaf139e54f2186cfd19d468f5a1123835d testsuite/cds-mock-ssh;a43ce8950dcc36363c406b1cc4043dc7d623c9f4 -testsuite/oom;f3b6c657d38373ce2aaac9a2041285b75525bfc2 -testsuite/python-testing-utils;1911416dec8d483ccaa320b5ed0a6fbbafe1f9c2 -testsuite/pythonsdk-tests;1a77bcd6eb5ab695a232004b88e5e59d9d9ff6a3 -testsuite/robot-utils;8b80d8c8bebad201185639807ec50110fb857638 +testsuite/oom;5809297b562203922c13c843c085049148d78edb +testsuite/python-testing-utils;17d603cf6655198fa61873e4d715889998a92b69 +testsuite/pythonsdk-tests;81584955687e053d0697a63131b026fa0eda47c7 +testsuite/robot-utils;a67403bdb58cfdfc272801d9c4448a22bd40046d diff --git a/docs/files/csv/release-oparent-features.csv b/docs/files/csv/release-oparent-features.csv index f1ba6b3fa..80462fe00 100644 --- a/docs/files/csv/release-oparent-features.csv +++ b/docs/files/csv/release-oparent-features.csv @@ -1,12 +1,2 @@ Issue-ID;Description - -INT-1948;Set default branch in oparent gitreview file -INT-1948;Bump oparent to 3.2.2 -INT-1948;Release oparent 3.2.1 Istanbul -INT-1938;Upgrade depenencies for Istanbul -POLICY-3209; Step version of spring to 5.3.8 -POLICY-3206;Update Checkstyle to version 8.43 -INT-1711;Bump oparent 3.2.1-SNAPSHOT -INT-1711;Release 3.2.0 oparent -INT-1766;Upgrade latest dependencies -INT-1756;Bump master to 3.2.0-SNAPSHOT +CPS-475;Enable @surpressWarnings for Checkstyle diff --git a/docs/files/csv/release-pythonsdk-features.csv b/docs/files/csv/release-pythonsdk-features.csv index 8c119f0bc..1684b2234 100644 --- a/docs/files/csv/release-pythonsdk-features.csv +++ b/docs/files/csv/release-pythonsdk-features.csv @@ -1,20 +1,14 @@ Issue-ID;Description -TEST-364;[TEST] Do not use VID API in tests -INT-1978;[BASIC_CLAMP] Adapt tca clamp plugin -TEST-361;Update HEAT-file for ubuntu20 used for basic_vm_macro test -TEST-357;[TEST] Get cleanup reports from substeps also if parent step has no cleanup report -MULTICLOUD-1377;Change rb-definition-version identifier -TEST-352;[TEST] Use the newest ONAP SDK version -TEST-349;[TEST] Basic macro stability scenario -TEST-347;[TEST] Check if cds blueprintsprocessor service type is 'NodePort' -TEST-341;[TEST] Wait for instantiated simulator longer -TEST-341;[TEST] Create "pnf-macro-test-simulator" resources -TEST-341;[TEST] Use nf-simulator/vesclient -TEST-315;[OPTIM] Tune SDC delay before certification -INT-1894;[TEST] Patch ip values in pnf-simulator event -TEST-333;[TEST] Do not try to recreate already created SDC resources -TEST-338;[CLAMP] Fix Policy exception in basic_clamp -TEST-337;[TEST] Catch ConnectionError exception during pnf simulator startup -TEST-336;[TEST] Catch k8s connection exceptions -TEST-334;[CLAMP] Update clamp to allow re-play of the test -TEST-332;[EXCEPTIONS] Distinguish onaptests and onapsdk exception
\ No newline at end of file +SDC-3949;Log exception stack trace on test failure +TEST-384;[TEST] Change of the k8sregion name +TEST-382;[TEST] Change of the namespace for basic_cnf_macro +INT-2078;Use Python ONAP SDK 9.4.0 +TEST-354;[TEST] PNF macro nad CDS resource resoulution tests are failing on retry +INT-2078;[PYTHON] Improve requirement versioning +TEST-380;[TEST] Add cds resource resolution missing cleanup method call +TEST-376;[TEST] Basic CNF macro +TEST-356;[TEST] Do not create simulators in "onap" namespace +TEST-369;[TEST] Fix cds-resource-resolution test +TEST-368;[TEST] Do not show "No execution start time..." error log message for skipped substeps +TEST-358;[TEST] Added support for multi-vnf macro instantiation +INT-1994;[INTEGRATION] Use the newest onapsdk (9.0.0)
\ No newline at end of file diff --git a/docs/files/csv/release-testsuite-features.csv b/docs/files/csv/release-testsuite-features.csv index ee2d03418..9b1a96f8f 100644 --- a/docs/files/csv/release-testsuite-features.csv +++ b/docs/files/csv/release-testsuite-features.csv @@ -1,10 +1,19 @@ Issue-ID;Description -TEST-364;[TEST] Do not use VID API in pnf-registrate test -TEST-365;[HEALTHCHECK] Remove VID from healthcheck -DCAEGEN2-2718;Use configMap instead of Consul to configure hv-ves -TEST-353;Cmpv2 robot testcase fails when using proxy -MULTICLOUD-1362;[MULTICLOUD] Exclude multicloud healthcheck tests -OPTFRA-969;[OOF] Remove CMSO related test cases -TEST-346;CMPv2 test case fails with error No keyword with name -TEST-345;Refactor ves client and mongo db host name usage in CMPv2 test -TEST-339;[POLICY] Increase Timeout for Enhanced Policy Healthcheck Test +INT-1895;[ROBOT] Change performance measurements topic for 5gbulkpm +INT-1895;[ROBOT] Add timout flag for helm unintsll operation +INT-1895;[ROBOT] Change pm mapper readiness check to HTTP +INT-2012;[Healthcheck] Remove clamp Healthcheck +NT-1895;[ROBOT] Adopt DCAEMOD test cases to helm based deployment +INT-2093;[DCAE] Deprecate DCAE basic healthcheck +INT-1895;[ROBOT] Fix failing CMPv2 and 5gbulkpm test cases in CI +TEST-383;[INTEGRATION] Fix failing HVVES test case in Jakarta release +OOM-2921;[INT] Remove Portal robot test from full and medium test suite +INT-1895;[ROBOT] ADD CMPv2 test cases that use helm based components +POLICY-3887;Add policy cleanup if policy is existing before policy health check execution +INT-1895;[ROBOT] FIX BULKPM test cases for Jakarta release +SO-3829;[HEALTCHECK] remove mariadbgalera connectivity tests from core +SO-3829;[SO] MariaDB Galera connectivity with SO Issue-ID:SO-3829 +INT-1895;[ROBOT] ADD HTTPS based BULKPM test cases that use helm based components +POLICY-3815;[POLICY] Change API and PAP usernames +INT-1895;[ROBOT] ADD BULKPM test cases that use helm based component services +INT-2006;[TIMEOUT] Extend healthcheck timeout value diff --git a/docs/files/csv/repo-integration.csv b/docs/files/csv/repo-integration.csv index c9487da6f..93469a4c1 100644 --- a/docs/files/csv/repo-integration.csv +++ b/docs/files/csv/repo-integration.csv @@ -1,6 +1,7 @@ Repository;Description;Link integration;Historical main repository including documentation, simulators (e.g. mass PNF simulator), non robot tests (e.g. security tests, vCPE Tosca,..), ...;`link <https://git.onap.org/integration>`__ integration/csit;Repository hosting some tooling to start component functional tests in Jenkins (To be deprecated in Guilin as such tests must be reinsourced by the projects);`link <https://git.onap.org/integration/csit>`__ +integration/data-provider;Project that provides a tool to automate common ONAP resource creation;`link <https://git.onap.org/integration/data-provider>`__ integration/docker/onap-java11;Java11 baseline image conformed to SECCOM recommendations;`link <https://git.onap.org/integration/docker/onap-java11>`__ integration/docker/onap-python;Python baseline image conformed to SECCOM recommendations;`link <https://git.onap.org/integration/docker/onap-python>`__ integration/ietf-actn-tools;IETF ACTN tools introduced in Honolulu);`link <https://git.onap.org/integration/ietf-actn-tools>`__ @@ -8,4 +9,3 @@ integration/seccom;Repory hosting seccom recommended versions and security test integration/usecases/A1-policy-enforcement;A1 policy enforcement introduced in Honolulu;`link <https://git.onap.org/integration/usecases/A1-policy-enforcement>`__ integration/usecases/A1-policy-enforcement-r-apps;A1 policy enforcement (analyticis part) introduced in Honolulu;`link <https://git.onap.org/integration/usecases/A1-policy-enforcement-r-apps>`__ integration/xtesting;Repository in charge to build th xtesting dockers used in CI/CD chains;`link <https://git.onap.org/integration/xtesting>`__ -integration/data-provider;Project that provides a tool to automate common ONAP resource creation;`link <https://git.onap.org/integration/data-provider>`__ diff --git a/docs/files/csv/s3p-instantiation.csv b/docs/files/csv/s3p-instantiation.csv index 6b3febd3d..d21f2ee5e 100644 --- a/docs/files/csv/s3p-instantiation.csv +++ b/docs/files/csv/s3p-instantiation.csv @@ -1,6 +1,6 @@ -Parameters;Istanbul;Honolulu -Number of tests;1310;1410 -Global success rate;97%;96% -Min duration;193s;81s -Max duration;2128s;2000s -mean duration;564s;530s
\ No newline at end of file +Parameters;Jakarta;Istanbul;Honolulu +Number of tests;1190;1310;1410 +Global success rate;96%;97%;96% +Min duration;140s;193s;81s +Max duration;2075s;2128s;2000s +mean duration;603s;564s;530s
\ No newline at end of file diff --git a/docs/files/csv/s3p-sdc.csv b/docs/files/csv/s3p-sdc.csv index f89fef24a..cd9bb9e6c 100644 --- a/docs/files/csv/s3p-sdc.csv +++ b/docs/files/csv/s3p-sdc.csv @@ -1,6 +1,6 @@ -Parameters;Istanbul;Honolulu -Number of tests;1085;715 -Global success rate;92%;93% -Min duration;111s;80s -Max duration;799s;1128s -mean duration;366s;565s
\ No newline at end of file +Parameters;Jakarta;Istanbul;Honolulu +Number of tests;1000;1085;715 +Global success rate;92%;92%;93% +Min duration;119;111s;80s +Max duration;844;799s;1128s +mean duration;394s;366s;565s
\ No newline at end of file diff --git a/docs/files/csv/tests-healthcheck.csv b/docs/files/csv/tests-healthcheck.csv index 6571255a9..df5411cbb 100644 --- a/docs/files/csv/tests-healthcheck.csv +++ b/docs/files/csv/tests-healthcheck.csv @@ -5,7 +5,6 @@ healthdist;Check the onboarding and distribution of the vFW;`robot tests <https: postinstall;Check dmaap and AA&I Design model DB tests;`robot tests <https://git.onap.org/testsuite/tree/robot/testsuites/post-install-tests.robot>`__;`robotframework <https://robotframework.org/>`__ ves-collector (new);Suite for checking handling events by VES Collector;`code <https://git.onap.org/testsuite/tree/robot/testsuites/ves.robot>`__;`robotframework <https://robotframework.org/>`__ hv-ves;HV-VES 'Sunny Scenario' Robot Framework test - message is sent to the collector and Kafka topic is checked if the message has been published. Content is decoded and checked.;`code <https://git.onap.org/testsuite/tree/robot/testsuites/hvves-ci.robot>`__;`robotframework <https://robotframework.org/>`__ -basic_cds;CDS blueprint enrichment, open a nodeport on CDS then enrich CDS CBA;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/cds_blueprint_enrichment.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ basic_onboard;onboard a model, subset of most of the other basic_* tests, created to perform stability testing;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_onboard.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ dcaemod;Check new DCAEmod;`robot tests <https://git.onap.org/testsuite/tree/robot/testsuites/dcaemod.robot>`__;`robotframework <https://robotframework.org/>`__ -**cps-healthcheck**;Call liveness and readiness probes of the CPS module;`robot tests <https://github.com/onap/cps/blob/master/csit/tests/actuator/actuator.robot>`__;`robotframework <https://robotframework.org/>`__ +cps-healthcheck;Call liveness and readiness probes of the CPS module;`robot tests <https://github.com/onap/cps/blob/master/csit/tests/actuator/actuator.robot>`__;`robotframework <https://robotframework.org/>`__ diff --git a/docs/files/csv/tests-infrastructure-healthcheck.csv b/docs/files/csv/tests-infrastructure-healthcheck.csv index a61e02991..0bdabf3cb 100644 --- a/docs/files/csv/tests-infrastructure-healthcheck.csv +++ b/docs/files/csv/tests-infrastructure-healthcheck.csv @@ -2,4 +2,3 @@ Tests;Description;Code;Comments onap-helm;Verify Helm chart status, the test has been updated to take into account Helm3;`python module <https://gitlab.com/Orange-OpenSource/lfn/tools/helm-onap-status>`__; onap-k8s;Check common resources of the ONAP Kubernetes namespace ;`python module <https://gitlab.com/Orange-OpenSource/lfn/tools/kubernetes-status>`__;kubernetes python library nodeport_check_certs;This test list the nodeports and tries to get SSL information to evaluate the validity of the certificates (expiration and issuer) used on the nodeports;`python module <https://git.onap.org/integration/tree/test/security/check_certificates>`__;pyopenssl, kubernetes python libraries -**internal_check_certs**;This test list the internal ports and tries to get SSL information to evaluate the validity of the certificates (expiration and issuer) used ;`python module <https://git.onap.org/integration/tree/test/security/check_certificates>`__;pyopenssl, kubernetes python libraries diff --git a/docs/files/csv/tests-security.csv b/docs/files/csv/tests-security.csv index 4e88b0ada..0ded0a206 100644 --- a/docs/files/csv/tests-security.csv +++ b/docs/files/csv/tests-security.csv @@ -7,4 +7,4 @@ http_public_endpoints;check that there is no public http endpoints exposed in ON jdpw_ports;check that there are no internal java ports;`bash script <https://git.onap.org/integration/plain/test/security/check_for_jdwp.sh>`__;kubectl, procfs kube_hunter;security suite to search k8s vulnerabilities (upstream src aquasecurity);`kube-Hunter <https://github.com/aquasecurity/kube-hunter>`__; `kube-Hunter <https://github.com/aquasecurity/kube-hunter>`__ versions;check that Java and Python are available only in versions recommended by SECCOM. This test is long and run only in Weekly CI chains;`python module <https://git.onap.org/integration/tree/test/security/check_versions>`__;cerberus, kubernetes python lib, -**tern**;Check the component licenses within the ONAP dockers;`bash script <https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/blob/master/scripts/run_tern.sh>`__;kubectl +tern;Check the component licenses within the ONAP dockers;`bash script <https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/blob/master/scripts/run_tern.sh>`__;kubectl diff --git a/docs/files/csv/tests-smoke.csv b/docs/files/csv/tests-smoke.csv index b990624c1..db2c173de 100644 --- a/docs/files/csv/tests-smoke.csv +++ b/docs/files/csv/tests-smoke.csv @@ -2,8 +2,10 @@ Tests;Description;Code;Comments basic_vm;Onboard, distribute and instantiate an Openstack VM using à la carte BPMN, replaced the former basic_vm test;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_vm.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ basic_network;Onboard, distribute and instantiate a Neutron network;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_network.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ basic_cnf;Onboard (new), distribute and instantiate a Kubernetes pods;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_cnf.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ -**5gbulkpm**;5G Bulk PM Usecase functionality. The test has been significantly enhanced in Honolulu;`code <https://git.onap.org/testsuite/tree/robot/testsuites/usecases/5gbulkpm.robot>`__;`robotframework <https://robotframework.org/>`__ +5gbulkpm;5G Bulk PM Usecase functionality. The test has been significantly enhanced in Honolulu;`code <https://git.onap.org/testsuite/tree/robot/testsuites/usecases/5gbulkpm.robot>`__;`robotframework <https://robotframework.org/>`__ pnf-registrate;Executes the PNF registration test cases including setup and teardown;`code <https://git.onap.org/testsuite/tree/robot/testsuites/pnf-registration.robot>`__;`robotframework <https://robotframework.org/>`__ cmpv2;CMPv2 Usecase functionality;`code <https://git.onap.org/testsuite/tree/robot/testsuites/cmpv2.robot>`__;`robotframework <https://robotframework.org/>`__ -**basic_clamp**;distribute a model, enrich it with a tca blueprint, call Clamp to create a loop then instantiate it in Policy and DCAE;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_clamp.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ -**basic_vm_macro**;Instantiate a VM using macro bpmn;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_vm_macro.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ +basic_vm_macro;Instantiate a VM using macro bpmn;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_vm_macro.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ +**pnf_macro**;Run PNF simulator, onboard, distribute and instantiate service including PNF;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/pnf_macro.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ +**cds_resource_resolution**;Upload blueprint file into CDS, execute test workflow and check results;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/cds_resource_resolution.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ +**basic_cnf_macro**;Onboard (new), distribute and instantiate a Kubernetes pods using SO's macro flow;`code <https://git.onap.org/testsuite/pythonsdk-tests/tree/src/onaptests/scenario/basic_cnf_macro.py>`__;`onap_pythonsdk <https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk>`__, `pythonsdk-tests <https://git.onap.org/testsuite/pythonsdk-tests/tree/>`__ diff --git a/docs/files/csv/usecases.csv b/docs/files/csv/usecases.csv index ad91ffd54..629088202 100644 --- a/docs/files/csv/usecases.csv +++ b/docs/files/csv/usecases.csv @@ -1,4 +1,4 @@ Ref;Summary;Link;Contacts -REQ-440;E2E Network Slicing;:ref:`official doc <docs_E2E_network_slicing>`;Lin Meng -REQ-429;5G OOF SON;:ref:`official doc <docs_5G_oof_son>`;Swaminathan Seetharaman +REQ-440;E2E Network Slicing;:ref:`official doc <docs_E2E_network_slicing>`;Kevin Tang +REQ-429;5G OOF SON;:ref:`official doc <docs_5G_oof_son>`;N. K. Shankaranarayanan REQ-459;CCVPN-Transport Slicing;:ref:`official doc <docs_ccvpn>`;Henry Yu diff --git a/docs/files/s3p/jakarta-dashboard.png b/docs/files/s3p/jakarta-dashboard.png Binary files differnew file mode 100755 index 000000000..e5f2fd1b8 --- /dev/null +++ b/docs/files/s3p/jakarta-dashboard.png diff --git a/docs/integration-CICD.rst b/docs/integration-CICD.rst index aed0e6f0a..e85e35eed 100644 --- a/docs/integration-CICD.rst +++ b/docs/integration-CICD.rst @@ -11,7 +11,7 @@ CI/CD Integration team deals with 2 different CI/CD systems. - Jenkins CI/CD, CI managed by LF IT and CD by Integration team - - GitLab-ci managed by Integration and OOM team + - GitLab-CI managed by Integration team Continuous Integration ---------------------- @@ -40,30 +40,6 @@ The Jenkins jobs (jjb) are hosted in https://git.onap.org/ci-management/. Continuous Deployment --------------------- -There are 2 Continuous Deployment architectures. - -Jenkins CD on Windriver/Intel lab -.................................. - -The CD part on Windriver/Intel is based on Jenkins. - -It is based on a standalone VM hosting a Jenkins server. -The credentials of this VM as well as the Jenkins server have been provided to -integration committers. - -Several jobs can be triggered from this Jenkins interface. -Historically several chains were run daily (staging/release) but due to -performance issues, they have all been stopped. -Only SB-00 has been kept for use case support. -The Jenkins interface was however used to launch the installation of SB-00. - -This Jenkins script is leveraging resources available in OOM and integration -repositories. - -The replacement of this CD by a GitLab runner based CD to unify the CD -management was planned, but finalizing the operation in Guilin was not possible -due to performance issues. - GitLab CD ......... @@ -71,12 +47,7 @@ This CD is leveraging public gitlab-ci mechanism and used to deploy several ONAP labs: - Daily Master: daily run using OOM Master -- Daily Guilin: daily run using the last stable version during Honolulu Release - processing -- Daily Honolulu: daily run setup at RC0 (candidate dockers available for integration) -- Daily Istanbul: daily run setup at RC0 (candidate dockers available for integration) - Weekly Master: run once a week with longer tests -- Weekly Istanbul: run once a week with longer tests - Gating: run on OOM, clamp or SO patchset submission. It means a full ONAP deployment on demand based on new patchset declared in gerrit. diff --git a/docs/integration-labs.rst b/docs/integration-labs.rst index 9579f9590..943e402a9 100644 --- a/docs/integration-labs.rst +++ b/docs/integration-labs.rst @@ -10,47 +10,15 @@ Integration Labs .. important:: The Integration team deals with several community labs: - - The Windriver/Intel lab - The Azure staging lab - The Orange openlab - The DT lab - The Nokia dualstack lab + - The University New Hempshire lab Additionally integration contributors may deal with their own lab pushing results in the integration portal (See DT http://testresults.opnfv.org/onap-integration/dt/dt.html) -Windriver/Intel lab -------------------- - -The Historical Community Lab -............................ - -This lab is the historical lab of ONAP integration team based on OpenStack Ocata. - -The figure hereafter shows all the ONAP projects consuming Windriver/Intel lab -resources (April 2020). - -.. figure:: files/windriver/windriver_servers.png - :align: center - -This lab is mainly used by the projects for the development. -A staging lab named SB-00 is also available. - -If you want to use this lab, you need a VPN access. The procedure is described in -the `wiki <https://wiki.onap.org/pages/viewpage.action?pageId=29787070>`_. - -Environment Installation Scripts -................................ - -In addition to the official OOM scripts, Integration used to provide some -extra scripts/guidelines to install your OpenStack infrastructure thanks to a -heat template. See :ref:`Integration heat guideline <integration-installation>` -for details. These scripts were used mainly in Windriver labs but are not actively -maintained. - -.. caution: - The official reference for installation is the OOM documentation. - Azure staging lab ----------------- @@ -80,3 +48,9 @@ Nokia lab Nokia setup a lab to support the dual stack IPv4/IPv6 tests. Results are shared with the community in `<https://logs.onap.org/onap-integration/daily/onap_daily_nokia_dualstack_master/>`_ + +University New Hempshire lab +---------------------------- + +Lab for community use. See `ONAP UNH lab <https://wiki.onap.org/display/DW/ONAP+IOL-UNH+Lab>`_ +for more information. diff --git a/docs/integration-repositories.rst b/docs/integration-repositories.rst index 1d2def58e..fe821bfdc 100644 --- a/docs/integration-repositories.rst +++ b/docs/integration-repositories.rst @@ -16,11 +16,11 @@ Most of the repositories are internal ONAP repositories. ├── demo ├── integration │ ├── csit + | ├── data-provider │ ├── docker │ │ ├── onap-java11 │ │ └── onap-python │ ├── ietf-actn-tools - │ ├── integration │ ├── seccom │ ├── simulators │ │ ├──5G-core-nf-simulator diff --git a/docs/integration-s3p.rst b/docs/integration-s3p.rst index b41a37323..be2edfeeb 100644 --- a/docs/integration-s3p.rst +++ b/docs/integration-s3p.rst @@ -2,15 +2,14 @@ Creative Commons Attribution 4.0 International License. .. _integration-s3p: -Stability/Resiliency -==================== +Stability +========= .. important:: The Release stability has been evaluated by: - - The daily Istanbul CI/CD chain + - The daily Jakarta CI/CD chain - Stability tests - - Resiliency tests .. note: The scope of these tests remains limited and does not provide a full set of @@ -20,12 +19,12 @@ CI results ---------- As usual, a daily CI chain dedicated to the release is created after RC0. -An Istanbul chain has been created on the 5th of November 2021. -The daily results can be found in `LF daily results web site -<https://logs.onap.org/onap-integration/daily/onap_daily_pod4_istanbul/>`_. +The daily results can be found in `LF Orange lab daily results web site +<https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/>`_ and +`LF DT lab daily results web site <https://logs.onap.org/onap-integration/daily/onap-daily-dt-oom-master/>`_. -.. image:: files/s3p/istanbul-dashboard.png +.. image:: files/s3p/jakarta-dashboard.png :align: center @@ -34,17 +33,11 @@ Infrastructure Healthcheck Tests These tests deal with the Kubernetes/Helm tests on ONAP cluster. -The global expected criteria is **75%**. +The global expected criteria is **100%**. The onap-k8s and onap-k8s-teardown, providing a snapshop of the onap namespace in Kubernetes, as well as the onap-helm tests are expected to be PASS. -nodeport_check_certs test is expected to fail. Even tremendous progress have -been done in this area, some certificates (unmaintained, upstream or integration -robot pods) are still not correct due to bad certificate issuers (Root CA -certificate non valid) or extra long validity. Most of the certificates have -been installed using cert-manager and will be easily renewable. - .. image:: files/s3p/istanbul_daily_infrastructure_healthcheck.png :align: center @@ -70,11 +63,6 @@ The expectation is **100% OK**. .. figure:: files/s3p/istanbul_daily_smoke.png :align: center -An error has been reported since Guilin (https://jira.onap.org/browse/SDC-3508) on -a possible race condition in SDC preventing the completion of the certification in -SDC and leading to onboarding errors. -This error may occur in case of parallel processing. - Security Tests ~~~~~~~~~~~~~~ @@ -83,108 +71,19 @@ See the :ref:`the Integration Test page <integration-tests>` for details. Waivers have been granted on different projects for the different tests. The list of waivers can be found in -https://git.onap.org/integration/seccom/tree/waivers?h=istanbul. +https://git.onap.org/integration/seccom/tree/waivers?h=jakarta. -The expectation is **100% OK**. The criteria is met. +nodeport_check_certs test is expected to fail. Even tremendous progress have +been done in this area, some certificates (unmaintained, upstream or integration +robot pods) are still not correct due to bad certificate issuers (Root CA +certificate non valid) or extra long validity. Most of the certificates have +been installed using cert-manager and will be easily renewable. + +The expectation is **80% OK**. The criteria is met. .. figure:: files/s3p/istanbul_daily_security.png :align: center -Resiliency tests ----------------- - -The goal of the resiliency testing was to evaluate the capability of the -Istanbul solution to survive a stop or restart of a Kubernetes worker node. - -This test has been automated thanks to the -Litmus chaos framework(https://litmuschaos.io/) and automated in the CI on the -weekly chains. - -2 additional tests based on Litmus chaos scenario have been added but will be tuned -in Jakarta. - -- node cpu hog (temporary increase of CPU on 1 kubernetes node) -- node memory hog (temporary increase of Memory on 1 kubernetes node) - -The main test for Istanbul is node drain corresponding to the resiliency scenario -previously managed manually. - -The system under test is defined in OOM. -The resources are described in the table below: - -.. code-block:: shell - - +-------------------------+-------+--------+--------+ - | Name | vCPUs | Memory | Disk | - +-------------------------+-------+--------+--------+ - | compute12-onap-istanbul | 16 | 24Go | 10 Go | - | compute11-onap-istanbul | 16 | 24Go | 10 Go | - | compute10-onap-istanbul | 16 | 24Go | 10 Go | - | compute09-onap-istanbul | 16 | 24Go | 10 Go | - | compute08-onap-istanbul | 16 | 24Go | 10 Go | - | compute07-onap-istanbul | 16 | 24Go | 10 Go | - | compute06-onap-istanbul | 16 | 24Go | 10 Go | - | compute05-onap-istanbul | 16 | 24Go | 10 Go | - | compute04-onap-istanbul | 16 | 24Go | 10 Go | - | compute03-onap-istanbul | 16 | 24Go | 10 Go | - | compute02-onap-istanbul | 16 | 24Go | 10 Go | - | compute01-onap-istanbul | 16 | 24Go | 10 Go | - | etcd03-onap-istanbul | 4 | 6Go | 10 Go | - | etcd02-onap-istanbul | 4 | 6Go | 10 Go | - | etcd01-onap-istanbul | 4 | 6Go | 10 Go | - | control03-onap-istanbul | 4 | 6Go | 10 Go | - | control02-onap-istanbul | 4 | 6Go | 10 Go | - | control01-onap-istanbul | 4 | 6Go | 10 Go | - +-------------------------+-------+--------+--------+ - - -The test sequence can be defined as follows: - -- Cordon a compute node (prevent any new scheduling) -- Launch node drain chaos scenario, all the pods on the given compute node - are evicted - -Once all the pods have been evicted: - -- Uncordon the compute node -- Replay a basic_vm test - -This test has been successfully executed. - -.. image:: files/s3p/istanbul_resiliency.png - :align: center - -.. important:: - - Please note that the chaos framework select one compute node (the first one by - default). - The distribution of the pods is random, on our target architecture about 15 - pods are scheduled on each node. The chaos therefore affects only a limited - number of pods. - -For the Istanbul tests, the evicted pods (compute01) were: - - -.. code-block:: shell - - NAME READY STATUS RESTARTS AGE - onap-aaf-service-dbd8fc76b-vnmqv 1/1 Running 0 2d19h - onap-aai-graphadmin-5799bfc5bb-psfvs 2/2 Running 0 2d19h - onap-cassandra-1 1/1 Running 0 2d19h - onap-dcae-ves-collector-856fcb67bd-lb8sz 2/2 Running 0 2d19h - onap-dcaemod-distributor-api-85df84df49-zj9zn 1/1 Running 0 2d19h - onap-msb-consul-86975585d9-8nfs2 1/1 Running 0 2d19h - onap-multicloud-pike-88bb965f4-v2qc8 2/2 Running 0 2d19h - onap-netbox-nginx-5b9b57d885-hjv84 1/1 Running 0 2d19h - onap-portal-app-66d9f54446-sjhld 2/2 Running 0 2d19h - onap-sdnc-ueb-listener-5b6bb95c68-d24xr 1/1 Running 0 2d19h - onap-sdnc-web-8f5c9fbcc-2l8sp 1/1 Running 0 2d19h - onap-so-779655cb6b-9tzq4 2/2 Running 1 2d19h - onap-so-oof-adapter-54b5b99788-x7rlk 2/2 Running 0 2d19h - -In the future, it would be interesting to elaborate a resiliency testing strategy -in order to check the eviction of all the critical components. - Stability tests --------------- @@ -231,7 +130,7 @@ The following graphs provides a good view of the SDC stability test. .. csv-table:: S3P Onboarding stability results :file: ./files/csv/s3p-sdc.csv - :widths: 60,20,20 + :widths: 60,20,20,20 :delim: ; :header-rows: 1 @@ -281,7 +180,7 @@ The results can be described as follows: .. csv-table:: S3P Instantiation stability results :file: ./files/csv/s3p-instantiation.csv - :widths: 60,20,20 + :widths: 60,20,20,20 :delim: ; :header-rows: 1 diff --git a/docs/integration-tests.rst b/docs/integration-tests.rst index 3abe7735b..6453e55ef 100644 --- a/docs/integration-tests.rst +++ b/docs/integration-tests.rst @@ -71,7 +71,7 @@ All the pages and artifacts are pushed to LF backend: - Daily chains: https://logs.onap.org/onap-integration/daily - Weekly chains: https://logs.onap.org/onap-integration/weekly -- Gating chains: the result link is indicated in gerrit +- Gating chains: the result link is indicated in gerrit A video has been recorded to help launching some of the automated tests on ONAP Guilin. See `Running ONAP tests in Guilin Video <https://www.youtube.com/watch?v=ABvuJfyGDmw>`_ @@ -151,8 +151,8 @@ to adapt then run the security tests on your own system. Note for security tests, integration team follows `SECCOM recommendations and apply waivers granted by SECCOM if needed through xfail lists <https://git.onap.org/integration/seccom/tree/>`_. -Stability/Resiliency tests --------------------------- +Stability tests +--------------- Ensuring the stability of ONAP is one of the missions of the Integration team. CI chains and stability tests are performed to help stabilising the release. diff --git a/docs/release-notes.rst b/docs/release-notes.rst index ae1015190..0485f5b87 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -3,7 +3,7 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. http://creativecommons.org/licenses/by/4.0 -Integration Istanbul Release Notes +Integration Jakarta Release Notes ================================== .. csv-table:: Integration Releases @@ -14,20 +14,22 @@ Integration Istanbul Release Notes .. important:: - - Creation of an Istanbul Daily CI/CD chain - - Creation of Java and Python baseline images for Istanbul + - Creation of an Jakarta Daily CI/CD chain + - Creation of Java and Python baseline images for Jakarta - Update of Seccom waivers and version recommendations - - Stability tests (basic_onboard, basic_vm) - - New tests (cps-healthcheck) + - Adapt robot tests to DCAE project changes + - New tests (basic_cnf_macro) - New repositories (see dedicated section) + - Release ONAP Data Provider tool + - Automate repositories INFO.yaml updates - Bug fixes - ONAP tests library gating tests Quick Links: - - `Istanbul Integration page <https://wiki.onap.org/display/DW/Integration+Istanbul>`_ - - `Istanbul Integration JIRA follow-up <https://wiki.onap.org/display/DW/Istanbul+Integration+Blocking+points>`_ - - `Istanbul Integration weather Board <https://wiki.onap.org/display/DW/0%3A+Integration+Weather+Board+for+Istanbul+Release>`_ + - `Jakarta Integration page <https://wiki.onap.org/display/DW/Integration+Jakarta>`_ + - `Jakarta Integration JIRA follow-up <https://wiki.onap.org/display/DW/Jakarta+Integration+Blocking+points>`_ + - `Jakarta Integration weather Board <https://wiki.onap.org/display/DW/0%3A+Integration+Weather+Board+for+Jakarta+Release>`_ Code changes ------------ @@ -38,8 +40,8 @@ Integration Repo :Release Date: 2021-10-14 -Version: 9.0.0 (aka Istanbul) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Version: 10.0.0 (aka Jakarta) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: Integration Changes :file: ./files/csv/release-integration-features.csv @@ -62,8 +64,8 @@ Main changes: Robot (Testsuite) ................. -Version: 1.9.0 -^^^^^^^^^^^^^^ +Version: 1.10.0 +^^^^^^^^^^^^^^^ Main changes: @@ -77,7 +79,7 @@ Main changes: O-Parent ........ -Version: 3.2.2 +Version: 3.3.1 ^^^^^^^^^^^^^^ .. csv-table:: Oparent Changes @@ -89,8 +91,8 @@ Version: 3.2.2 Demo Artifacts (Heat Templates) ............................... -Version: 1.9.0 -^^^^^^^^^^^^^^ +Version: 1.10.0 +^^^^^^^^^^^^^^^ .. csv-table:: Demo Changes :file: ./files/csv/release-demo-features.csv @@ -104,7 +106,7 @@ The demo artifacts are pushed to https://nexus.onap.org/content/repositories/rel Use Cases and Requirements -------------------------- -See dedicated :ref:`Istanbul Use Cases and requirements page <docs_usecases_release>` +See dedicated :ref:`Jakarta Use Cases and requirements page <docs_usecases_release>` Maturity Testing Notes ---------------------- diff --git a/docs/usecases/release_automated_usecases.rst b/docs/usecases/release_automated_usecases.rst index aa7369380..1ec262c33 100644 --- a/docs/usecases/release_automated_usecases.rst +++ b/docs/usecases/release_automated_usecases.rst @@ -8,7 +8,7 @@ Automated Use Cases ------------------- -These use cases have been run on the Daily Honolulu CI chains and are used to +These use cases have been run on the Daily Jakarta CI chains and are used to validate the integration of any new dockers in OOM. New tests are indicated in **bold**. diff --git a/docs/usecases/release_usecases.rst b/docs/usecases/release_usecases.rst index 066dbc793..2dcd270fd 100644 --- a/docs/usecases/release_usecases.rst +++ b/docs/usecases/release_usecases.rst @@ -5,14 +5,14 @@ :orphan: -Istanbul Use Cases -================== +Jakarta Use Cases +================= Description ----------- This session includes use cases and functional requirements which have been -officially verified in Istanbul release by the ONAP community. +officially verified in Jakarta release by the ONAP community. For each use case or functional requirement, you can find contact names and a link to the associated documentation. @@ -27,20 +27,11 @@ This documentation deals with Use cases --------- -Istanbul Official Use Cases -~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Jakarta Official Use Cases +~~~~~~~~~~~~~~~~~~~~~~~~~~ .. csv-table:: :file: ../files/csv/usecases.csv :widths: 10,40,20,30 :delim: ; :header-rows: 1 - -Old Use Cases Tested in Istanbul -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -.. csv-table:: - :file: ../files/csv/usecases-old-valid.csv - :widths: 50,20,30 - :delim: ; - :header-rows: 1 |
