Skip to end of metadata
Go to start of metadata

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, 2, x)

RC Release Candidate Milestone overview is available in wiki.


Usage

  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 "Done" in Jira?No

Link to JIRA

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-146


T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh



Have all findings from previous milestones been addressed?Yes

Provide link to JIRA findings

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-146


DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?Yes, moved to Cassablanca

Provide link to JIRA issue (type bug) of priority Highest and High. 

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh


Are all JIRA issues used as a reference in a commit in status "Done" 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.Nohttps://gerrit.onap.org/r/#/q/status:open+project:+logging-analytics
Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Provide link to "Merge job" as evidence in Jenkins project tab

#6 in

https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-master-merge-java/


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

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

N/Ano artifacts beyond the python and java lib jarsRefer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?N/A

Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green"

CSIT in progress LOG-245 - Getting issue details... STATUS


Is there a Docker images available for each repository?N/A

Provide link to evidence

No docker images for logging required


Has the project code successfully passed the Daily Build process?Yes

passing

https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-master-merge-java/

not passing because we don't have a test docker yet until casablanca

https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-master-docker-version-java-daily/


still doing csit and code coverage – having issues with the combined python and java in the same repo for the sonar job – it is skipping the project containing my junits – would be better if I had separate java/python repo

Issues being worked out below

https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/logging-analytics-sonar/76

Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the OOM deployment passed?No

Ensure in Jenkins External Labs all Health Check pass.

OOM-914 - Getting issue details... STATUS

http://jenkins.onap.info/job/oom-cd-master2-aws/55/console

13:30:58 onap          dev-log-elasticsearch-66cdc4f855-qz9bz         1/1       Running             0          1h
13:30:58 onap          dev-log-kibana-567557fb9d-pnfvz                1/1       Running             0          1h
13:30:58 onap          dev-log-logstash-fcc7d68bd-jws5c               1/1       Running             0          1h

deployment running - HC passes

13:40:37 Basic Log Elasticsearch Health Check                                  | PASS |
13:40:37 ------------------------------------------------------------------------------
13:40:37 Basic Log Kibana Health Check                                         | PASS |
13:40:37 ------------------------------------------------------------------------------
13:40:37 Basic Log Logstash Health Check                                       | PASS |



Has the Heat deployment passed?

N/A

(no ELK stack in heat)

Ensure in Jenkins External Labs all Health Check pass.

Logging is not in HEAT - design decision in Amsterdam - would need a filebeat docker in all the VMs


Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?


N/A

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?

Yes

For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?

N/A

For RC2, has the Documentation Team provided the final approval for your project documentation?N/A