Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Purpose

Frequent meetings for ONAP El Alto Release contributors to discuss scope, requirements and development progress on DMaaP.

Logistics

Community Meetings & Calendar - See for further details


Wed 9am EST: DR working session & DMaaP status meeting

Connection Details:

#dmaap No.2

Join from PC, Mac, Linux, iOS or Android https://zoom.us/j/987639384
One tap mobile +16699006833,,987639384# US (San Jose) +16465588656,,987639384# US (New York) 

Dial by your location         +1 669 900 6833 US (San Jose)         +1 646 558 8656 US (New York)         +1 855 880 1246 US Toll-free         +1 877 369 0926 US Toll-free Meeting ID: 987 639 384

Find your local number: https://zoom.us/u/aepvj958Jh


DMaaP Working Session Agenda

  • Blocking Issue (status, new?)
  • Open Issue (status, new?)
  • Project Management - Jira-based discussion of status

Issue Tracker

Open Items:

RefBlocking?StatusComponentDescription/Notes
1
OpenAll

07/17: OOM are proposing a global AAF flag OOM-1986 - Getting issue details... STATUS which we discussed previously. Will potentially need to align existing patch with their proposal.

09/25: this is tied with the HTTP disabling item below. The HTTPS-only exposure will be pursued in Frankfurt release

12/3: Mandar to send an email to onap-discuss indicating the plan to switch to HTTPS port and clients to update their configuration accordingly.

2
OpenAll

08/28: Disable HTTP port altogether and only provide HTTPS endpoints for all the containers.

Dependency on AAF cert based auth and how it will be mitigated.

09/25: This effort for HTTPS-only will be pursued in Frankfurt

11/20: double check with SECCOM if HTTP needs to be completely removed or can be available using a flag for lower environments like dev - Mandar to check

12/3: Mandar to send an email to onap-discuss indicating the plan to switch to HTTPS port and clients to update their configuration accordingly.

3
OpenAll

11/6: Java 11 upgrade discussion. Individual components will try this out and see what issues they run into.

11/7: DR (Fiachra) tried and is seeing mostly working good for the core code, but running into issues with Mockito. Will continue investigation.

11/13: waiting on the SECCOM recommendation to finalize the Java version to be used (12/13)

11/27: Waiting on SECCOM to release the custom image using Alpine and Java 11.

12/3: Still waiting on image from SECCOM

12/6:  meanwhile, I needed a Jira so I created Epic  DMAAP-1359 - Getting issue details... STATUS  Please create any tasks under this. -Dom

5
OpenAll

11/18 - Helm charts migration to individual projects work has resumed. DMaaP is in the list of projects being worked on currently.  OOM-1249 is the corresponding ticket. 

11/27 - Helm chart templates from OOM team does not seem to be available yet.

12/3 - waiting on OOM team to complete the templates.


Closed Items:

RefBlocking?StatusComponentDescription/Notes
4
ClosedMR

11/6: dmaap-kafka coverage seems to have dropped below 55% at 52.5%. Need to bring it up to at least 55% to meet Frankfurt target

11/27: This is completed. Coverage for dmaap-kafka is now over 60%


Other Notes:

  • No labels