Versions Compared

Old Version 2

changes.mady.by.user Tao Shen

Saved on

compared with

New Version Current

changes.mady.by.user Tao Shen

Saved on

Key

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

DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass the Release Candidate Milestone.

This template must be filled out for every Release Candidate Milestone (RC0, 1

...

     VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS.

...

  • compliant with ETSI NFV MANO architecture,
  • providing resource orchestration and full life cycle management and FCAPS for NS,
  • providing standard south bound interface to VNFMs,
  • providing north bound interface to SO, to take part in fulfilling the orchestraion and operation of end2end service,
  • providing interface and work with DCAE and Policy for Close Loop Automation.

...

  • compliant with ETSI NFV MANO architecture 
  • providing full life cycle management and FCAPS for VNFs which do not require a vendor VNFM

...

, 2, x)

RC Release Candidate Milestone overview is available in wiki.


Info
titleUsage
  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)


Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Closed" in Jira?Yes

Usecase-UI Backlog


Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Closed" in Jira?YesUsecase-UI Backlog
Are all JIRA issues used as a reference in a commit in status "Closed" in Jira?Yes
Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful.
Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.No
Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2  AND is:mergeable age:1week
Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Usecase-UI Jenkins

https://jenkins.onap.org/view/Merge-Jobs/
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)Yes

Goal: 55% for Incubation project in the current release

Usecase-UI sonar data

Sonar

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

Has the team delivered all their release artifacts in Nexus Release repo?

There should be at least ONE version of each artifacts available in Nexus Release repo.

Yes
Refer to Independent Versioning and Release Process for procedure
Check the certification expiry of your application. It should be valid for the next 9 months after RC0.Yes

Integration and Testing


Have all CSIT Use Cases (created by each project team) passed?


It should include at least 1 CSIT that will be run on


Lab-xxx-OOM-Daily Jenkins Job

YesProvide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".
At RC0, has the Pair Wise testing table been filled out?Yes

Integration Weather Board for Dublin Release

UUI Pair Wise Testing for Dublin Release


At RC0, have all OOM Release Healtcheck related to your project passed?Yes

At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository?YesUUI Docker images
Has the project code successfully passed the Daily Build process?YesUsecase-UI JenkinsGoal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the OOM deployment passed?YesEnsure in Jenkins External Labs all Health Check pass.

Has the project passed the Integration Sanity Tests?

Yes

Integration sanity tests in Dublin Release cover:

  • ONAP deployment
  • All components health check
  • VNF onboarding and service creation for vFW use case
  • Model distribution for vFW
  • vFW instantiation
  • vFW closed loop
  • vFW deletion

No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1

No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues

Documentation

For RC0, does the project team has solved their JIRA Documentation Tickets?

If not, what are the risks?



JIRA Query (Bugs Only)

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels = Documentation OR project = Documentation) AND issuetype= Bug AND  fixversion = "Dublin Release" AND status != Closed ORDER BY issuetype DESC, fixVersion ASC, status DESC, priority DESC, updated DESC

For RC1, has the team addressed all the remaining Documentation JIRA tickets ?

JIRA Query

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC

For RC1, is the project prepared for the upcoming 'Ready to review'?

Documentation related patches should be reviewed by the documentation team to make sure everyone follows style guides.
For RC2, has the team addressed all the remaining Documentation JIRA tickets identified during the review?Yes


JIRA Query

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC

2.New component capabilities for Dublin, i.e. the functional enhancements

  1. Mysql DB migrates to OOM shared MariaDB Galera Cluster which can be used to meet S3P HA requirements.

    1. Update VF-C DB Helm Chart
    2. Update VF-C component to leverage new MariaDB Galera Cluster 
      1. Docker configuration update 
      2. DB script migrate 
      3. Other work 
  2. Configuration Improvement
    1. Investigate all VF-C configuration could be automatically injected through OOM.
  3. Data Persistence
    Add data persistent storage to avoid data loss due to pod restart

3.New or modified interfaces

Update VF-C Northbound APIs to align SOL005. 

Yes, almost APIs required parameters has been supported by previous version，the alignment will add more optional parameter support which can comply with previous APIs.

4.Interface naming

       VF-C supports the following APIs:

  1.  NSLCM APIs (Create/Instantiate/terminate/delete/scale/heal....), such as 

    api/nslcm/v1/ns
    api/nslcm/v1/ns/(?P<ns_instance_id>[0-9a-zA-Z_-]+)/instantiate
    api/nslcm/v1/subscriptions
    api/nslcm/v1/ns_lcm_op_occs

  2.   Package management APIs( VNF/PNF/NS package create/upload/delete/update ....), such as 
     api/vnfpkgm/v1/vnf_packages
     api/vnfpkgm/v1/subscriptions

5.Reference to the interfaces

No

6.Involved use cases, architectural capabilities or functional requirements

...

Use case support

  1. CCVPN 
  2. vCPE
  3. vFW

Functional Requirements support 

      a. Centralized Representation and Consistent ID of Cloud Regions

...

Listing of new or impacted models used by the project (for information only)

...