| Requirement | Details | Sponsor | Priority | Target Release | Remark | Resolution | Jira (if applicable) |
|---|---|---|---|---|---|---|---|
| Dynamic Orchestration | SO Should be able to on-board a recipe (BPMN+ supported code) without the need to restart the pods. | Huawei Ericcson | Med | Jakarta | |||
| Recursive Orchestration in SO Macro flow | Macro flow should support the customer facing services that are composed of other network services by design. | Tech Mahindra | High | Bell Canada has a prototype to refer to, need further discussion | SO-3809 | ||
| VNF LCM / Modify the existing service | SO should be add/ delete new VNFs to an existing service through the Macro flow | Bell Canada | High | Jakarta | |||
| Documentation Improvements | Improve the current ReadtheDocs of SO and furnish further details on the usage of SO and its functionalities APIs, code flows, features, known issues. | Med | Should be an on-going activity for every release. | ||||
| Review the timeout | Timeout in the BPMNs interacting with external modules (SDNC, AAI, OOF, CDS, OpPenstack ....) | Low | |||||
| Camunda DB (MariaDB) interactions | Camunda DB has too many operations performed that increases the load on the SO overall progress, this needs to be tested with the latest patch in the performance testing env. | Bell Canada Orange Huawei | Med | On-going | |||
| Timeout with CDS | the issue with the GRPC API that is being used is sync in nature and this is causing the issue with the BPMN 15 min timout, need to change the API to async. | Bell Canada | Low | WIP | |||
CSIT and verify build improvement
| Multi VNF support usecase | usecase to test the scenario of multi VNFs as part of the AT (Robo ) Test | Bell Canada | Med | ||||
| 5G slicing based verification | Automating the test cases and adding them to the verify jobs for testing the flows in SO | Wipro | Med | ||||
5G slicing enhancements
| Requirement | Details | Sponsor | Priority | Target Release | Remark | Resolution | Jira (if applicable) |
|---|---|---|---|---|---|---|---|
Core, RAN Endpoints dynamic discovery at NSMF | Currently, dummy endpoints are used for AN and CN domains. Actual endpoints will be discovered and used as an input to TN NSSMF | Wipro | Jakarta | ||||
| TN NSSMF modelling enhancements | Model enhancements according to IETF latest specification | Huawei | Jakarta | ||||
| OOF involvement in TN NSSMF | Use of Optimization solution in allocateNSSI, deallocateNSSI in TN NSSMF | Wipro | Jakarta | ||||
| Enhancements/Bug fixes | Bug fixes/enhancements due to carry-over test cases from Istanbul release | Wipro | Jakarta |
CNFO Enhancements
| Requirement | Details | Sponsor | Priority | Target Release | Remark | Resolution | Jira (if applicable) |
|---|---|---|---|---|---|---|---|
| AAI-offline synchronization of k8s-resources | The purpose is to synchronize data between AAIand k8s cluster after the creation of CNF in order to keep the consistency of the information in AAI | Samsung Orange | |||||
| CNF in-place upgrade | The purpose is to trigger an update of the existing CNF vf-modules belonging to the CNF in order to invoke upgrade operation on the k8s cluster. It should be an alternative to the build-and-replace approach (Create new CNF - delete old CNF). In a result cnf-adapter should trigger in k8splugin helm upgrade alike operation | Tech Mahindra Orange Samsung |