****** Note: this Use case has been moved to the future release *****
Use Case Overview & Description
(description of U/C)
Use Case Key Information
| 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. | Orchestration Scenarios |
BUSINESS DRIVER
...
Onboard ETSI SOL004 compliant VNF/CNF packages with large size software/container image files
Executive Summary -
...
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 methodology.
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.
...
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 | victor gao (Old) → Former user (Deleted) (New) | ||||||||||||||
| CDS |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
USE CASE DIAGRAM
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
- Risk:
- After we have altered the CSAR, the original CSAR protection (as per option1 or 2 of SOL004) is no longer reliable
- Since Release 3, it is mandatory to add individual signatures of every file in the package. It is mandatory to add individual signatures of every file in the package.
- This will allow still to verify the integrity of each file during its complete life cycle, i.e., also after onboarding.
- The fact that the VNF package is immutable is one of the sacred principles. It is the contract between the VNF vendor and the Service Provider.
- Risk:
...
- Once it is onboarded, SDC needs to verify the integrity with the original protection provided in the CSAR.
- In that case, the stored CSAR in the ETSI Catalog Manager is not the original vendor package
- 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 | ||||||
|---|---|---|---|---|---|---|
|
Use Case Functional Definitions
Use Case Title | Title of the Use Case |
Actors (and System Components) | The list of Actors and System Components that participate in the Use Case |
Description | Short overview of the Use Case |
Points of Contact | Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors. |
Preconditions | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed |
Triggers / Begins when | Describes the trigger for beginning the Use Case |
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced |
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced |
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case |
Related Use Cases | List of the Use Cases referenced by this Use Case |
Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |