Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2, Fulfill functional requirements:   Distributed Analytics as a Service (Dublin Summary) - Edge Automation,  K8S based Cloud Region Support,  Continuation of HPA (Dublin)

3, Expanding the infrastructure's support:  StarlingX, Lenovo ThinkCloud

...

5, Further integration with SO


Use Cases

CCVPN Use Case (Dublin)

vFW/vDNS

vCPE

Minimum Viable Product

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

...

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)

eventListener/v5VES collector event publish APIsN/A since It is ready nowN/A since It is ready nowhttps://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/1359970816242677/ves.html?version=1&modificationDate=1503378662000&api=v2



API Outgoing Dependencies

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...