Page Comparison

Ref

Status

Description/Notes

1

Closed

Any additional documentation that can help?

Dom has identified some internal AT&T deployment docs but needs to scrub them before releasing.

Dom distributed 2 docs on installation and configuration

2

Closed

Identification of committers for relevant ONAP projects. Need to identify committer per gerrit repo:

dmaap/datarouter: Ram Koya

integration: Gary Wu

ci-management: Jessica Wagontall

oom: Borislav Glozman, Michael O'Brien, Mike Elliot

Closed

Need to review ONAP milestones – highlight high risk items.

7/25: might need a level of discretion / exemption required for what we submit on next milestone this week(M3). Ram: Is there a way to limit the functional commitment of DR to just what is needed for RAN Use Cases? e.g. existing code base, single Node, existing pub/sub API, simplest pub and sub routing path, no heat template for Itegration-Stable

Review RAN Use Case and identify DR features which will be exercised, then focus all efforts on this. Leah will follow up with RAN team to identify Use Cases.

7/26: reviewed RAN Use Case and confirmed DR functionality is adequate. And may have clarified even more function to exclude from code coverage.

4

Closed

Tie into CI process.  JJB templates.  What is repo?  What are good examples?

7/24: Sunil shared existing JJB templates

7/25: Dom provided overview of CSIT process

5

Open

Automated testing framework.  Show some examples/repos.

1. Integration test team using ONAP test framework (aka CSIT). See item 4. Closed.
2. Unit test  (aka Code Coverage). See item 12 details
3. OOM healthcheck. ...leave till OOM work. Part of DMAAP-107. healthcheck is NOT in the Helm chart - Sunil to send link with info
   8/10: Sunil shared email from Roger Maitland (Subject: DMaaP Message Router Health Check). Very good explanation that should be captured on the wiki someplace.

6

Closed

Different from AAI DR?

Yes, aai/datarouter seems to be a service that listens to some Message Router topic for certain events for the purpose of discovery.

7

Closed

Introduce ONAP required documentation.  Architecture, APIs, etc.

7/25: need to assign JIRA tickets

7/26: Brian needs to enumerate what documentation is really needed

7/27: Conner provided a list of documentation requirements which will be added to Jira

7/24: Ronan asks:

We have started looking into Jenkins Job Builder.

-          We have started with the Using Standard Jenkins Job (JJB) Templates page – is this the best place to start? A: Yes, but also look to existing project templates as working examples.

-          Do you have any sample template files that we could start with? A: Yes, Sunil to share. Sent.

-          Will we need access to run jobs in https://jenkins.onap.org/ ? A: No. The commit of the template into the ci-management/jjb repo is sufficient to run the job.

Be sure not to introduce any OpenSource security vulnerabilities. DR code has not been scanned yet. Expectation is that mySQL driver has some known vulnerability. Other projects have switched to PostgreSQL, or may need to claim an exception. Strategy: get a version committed ASAP so scan gets done.

7/26: get a container up and running and committed so we get a scan. Using 3/23 scan results, found few violations - Dom to send that report. Also mysql issues were NOT severe (red).

7/27: known vulnerability: new version of com.thoughtworks.xstream. Also, mySQL has a license violation, so may need to use mariadb

8/2: See Section 4, in blocking issues

8/7: code changes in progress, but still can't see because of blocking issue #4

8/8: DMAAP-557 has fixes

8/9: complicated by Jetty 9 API changes. But mySQL and xstream changes are finished.

Do we need to amend the M1 checklist to include DR? Or do we want to get a bit more confidence?

Is there risk for NOT amending the checklist? Anne notes that Functionality Freeze is 7/26 anyway, so maybe that is the place to re-introduce DR.

Anne to review with Ram.

7/30: Moot point now!

Fiachra requests help with code testing error resolution. Dom to meet to review who to contact next.

7/26: Fiachra demonstrated unit testing progress against DR in docker containers. Many tests (of provisioning API) are failing with 403. Attempts to manually configure for proper authorization were not successful. Also, test code seems to be missing a critical tests.properties file. Fiachra took a good stab at creating this, but uncertain if we are missing any assumptions. Dom to investigate further, and request help from prior DR contributors.

7/27: Progress! only 11 of 96 tests failing. Still concerned that code coverage metric seems not to reflect properly after these tests are run (i.e. under 5%). Will continue on current path but may need to adjust methodology.

7/30: existing tests are functional (tests the API entry points), and assume server is running in a sep container, so doesn't match the code coverage methodology. Will be a major work item. Sunil shared MR pom settings:

<jacoco.version>0.7.7.201606060606</jacoco.version> <sonar-jacoco-listeners.version>3.2</sonar-jacoco-listeners.version> <sonar.core.codeCoveragePlugin>jacoco</sonar.core.codeCoveragePlugin> <!-- Default Sonar configuration --> <sonar.jacoco.reportPath>target/code-coverage/jacoco-ut.exec</sonar.jacoco.reportPath> <sonar.jacoco.itReportPath>target/code-coverage/jacoco-it.exec</sonar.jacoco.itReportPath> <!-- Note: This list should match jacoco-maven-plugin's exclusion list below --> <sonar.exclusions>**/gen/**,**/generated-sources/**,**/yang-gen**,**/pax/**</sonar.exclusions> <sitePath>/content/sites/site/org/onap/dmaap/messagerouter/msgrtr/${project.artifactId}/${project.version}</sitePath>

7/31: will need to mock api for unit test coverage

8/2 : No change in status, mocking API the process to increase code coverage

8/7: getting tips from test team, expects 50% to be achievable.

8/8: Target is 8/15

8/15: Sonar is not picking up code coverage (missing pom entry). Prov at 8% (Feed Servlet 95%. Subscribe Servlet 70%.) Node not started.

Desire to sync with Anne about JIRA management.

7/30: need to wait for assignment of new PM

08/01: I created the next two sprints (Leah/Ericsson) so we should be able to populate DMAAP 2018-11 now, also contacted RAM about getting admin access to update the quick filters.

08/02: New sprint created - need to ensure that we also handle Casablanca Release Platform Maturity requirements

Keep this line in Copyright section of code?

ECOMP is a trademark and service mark of AT&T Intellectual Property.

A: Yes, please.

Problem with jenkins job creating docker container.

7/31: successfully building images locally. turn on boolean for push during jenkins build

8/2 : troubleshooting ongoing - expect resolution shortly

8/7: image on nexus3! seeing both SNAPSHOT and finished image, but Sunil says that is correct.

OOM updates. App team makes delivery to oom project. No special approval, but nice to let them know.

OOM NodePort List

NOTE: port reservation coordination recorded on wiki page....a good item to discuss with oom team

8/2: 2 ports reserved, a good starting place, may need a third?

Acquire original DR Prov DDL scripts.

8/3: provided by Dom

Backlog grooming. Fortress to review list and bring up anything needing discussion.

8/9: cover in JIRA discussion

Ronan:

1. Q on DMAAP-51 re docker tagging. necessary? A: Sunil: not used yet. But suggestion for creating separate jjb file for docker. see email in onap-discuss from a few weeks ago
2. See released version in Nexus3? A: Sunil advises to see if they are released by 8/9. in POM use version-SNAPSHOT. When satisfied, enter LF Ticket to release docker image. If not, then enter LF ticket.

8/9: Sunil: jar in staging until the end, then released. To release, send email to LF w/ CC to Ram for approval. Be sure image works with integration tests because tests will be repeated every day.

CSIT testing: publish feed request gets redirected and auth header gets stripped.

Workarounds: publish directly to Node. Sleep before publish to allow for provisioning propagation delay.

Fortress demo of DR to RAN collector possible for this week.

8/9: probably next week. NOTE: Dom unavail on 8/20 and 8/21.

813: no reply from client group....so close till they are ready

Nobody on Dmaap team has JIRA Admin access. Gildas is on vac. Mail sent to Ram for privileges.

8/13: will provide details for filters. Ram will get that implemented in Jira. Sunil now has admin access

8/15: Rachel has admin access too

CSIT tests failing.

/setup.sh: line 16: /usr/local/bin/docker-compose: Permission denied

Sunil suggests Conor send request to helpdesk@onap.org for inquiry.

8/13: Jessica will investigate, but it cleared up in the meantime.

M3 Readiness includes API review with Arch team. Sunil opinion: Arch will request review if needed. But DR is not really new so no email necessary.

8/15: Ram: "I don’t think we need to review as its an existing component."

If DR is not supporting heat deployment, do we need a waiver of some sort? Sunil: bring up in next TSC review for official decision. Look for advice for Ram on wed.

8/15: Ram: "Should we check with deployment team if they still insist us to create heat-style deployment?" Sunil: Project is Gildas, Integration is ???

Target next thurs TSC mtg where they review M3 checklist (last thursday of release cycle)

https://wiki.onap.org/display/DW/CII+Badging+Program 98% for Beijing

Reviewed feed provisioning and publishing sequence with Team Frontrunner (RAN File Collector).  Initially, will assume static pre-provisioned single feed that Frontrunner can assume will exist in ONAP. Later phase would support dynamic provisioning of feed via Buscontroller, but we need all the pieces (AAF, certs, DR) in place to demonstrate how to do this, so we don't want it to block Frontrunner.

Henry to provide Name, Description, publisher credentials for the static provisioning.

Emmett asks “Release Planning Platform Maturity Table” due date? 

Release Planning Template was due 6/28/2018  but that seems to be a different definition.

There are Platform Maturity Requirements (S3P)  with Casablanca specifics  but no date.