Versions Compared

Old Version 2

changes.mady.by.user Tao Shen

Saved on

compared with

New Version 3

changes.mady.by.user Tao Shen

Saved on

Key

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

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject= VFC AND issuetype = Epic AND fixVersion = "Beijing Release" usecaseui and issuetype in (epic)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject= VFC AND issuetype = Story AND fixVersion = "Beijing Release" usecaseui and issuetype in (story)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name

Deliverable Description

NS/VNF Scaling API

NS/VNF Scaling API to So/Policy/UUI

Optimized NS/LCM API

Provide the Optimized NS/LCM API/UUI

Indirect mode proxy

Provide Indirect mode proxy function

HPA feature parse

Provide HPA feature parse function

GVNFM with improvement function

Provide GVNFM which can used to support vFW/vLB use case

Source CodeSource code for all VF-C componentsMaven ArtifactsMaven Artifacts for all VF-C componentsDocker ContainersDocker container  associated with VF-C componetsDocumentationVF-C detailed documentation

Service LCM Portal

Providing GUI of service life cycle management

VNF Monitor Portal

Providing GUI for VNFs alarm and performance

VM Monitor Portal

Providing GUI for VMs alarm and performance

Sub-Components

List all sub-components part of this release.

Activities related to sub-components must be in sync with the overall release.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01Awaiting guidance from Benchmark subcommittee
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01We assume that integration team will do a 72 hour ONAP soak which includes VFUsecase-C.UI
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency12automated detection and recovery
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01

increase test coverage to 50%


  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability00(*)
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability01support ONAP standard logging.
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11onap.readthedocs.io
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation


API Incoming Dependencies

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.

...

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

Portal Platform APIAPI for integration of portal applications


Catalog API (SDC)

API to read the NS and VNF Catalog




Parser SO API(Modeling)

API for parsering TOSCA fileNS instantiation and termination




Micro-services bus API

API for registration and use of micro-services bus




Multi-vim DMaaP API

API to allocate resource to VIM

DCAE VES collector SB API

API to push vnf fcaps data to VES collectorfor VNFs/VMs fcaps data subscription




A&AI API

API to store for gettring inventory

API to get/store image

OOF API (TBD)API to get vnf placement

  • API Outgoing Dependencies

API this project is delivering to other projects.

...

API Name

...

API Description

...

API Definition Date

...

API Delivery date

...

API Definition link (i.e.swagger)

...

NSLCM API Definition

...

Network services lifecycle management APIs, including scaling API

...

Link toward the detailed API description

...

VNFM Driver API Definition

...

VNFM Driver component northbound APIs, including scaling API

...

  • Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

...

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.




VF-C APIAPI for NS instantiation and termination


API Outgoing Dependencies

None

Third Party Products Dependencies

None.

Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.


Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
To fill outTo fill out

Known Defects and Issues

Provide a link toward the list of all known project bugs.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject= VFC AND issuetype = Bug AND status in ("In Progress", "To Do") AND fixVersion = "Beijing Release" usecaseui and issuetype in (bug)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo 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.


Team Internal Milestone


This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

...

DateProjectDeliverable
To fill outTo fill outTo fill out


Documentation, Training


  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...