Versions Compared

Old Version 1

changes.mady.by.user Bharath Balasubramanian

Saved on

compared with

New Version 2

changes.mady.by.user Bharath Balasubramanian

Saved on

Key

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

...

425b2b0a-557c-3c0c-b515-579789cceedb

425b2b0a-557c-3c0c-b515-579789cceedb
Practice AreaCheckpointYes/NoEvidencesHow to?
SecurityHas the Release Security/Vulnerability table been updated in the  protected Security Vulnerabilities wiki space?YesTable in in the protected Security Vulnerabilities wiki space   corresponds to the latest NexusIQ scanPTL reviews the NexusIQ scans for their project repos and fills out the vulnerability review table
Has the project committed to enabling transport level encryption on all interfaces and the option to turn it off?Yes*

MUSIC Node-to-node encryption using SSL

  • This is a stretch goal in our release planning: OOF Dublin M1 Release Planning#Whatisthisreleasetryingtoaddress?
    • Jira stories have been created and tracked for this.
    Jira
    serverONAP JIRA
    jqlQuerytext ~ "encryption" and project = "Optimization Framework"
    counttrue
    serverIdRequirements and test cases for transport layer encryption have been   created for all interfaces not currently supporting encryption.
    Has the project documented all open port information?Yes
    		Update OOM NodePort List
    Has the project provided the communication policy to OOM and Integration?Yes
    		 Recommended Protocols
    Do you have a plan to address by M4 the Critical and High vulnerabilities in the third party libraries used within your project?Yes
    • Replace vulnerable packages
    • Document false positives in the release notes if it is not possible to replace the vulnerable packages
    • Document vulnerabilities inherited in dependencies: include the name of the dependency and any mitigations that can be implemented by an ONAP user
    • Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repository
    Architecture


    		Has the Project team reviewed the APIs with the Architecture Committee (ARC)?Yes

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyONAPARC-406

    MUSIC Dublin (R4) Architecture Alignment

    Architecture walk through to understand how each project contributes on Release Use Case. ARC to organize the walk through.

    Is there a plan to address the findings the API review?YesLink to planThe plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki.
    Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval?Yes
    		In the case some changes are necessary, bring the request to the TSC for review and approval.

    Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone?


    		If Yes, please a link to the evidence of these changes.Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes.
    Provide link to the API Documentation.Yes

    CMSO: CMSO API v1_v2, New CMSO APIs in Dublin

    HAS: OOF-HAS Homing Specification Guide, Traffic Distribution

    OSDF: API Specifications for OOF Applications

    FGPS: FGPS Dependencies and APIs


    https://gerrit.onap.org/r/#/c/31127/2/swagger.json



    Release ManagementAre committed Sprint Backlog Stories been marked as "Closed" in Jira board?Yes.


    Jira
    serverONAP JIRA
    jqlQueryproject = OPTFRA AND issuetype = Story AND status in (Delivered, Closed, Done) AND fixVersion in ("Dublin Release", "Casablanca Maintenance Release")
    counttrue
    serverId
    https://jira.onap.org/secure/RapidBoard.jspa?rapidView=113&view=planning&selectedIssue=MUSIC-45



    Are all tasks associated with Sprint Backlog Stories been marked as "Closed" in Jira?Yes


    JiraserverONAP JIRAjqlQueryproject = OPTFRA AND issuetype = Task AND status = Closed AND resolution = Done AND fixVersion in ("Dublin Release", "Casablanca Maintenance Release") counttrueserverId425b2b0a-557c-3c0c-b515-579789cceedb
    https://jira.onap.org/secure/RapidBoard.jspa?rapidView=113&view=planning&selectedIssue=MUSIC-45



    Have all findings from previous milestones been addressed?Yes

    OSDF code coverage has been bumped up to 65%

    HAS code coverage has been bumped up to 51%, will meet target 55% by M4.


    https://jira.onap.org/secure/RapidBoard.jspa?rapidView=113&view=planning&selectedIssue=MUSIC-45



    DevelopmentIs there any pending commit request older than 36 Business hours in Gerrit?No

    Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2  AND is:mergeable age:1week


    Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)NoYes

    56%

    OSDF: 65%

    HAS: 51%

    CMSO: Team is currently working towards this.

    Sonar

    Guidance on Code Coverage and Static Code Analysis

    Tools: Sonar

    Are all the Jenkins jobs successfully passed ( Merge-Jobs)?



    https://jenkins.onap.org/view/
    optf/job/optf-has-master-conductor-merge-java/

    https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/

    https://jenkins.onap.org/view/optf/job/optf-cmso-
    Merge-Jobs/job/music-master-merge-
    properties-
    java/


    https://jenkins.onap.org/view/Merge-Jobs/

    Are all binaries available in Nexus?Yes


    https://nexus.onap.org/
    content/groups/staging/org/onap/optf/
    #nexus-search;quick~music



    Integration and Testing


    Have 50% of System Integration Testing Use Cases been implemented successfully in Jenkins?

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

    Lab-xxx-OOM-Daily Jenkins Job

    Yes

    CSIT completed (18/18 tests)

    for the has been completed for CMSO, OSDF, HAS https://jenkins.onap.org/view/CSIT/job/music-master-csit-music-test-plan/


    OOM based CSIT is targeted for M4. Still awaiting instructions
    Has the project code successfully passed the Daily Build process?Yes
    Goal is to ensure the latest project commit has not broken the Integration Daily Build 

    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

    ModelingHas the Project team provided links to Data Models (e.g, JSON, YANG, Swagger, etc.) for all Shared Information (e.g., APIs, API Payload, Shared Design Model)?Yeshttps://gerrit.onap.org/r/#/c/31127/2/swagger.jsonIt is a non-blocking item for M3 - The Modeling team is gathering information

    ...