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 2 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

Communication to register DR Node & BC

DR node reg with BC client? - Hook is in place, values need to pass still to be determined

post install hooks, flag can be added to keep alive (if post install jobs are completed they are deleted, flag is to allow them to not be deleted)

04/24: potentially call meeting next week with Jack Lucas, when we have resolved RC0 issues

05/01: Demo done at DCAE meeting - link to be added

Jack is currently on holidays (return date - 5/5) , can we use same logic as demoed?

Wednesday meeting(5/8) to discuss this in greater detail?

5/8: Meeting with Jack postponed to 5/15

5/13: Jack not available on 5/15. Dom to meet with Jack on 5/14 to have initial discussion.

Reference wiki page: DMaaP Edge Deployment

5/15: Dom spoke with Jack. wiki page above updated. Review today.

5/22: Jira tickets for El Alto already created. Need little bit redesign and more discussion with the OOM team.

5/29: Continuation with POC.

6/5: Mike Elliott will be scheduling a meeting to further discuss. Fiachra trying core-dns plugin with rke.

6/19: had meeting with MIke Elliot before DDF. Not much progress.. reviewed what's in progress.

07/17: OOM plan to finalise decision on Ingress controller soon. OOM-1993 - Getting issue details... STATUS

Likely they are going with Istio + nginx Ingress Controller.

This should allow Service Mesh config https://itnext.io/istio-service-mesh-the-step-by-step-guide-adf6da18bb9a which will potentially help with multi-(site/cluster) deployment.

08/07: Jira for Ingress Controller testing created -  DMAAP-1268 - Getting issue details... STATUS


2
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

3
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

4
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)

5
OpenMR11/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


Closed Items:

RefBlocking?StatusComponentDescription/Notes


Other Notes:

  • No labels