...
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | |||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation | |||||||||
| Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: Fernando Oliveira Byung-Woo Jun USE KEY CONTACTS: Fernando Oliveira Byung-Woo Jun | |||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
BUSINESS DRIVER
...
BUSINESS DRIVER
Onboard ETSI SOL004 compliant VNF/CNF packages with large size software/container image files
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").
Enable a vendor provided ETSI SOL004 compliant VNF package including large size Software/Container Image files
- Support for onboarding ETSI v3.3.1 SOL004 CSAR packages with large size software/container image files
Business Impact - Enables operators and service providers to design and onboard their CSAR files with large size software/container image files.
Business Markets - All operators that are currently using ETSI packages to deploy VNFs
Funding/Financial Impacts - Reduction in operations expense from using industry standard VNF packaging. Reduction in capital expense from vendors using a single packaging methodologyFunding/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 requirement 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)
Development Status
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||||||
| A&AI | |||||||||||||||
| AAF | |||||||||||||||
| APPC | |||||||||||||||
| CLAMP | |||||||||||||||
| CC-SDK | |||||||||||||||
| CPS | |||||||||||||||
| DCAE | |||||||||||||||
| DMaaP | Mandar Sawant (Old) → Fiachra Corcoran (New) | ||||||||||||||
| External API | |||||||||||||||
| HOLMES | |||||||||||||||
| MODELING | |||||||||||||||
Multi-VIM / Cloud | |||||||||||||||
| OOF | |||||||||||||||
| OOM | |||||||||||||||
| POLICY | |||||||||||||||
| PORTAL | |||||||||||||||
| SDN-C | |||||||||||||||
| SDC |
| ||||||||||||||
| SO | |||||||||||||||
| VID | |||||||||||||||
| VF-C | |||||||||||||||
| VNFRQTS | |||||||||||||||
| VNF-SDK | Weitao Gao (Old) → user-67d6f (New) | ||||||||||||||
| CDS |
...
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
- Operators or Service Providers onboard a vendor ETSI SOL004 compliant VNF/CNF package to SDC
- SDC detects the CSAR file embeds software/container images, instead of referencing the image files
- SDC extracts the embedded software/container images from the CSAR file and stores the images to the Image Registry
- SDC updates the CSAR file for referencing the image files
- CIR component provides Docker Registry APIs for the image file access (CRUDQ), by conforming to ETSI specifications
- CIR will be registered to AAI for ONAP runtime component to locate the proper CIR instance(s)
- CIR admin can upload the container image files to the Image Registry thru Docker Registry APIs
- K8S CIS can query for the container image files from CIR (It is allowed to use de Facto API standard)
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
...