Skip to end of metadata
Go to start of metadata


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.

in edit 20190430:1700-2100 EDT

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

Link to JIRA

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?Yes

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

new SO JIRA for filebeat - helping SO team

SO-1110 - Getting issue details... STATUS

Are all JIRA issues used as a reference in a commit in status "Closed" in Jira?YesNote 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 finishedVery 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
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)


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.


2 images already merged under - thanks Michael O'Brien

2 images pending merge on SDNC dependent changes - thanks Prudence Au

Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave 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 RC1, has the Pair Wise testing table been filled out?Yes

Logging Pair Wise Testing for Dublin Release

via 244g server

LOG-1041 - Getting issue details... STATUS

LOG-1033 - Getting issue details... STATUS

At RC1, have all OOM Release Healthcheck related to your project passed?Yes
results below are intermittent - use my own deployment after for OK results

and 20190505 manual deployment on a 256g Azure VM,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,31530707

Basic Log Elasticsearch Health Check                                  | PASS |
Basic Log Kibana Health Check                                         | PASS |
Basic Log Logstash Health Check                                       | PASS |
Basic Pomba AAI-context-builder Health Check                          | PASS |
Basic Pomba SDC-context-builder Health Check                          | PASS |
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 RC1, is there a Docker image in Nexus Docker-Release repo available for each repository?Yes

Provide link to evidence



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 daily build


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



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?


no - as above

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?