There are 3 PNF software upgrade scenarios supported in Frankfurt release:
-* `Using direct Netconf/Yang interface with PNF <docs_5G_PNF_Software_Upgrade_direct_netconf_yang.html>`_
+* `Using direct Netconf/Yang interface with PNF <docs_5G_PNF_Software_Upgrade_direct_netconf_yang>`
- (https://wiki.onap.org/pages/viewpage.action?pageId=64007309)
-* `Using Ansible protocol with EM <docs_5G_PNF_Software_Upgrade_ansible_with_EM.html>`_
+* `Using Ansible protocol with EM <docs_5G_PNF_Software_Upgrade_ansible_with_EM>`
- (https://wiki.onap.org/pages/viewpage.action?pageId=64007357)
-* `Using Netconf/Yang interface with EM <docs_5G_PNF_Software_Upgrade_netconf_with_EM.html>`_
+* `Using Netconf/Yang interface with EM <docs_5G_PNF_Software_Upgrade_netconf_with_EM>`
- (https://wiki.onap.org/pages/viewpage.action?pageId=64008675)
The Integration project is in charge of:
- Providing testing environment and support for the release use cases
-- Executing Cross-project Continuous System Integration Testing (CSIT)
+- Executing project-specific Continuous System Integration Testing (CSIT)
- Managing full ONAP CI chains (daily master, staging, stable) to ensure the
stability of the integration
- Developing and performing tests within full ONAP context (healthcheck, End to
- Use-case documentation and artifacts
- a testsuite docker included in ONAP cluster to execute the tests
- baseline JAVA and Python images, as well as a docker managing Java libraries
-- Configuration fiales and Heat templates to simplify the creation of the virtual
- ressources needed for the ONAP deployment and the use cases.
+- Configuration files and Heat templates to simplify the creation of the virtual
+ resources needed for the ONAP deployment and the use cases.
The integration team manages several official ONAP repositories: