Template Cut & Paste for your Use Case/Requirement)
R9 PRESENTATION:
| ITEM | DETAILS |
|---|---|
| Presentation | |
| Recording mp4 | |
| Audio only |
Key Contacts - ("WHO")
Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Application Service Descriptor (ASD) onboarding package IM / DM
R9 PRESENTATION:
| ITEM | DETAILS |
|---|---|
| Presentation | |
| Recording mp4 | |
| Audio only |
Key Contacts Marian Darula , @Nguyenphu, Thinh, Byung-Woo Jun
Executive Summary -
In today, many complex applications are consisting in a mixed, complex workload, that is described in many Kubernetes resources, e.g. to be run on a certain cluster, etc. In order to deploy the application, the orchestration task would be requiring dealing with different abstract layers of resources, different templates system mapping, and application packaging. Another challenge is to keep up with changes in the cloud infrastructures features enhancement mapping into abstract resource template.
The proposal focuses on following main parts:
- Packaging, in a single, well defined bundle, cloud applications, to enable distribution, provisioning and installation.
- Application metadata and cloud-native tooling.
Leverages existing Kubernetes ecosystem and continuously growing set of extensions, plugins, and tools.
See Application Service Descriptor (ASD) and packaging Proposals for CNF for more details.
As a part of this requirement the definition of IM and DM for ASD shall be done.
Business Impact - Unified modelling and packaging of cloud native network functions (CNFs) relying on cloud native artefacts with simple descriptor additions. It will significantly simplify modelling and packaging of CNFs.
Business Markets - All operators and service providers that are using ONAP for CNF deployment.
Funding/Financial Impacts - Due to significant simplification of modelling and packaging of CNFs there will we OPEX cost savings.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)