| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | VID |
|---|---|
| Target Release Name | Dublin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Nokia |
...
What is this release trying to address?
- S3P improvements
- Adopt the ONAP format of ID when referring to a cloud region
- Initiate workflows designed in SDC (stretch goal)
- S3P improvements (stretch goal)
Use Cases
Will take part in following use-cases:
...
Change Management Dublin Extensions
- Stretch Goal, based on support of Nokia: Utilize SO as a repository of workflows, instead of VID's workflows' configuration
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VID and issuetype in (story) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
VID fit within the ONAP Archiecture diagram in the ONAP Architecture in the runtime block, highlighted below:
Block diagram showing relation with external components.
...
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.TBD
Platform Maturity
Referring to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
SO | ||||
| Workflows | Obtain the list of all available and certified Workflows (SO Native and User Designed) for the user selected vNF Type and the Meta Data for the Selected for Workflow | TBD | TBD | TBD |
| Instantiation | Enhancement: Instantiation API to be more flexible to consume workflow parameters | |||
| Manual Task | Get available manual tasks by request | Ready | ||
A&AI | ||||
| cloud-regions | Get cloud-owner by cloud-region ID /cloud-infrastructure/cloud-regions?cloud-region-id={id} | Ready |
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...