Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

RefBlocking?StatusComponentDescription/Notes
1Open
On HoldAll

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.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1993

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 - 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDMAAP-1268

11/06: This topic has been put on hold due to lack of activity from various teams. This will be resurrected once the topic gains more momentum.


5
OpenAll

07/17: OOM are proposing a global AAF flag

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1986
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

6
ClosedAll

SECCOM have requested that the PTL be added to all CII Badging pages. 

PTL added to all DMaaP project

7
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

...