...
ASD-based CNF Orchestration
| ITEM | DETAILS | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Presentation | ARCCOM:
| ||||||||
Recording MP4 | |||||||||
Audio Only |
...
Support ASD package runtime onboarding
- Support AS LCM RESTful protocol APIs
- Support ASD-based CNF orchestration operations, such as Create AS, Instantiate AS, Terminate AS and Delete AS (Upgrade AS as a stretch goal), providing:
- External K8s Clusters registration
- AS topology inventories
- Helm charts deployment to a selected K8s cluster
...
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
External secure communication only via Ingress
| ITEM | DETAILS | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Presentation |
ARCCOM presentation | ||||||||
Recording MP4 | |||||||||
Audio Only |
Executive Summary - When ONAP is deployed using Service Mesh (default: Istio) all internal communication between pods is secured by sidecars. If components expose there services outside ONAP (e.g User interfaces, APIs,...) they have to use the Ingress Gateway provided (here Istio-Ingress). A communication via NodePorts is not supported anymore.
...
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
|
Removal of AAF
| ITEM | DETAILS | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Presentation |
ARCCOM presentation | ||||||||
Recording MP4 | |||||||||
Audio Only |
Executive Summary - AAF is an unmaintained component used to create TLS certificates for ONAP services. When ONAP is deployed using Service Mesh (default: Istio) all internal communication between pods is secured by sidecars. Components just need to provide non-TLS interfaces.
Removal of the AAF component means:
- removal of AAF from the OOM helm charts
- ONAP Component Services must offer "plain" non-TLS interfaces
- ONAP Components must be able to uses not-TLS interfaces of other components
- (Optional) Code cleanup
- When AAF is not used anymore, all AAF related code can be removed
- All chart options related to AAF can be cleaned
Business Impact - Supports a cloud-native application deployment.
Business Markets -
Funding/Financial Impacts -
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
JIRA:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
All component must be able to run without MSB
| ITEM | DETAILS | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Presentation |
ARCCOM presentation | ||||||||
Recording MP4 | |||||||||
Audio Only |
Executive Summary - In the default ONAP deployment case using ServiceMesh, an Ingress Gatweay is used for external access to the services. Therefor the MSB component would not be needed and must be disabled. All components must be able to run without the usage of MSB.
Business Impact - Supports a cloud-native application deployment.
Business Markets -
Funding/Financial Impacts -
Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
JIRA:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|