Hi Mander, Removing HTTP ClusterIP port (3904) has impact for multiple DCAE component (possibly there are other ONAP components impacted). As we are well passed Frankfurt M1 and heading toward M2/M3, this change should not be added into Frankfurt scope now; please defer this for Guilin release.
I'm fine though with nodeport (30227) being disabled; if no concerns from other teams this could be targeted for Frankfurt. Regards, Vijay. From: [email protected] <[email protected]> On Behalf Of SAWANT, MANDAR Sent: Tuesday, December 10, 2019 4:41 PM To: '[email protected]' <[email protected]> Subject: [onap-discuss] DMaaP HTTP port will be disabled 1/10/2020 ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. ONAP projects using HTTP port to connect to DMaaP Message Router (MR), please start using HTTPS port as soon as possible. We will disable the HTTP port on 1/10./2020. This should give enough time to update your configuration to use port 3905 and validate. HTTP Ports Port: 3904, Nodeport: 30227 HTTPS Ports Port: 3905, Nodeport: 30226 Thanks, Mandar Sawant DMaaP PTL AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19661): https://lists.onap.org/g/onap-discuss/message/19661 Mute This Topic: https://lists.onap.org/mt/68005357/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
