...
This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)
RC Release Candidate Milestone overview is available in wiki.
in edit 20190430:1700-2100 EDT
Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes | Link to JIRA https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-146 | ||||||||||||||||||
Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings | |||||||||||||||||||
Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | Yes | Provide link to JIRA issue (type bug) of priority Highest and High. | new SO JIRA for filebeat - helping SO team
| |||||||||||||||||
Are all JIRA issues used as a reference in a commit in status "Closed" in Jira? | Yes | Note about the reverse - there are JIRAs in other projects that are closed but the code is still in review (not submitted) - internal poc worked but ONAP is not finished | 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 | https://gerrit.onap.org/r/#/q/status:open+logging | |||||||||||||||||||
Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | Provide link to "Merge job" as evidence in Jenkins project tab all merge, docker, verify jobs passing | in progress (fixing license issue first) working | ||||||||||||||||||
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 | |||||||||||||||||||
Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | No | Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green". See use cases | ||||||||||||||||||
At RC0, has the Pair Wise testing table been filled out? | PartialIn progress | Logging Pair Wise Testing for Dublin Release see attached results in via 244g server http://cd.onap.info
currently blocked only by a couple failed helm deployments | |||||||||||||||||||
At RC0, have all OOM Release HealtcheckHealthcheck related to your project passed? | Yes20181011:1000 status | - OK results below are intermittent - use my own deployment after for OK results jenkinsonapci. onap.infoorg/ job/oom-cd-master/3749/consolehttp://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS http://jenkins.onap.info/job/oom-cd-master/3704/console grafana/d/8cGRqBOmz/daily-summary?orgId=1 Basic Log Elasticsearch Health Check | PASS |
16:27:12
------------------------------------------------------------------------------
16:27:12
Basic Log Kibana Health Check | PASS |
16:27:12
------------------------------------------------------------------------------
16:27:12
Basic Log Logstash Health Check | PASS | 16:27:15
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Basic Pomba AAI-context-builder Health Check | PASS |
16:27:15
------------------------------------------------------------------------------
16:27:15
Basic Pomba SDC-context-builder Health Check | PASS |
16:27:16
------------------------------------------------------------------------------
16:27:16
Basic Pomba Network-discovery-context-builder Health Check | PASS |
------------------------------------------------------------------------------
Basic Pomba Service-Decomposition Health Check | PASS |
------------------------------------------------------------------------------
Basic Pomba Network-Discovery-MicroService Health Check | PASS |
------------------------------------------------------------------------------
Basic Pomba Pomba-Kibana Health Check | PASS |
------------------------------------------------------------------------------
Basic Pomba Elastic-Search Health Check | PASS |
------------------------------------------------------------------------------
Basic Pomba Sdnc-Context-Builder Health Check | PASS |
------------------------------------------------------------------------------
Basic Pomba Context-Aggregator Health Check | PASS |
------------------------------------------------------------------------------ | |||||||||||||||||||
At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository? | Yes | Provide link to evidence pomba https://nexus3.onap.org/#browse/search=keyword%3Dpomba logging-analytics (no dockers) | |||||||||||||||||||
Has the project code successfully passed the Daily Build process? | Yes | except for the release/docker jobs pending release | Goal is to ensure the latest project commit has not broken the Integration Daily Build | ||||||||||||||||||
Has the OOM deployment passed? | Yes | Ensure in Jenkins External Labs all Health Check pass. yes see hourly build in http://jenkins.onap.info/job/oom-cd-master/3641/console and http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS | Has the Heat deployment passed? (not a gating item for Casablanca) | N/A | Ensure in Jenkins External Labs all Health Check pass. pomba, clamp and logging are not in heat | daily build | |||||||||||||||
Documentation | For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? | /wiki/spaces/SV/pages/16089191 spring 4.x is insecure - first version that is ok is 5.0.5 - issue is it requires a retrofit of all my libraries including jax-rs 5.0.5 No | pending https://gerritonap.onapreadthedocs.orgio/ren/#latest/ctemplates/70161/1 - increased 4,2 to 8,55.0.9 sections/logging.html https://gerritonap.onapreadthedocs.orgio/ren/#latest/ctemplates/70188/ decreased 8,5 to 7,3sections/logging.html | Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed. Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK | |||||||||||||||||
For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team? Jira Legacy | | ||||||||||||||||||||
server | System Jira | ||||||||||||||||||||
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | LOG-463|||||||||||||||||||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | |||||||||||||||||||||
For RC2, has the Documentation Team provided the final approval for your project documentation? |
...