-
Epic
-
Resolution: Unresolved
-
High
-
None
-
None
-
ONAP Requirements Template
-
4
Before editing please read instructions here.
Description of Use Case / Requirement:
Owners (one of these should be the Assignee - use @ notation):
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project (ONAP Component #1) IMPACT: TO/C
- Impact Type: TO/C (Test Only/Code)
- Company Engagement: xyz
- Resources: xyz (People)
- Support Status: S/P/N (Supported/Partially supported/Not supported)
- Non-Functional Requirement Support: REQ-xxx, REQ-yyy
Project (ONAP Component #2) IMPACT: TO/C
- Impact Type: TO/C (Test Only/Code)
- Company Engagement: xyz
- Resources: xyz (People)
- Support Status: S/P/N (Supported/Partially supported/Not supported)
- Non-Functional Requirement Support: REQ-xxx, REQ-yyy
Integration Leads (use @ notation):
- is cloned by
-
REQ-356 ONAP shall increase the number of security tests performed during integration testing
-
- In Progress
-
-
REQ-470 DCAE extension for collecting files from HTTP servers
-
- In Progress
-
-
REQ-1071 CPS Enhancements for Rel J
-
- In Progress
-
-
REQ-203 VSP Compliance and Verification Check feature Phase 2
-
- In Progress
-
-
REQ-219 Java 11 migration from v8
-
- In Progress
-
-
REQ-231 HTTPS communication vs. HTTP
-
- In Progress
-
-
REQ-239 Communication Matrix
-
- In Progress
-
-
REQ-243 Kubernetes secure configuration recommendation
-
- In Progress
-
-
REQ-251 Ingress controller
-
- In Progress
-
-
REQ-255 ISTIO POC – limited ONAP deployment scope
-
- In Progress
-
-
REQ-267 5G Run-Time Data Persistence (Runtime Config DB)
-
- In Progress
-
-
REQ-359 Container rootfs must be mounted readOnly
-
- To Do
-
-
REQ-363 ONAP components should be able to run without AAF and MSB
-
- To Do
-
-
REQ-379 ONAP projects must use only approved and verified base images for their containers
-
- To Do
-
-
REQ-387 NRM Configuration enhancements in Guilin
-
- To Do
-
-
REQ-392 ONAP Rel. G requirements
-
- To Do
-
-
REQ-399 ONAP Projects dealing with GUI must provide GUI test suites
-
- To Do
-
-
REQ-215 Containers configured per secure recommendation
-
- To Do
-
-
REQ-313 Support transport of bio-matter over 5G
-
- To Do
-
-
REQ-314 ONAP Support for 5G Cheese Slicing
-
- To Do
-
-
REQ-315 PNF Plug and Play
-
- To Do
-
-
REQ-316 Levitation Support via 5G
-
- To Do
-
-
REQ-317 My Use Case
-
- To Do
-
-
REQ-396 Clearly split ONAP code and use case code
-
- To Do
-
-
REQ-49 5G NRM Configuration Management with RESTFul protocol
-
- Done
-
-
REQ-53 Enhancement on PNF S/W Upgrade with EM with Ansible
-
- Done
-
-
REQ-84 PNF Software Upgrade using direct Netconf/Yang interface with PNF
-
- Done
-
-
REQ-88 Enable PNF software version at onboarding
-
- Done
-
-
REQ-92 LCM API Evolution
-
- Done
-
-
REQ-195 Distributed Analytics use case on K8S regions
-
- Done
-
-
REQ-328 CLONE - ONAP Requirements Template
-
- Done
-
-
REQ-349 Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage
-
- Done
-
-
REQ-350 Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site.
-
- Done
-
-
REQ-357 ONAP shall increase the number of Docker Benchmark tests
-
- Done
-
-
REQ-358 No root (superuser) access to database from application container
-
- Done
-
-
REQ-360 Application config should be fully prepared before starting the application container
-
- Done
-
-
REQ-361 Continue hardcoded passwords removal
-
- Done
-
-
REQ-364 Replace NodePorts with ingress controller as a default deployment option
-
- Done
-
-
REQ-373 ONAP must complete update of the Python language (from 2.7 -> 3.8)
-
- Done
-
-
REQ-385 IPv4/IPv6 dual stack support in ONAP (Guilin)
-
- Done
-
-
REQ-397 Define Robustness and stability metrics, traffic model & run stability CI chain
-
- Done
-
-
REQ-398 Deploy on demand ONAP through CI per use case
-
- Done
-
-
REQ-428 5G Service Modeling in R8 - Modeling Work
-
- Done
-
-
REQ-429 Use Case for ONAP-based SON for 5G networks
-
- Done
-
-
REQ-430 PNF Plug & Play in R8
-
- Done
-
-
REQ-431 CMPv2 enhancements in R8
-
- Done
-
-
REQ-440 E2E Network Slicing use case requirements for Honolulu release
-
- Done
-
-
REQ-479 DCAE Transformation to support Helm
-
- Done
-
-
REQ-716 Control Loop in TOSCA LCM
-
- Done
-
-
REQ-717 Network CM Proxy & Temporal DB
-
- Done
-
-
REQ-721 E2E Network Slicing use case enhancements for Istanbul release
-
- Done
-
-
REQ-723 CMPv2 enhancements in Istanbul release
-
- Done
-
-
REQ-946 Integration Test for CCVPN Istanbul Release
-
- Done
-
-
REQ-993 Create ASD onboarding package IM / DM
-
- Done
-
-
REQ-994 Control Loop in TOSCA LCM improvement
-
- Done
-
-
REQ-1044 Support delete in SDC
-
- Done
-
-
REQ-1076 CCVPN Jakarta Enhancements for Intent-based Cloud Leased Line and Closed-loop
-
- Done
-
-
REQ-1085 E2E Network Slicing use case enhancements for Jakarta release
-
- Done
-
-
REQ-1281 CPS Enhancements for Release K
-
- Done
-
-
REQ-13 Service Resolving feature
-
- Done
-
-
REQ-17 Third Party Operational Domain Manager
-
- Done
-
-
REQ-21 TOSCA Compliant Policies
-
- Done
-
-
REQ-25 Policy Update Notifications
-
- Done
-
-
REQ-29 CLAMP Deployment of Policies to PDP Groups
-
- Done
-
-
REQ-33 Integration of CDS as an Actor in Control Loops
-
- Done
-
-
REQ-60 Modeling: Network Slicing modeling
-
- Done
-
-
REQ-64 Portal Security Enhancements
-
- Done
-
-
REQ-68 Portal Technology Stack Upgrade and New reporting features
-
- Done
-
-
REQ-76 NETCONF/TLS Certificate Management
-
- Done
-
-
REQ-80 PM Dictionary Schema shall be updated to specify one measurement per YAML document.
-
- Done
-
-
REQ-96 PNF S/W Upgrade with Netconf/yang with EM
-
- Done
-
-
REQ-118 Licensing Management with ONAP and xNFs. Define license management principles wrt. the key use cases. This will evolve beyond 5G but may start as a 5G U/C.
-
- Done
-
-
REQ-129 PM Control Support
-
- Done
-
-
REQ-136 Secure communication between xNFs and ONAP in 5G Bulk PM
-
- Done
-
-
REQ-140 Create Client, Plugin using Client and mechanisms for using CMPv2 as a CA.
-
- Done
-
-
REQ-141 CCVPN-E-LINE Service over OTN NNI
-
- Done
-
-
REQ-145 Vertical Industry Oriented On-demand 5G Slice Service Use Case
-
- Done
-
-
REQ-146 Vertical Industry Oriented On-demand 5G Slice Service
-
- Done
-
-
REQ-150 Control Loop Tutorial Documentation
-
- Done
-
-
REQ-154 Enhancements to 5G OOF SON use case
-
- Done
-
-
REQ-158 E2E Network Slice orchestration in R6 Frankfurt
-
- Done
-
-
REQ-162 This epic covers the work to upgrade ONAP components from legacy Policy API to new Lifecycle API
-
- Done
-
-
REQ-166 Integrate Acumos with DCAE
-
- Done
-
-
REQ-174 Remove dependencies on Python2
-
- Done
-
-
REQ-207 Code coverage - project defined improvements
-
- Done
-
-
REQ-208 OVP Testing and Certification Support Within SDC
-
- Done
-
-
REQ-223 CII badging – meet targeted Silver and Gold requirements
-
- Done
-
-
REQ-227 Complete the OJSI backlog
-
- Done
-
-
REQ-235 Password removal from OOM HELM charts
-
- Done
-
-
REQ-259 Secure communication for 5G – AAF contribution – CMPv2 protocol trial usage
-
- Done
-
-
REQ-263 Perform Software Composition Analysis - Vulnerability tables
-
- Done
-
-
REQ-427 Configuration Persistence Service in R8
-
- Done
-
-
REQ-864 SDC Multi Model Support Istanbul
-
- Done
-
-
REQ-1206 DMaaP Enhancements for Release K
-
- Done
-
-
REQ-1268 CCVPN Kohn Enhancements for Intent-based Cloud Leased Line and Transport Slicing
-
- Done
-
-
REQ-1413 CCVPN Support for Cloud-Network Convergence in London Release
-
- Done
-