Ramesh, Thanks for the update and the work guys– we now have 15 ports free in 302. AA&I can grab one of these https://lists.onap.org/g/onap-discuss/topic/spike_nodeportprefix/25502174?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,25502174
/michael From: PARTHASARATHY, RAMESH <rp6...@att.com> Sent: Monday, September 10, 2018 12:17 PM To: Mike Elliott <mike.elli...@amdocs.com>; FREEMAN, BRIAN D <bf1...@att.com>; Michael O'Brien <frank.obr...@amdocs.com>; Roger Maitland <roger.maitl...@amdocs.com>; HU, JUN NICOLAS <jh2...@att.com>; Seshu Kumar M <seshu.kuma...@huawei.com>; Marcus Williams <marcus.willi...@intel.com>; Gary Wu <gary.i...@huawei.com>; Borislav Glozman <borislav.gloz...@amdocs.com>; Mandeep Khinda <mandeep.khi...@amdocs.com> Cc: SMOKOWSKI, STEVEN <ss8...@att.com> Subject: RE: Change in oom[master]: helm chart for so containers Hi Mike, I had a brief exchange with Steve and he confirmed that we don’t need any other nodeport other than apih (30277). I have updated ONAP wiki https://wiki.onap.org/display/DW/OOM+NodePort+List to treat 30222->30225 as FREE_PORT. Thanks Ramesh From: Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>> Sent: Friday, September 07, 2018 11:34 AM To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; PARTHASARATHY, RAMESH <rp6...@att.com<mailto:rp6...@att.com>>; OBRIEN, FRANK MICHAEL <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; Roger Maitland <roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>; HU, JUN NICOLAS <jh2...@att.com<mailto:jh2...@att.com>>; Seshu Kumar M <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>; Marcus Williams <marcus.willi...@intel.com<mailto:marcus.willi...@intel.com>>; Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>> Cc: SMOKOWSKI, STEVEN <ss8...@att.com<mailto:ss8...@att.com>> Subject: Re: Change in oom[master]: helm chart for so containers Hey Ramesh, I agree with Brian’s comments, you only need to expose 30277 as a NodePort, and all other communication by SO components should use internal ports. I also agree with your comments about the OOM NodePort List<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_OOM-2BNodePort-2BList&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=3fnjrSZEVI89I2Yvh2KSk-lAUJ-HV9J4Se0Bs1ugtXI&s=qOWrl4TIG0E_CC7nZqdlhEYvgTKO6xyc0TxKmPDcPEc&e=> not being clear. I have taken a stab at cleaning up the node port wiki page to make it easier to reserve and manage node ports. It is a work in progress, but please take a look and provide any feedback you may have. In the node port list, 30277 is reserved for SO already. But there is also a range between 30222->30225 that is currently reserved for SO. It sounds like, based on this conversation, that the of the page range is no longer required. If this is true can you please update the wiki (as per instructions at the top) and release them as FREE_PORTs so others may use them? Thanks, Mike. From: "FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>> Date: Friday, September 7, 2018 at 2:11 PM To: "PARTHASARATHY, RAMESH" <rp6...@att.com<mailto:rp6...@att.com>>, Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>, Roger Maitland <roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>, "HU, JUN NICOLAS" <jh2...@att.com<mailto:jh2...@att.com>>, Seshu Kumar M <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>, Marcus Williams <marcus.willi...@intel.com<mailto:marcus.willi...@intel.com>>, Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>, Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>, Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>, Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>> Cc: "SMOKOWSKI, STEVEN" <ss8...@att.com<mailto:ss8...@att.com>> Subject: RE: Change in oom[master]: helm chart for so containers Ramesh, Those are not the right cluster ports. You need to use the internal ports 8081 etc Only api-handler has to be reachable on 30277 the rest are internal and I found they had to be defined to match the port that the corresponding application was listening on to work. https://gerrit.onap.org/r/#/c/65071/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_65071_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=3fnjrSZEVI89I2Yvh2KSk-lAUJ-HV9J4Se0Bs1ugtXI&s=SFJMZLFUXMZk7o9HB__YAAcIcwO8mueEgSZ4Rm8m2wA&e=> Brian _____________________________________________ From: PARTHASARATHY, RAMESH Sent: Friday, September 07, 2018 1:49 PM To: OBRIEN, FRANK MICHAEL <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; Roger Maitland <roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>; HU, JUN NICOLAS <jh2...@att.com<mailto:jh2...@att.com>>; Seshu Kumar M <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>; Marcus Williams <marcus.willi...@intel.com<mailto:marcus.willi...@intel.com>>; Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>> Cc: SMOKOWSKI, STEVEN <ss8...@att.com<mailto:ss8...@att.com>> Subject: RE: Change in oom[master]: helm chart for so containers Hi Everyone, I realize that I have triggered this port conflict issue with SO containers. My sincere apologies about the overhead! When I look at Mike's updates at https://wiki.onap.org/display/DW/OOM+NodePort+List<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_OOM-2BNodePort-2BList&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=3fnjrSZEVI89I2Yvh2KSk-lAUJ-HV9J4Se0Bs1ugtXI&s=qOWrl4TIG0E_CC7nZqdlhEYvgTKO6xyc0TxKmPDcPEc&e=>, I understand about SO should use NodePort 30277 for its API Handler. However, I need someone to guide me about cluster ports which can be used by SO. Here is the current usage NAMESPACE NAME TYPE PORT(S) Remarks onap so NodePort 10100:30277/TCP It was 30258 before onap so-bpmn-infra ClusterIP 10200/TCP onap so-openstack-adapter ClusterIP 10300/TCP onap so-sdnc-adapter ClusterIP 10400/TCP onap so-sdc-controller ClusterIP 10500/TCP onap so-vfc-adapter ClusterIP 10600/TCP onap so-request-db-adapter ClusterIP 10700/TCP onap so-catalog-db-adapter ClusterIP 10800/TCP onap so-mariadb NodePort 3306:30252/TCP Can I assume that usage of these cluster ports (10100 – 10800) is Ok? This is not clear from https://wiki.onap.org/display/DW/OOM+NodePort+List<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_OOM-2BNodePort-2BList&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=3fnjrSZEVI89I2Yvh2KSk-lAUJ-HV9J4Se0Bs1ugtXI&s=qOWrl4TIG0E_CC7nZqdlhEYvgTKO6xyc0TxKmPDcPEc&e=> Please let me know. Thanks Ramesh -----Original Message----- From: Michael O'Brien (ONAP Code Review) <ger...@onap.org<mailto:ger...@onap.org>> Sent: Thursday, September 06, 2018 8:11 AM To: PARTHASARATHY, RAMESH <rp6...@att.com<mailto:rp6...@att.com>> Cc: Roger Maitland <roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>; HU, JUN NICOLAS <jh2...@att.com<mailto:jh2...@att.com>>; Seshu Kumar M <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>; Marcus Williams <marcus.willi...@intel.com<mailto:marcus.willi...@intel.com>>; Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; ONAP Jobbuilder <onap-jobbuil...@cloud.onap.org<mailto:onap-jobbuil...@cloud.onap.org>>; FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>> Subject: Change in oom[master]: helm chart for so containers Michael O'Brien has posted comments on this change. Change subject: helm chart for so containers ...................................................................... Patch Set 15: guys, I have the 304xx change - will post a fix when I finish testing it -- To view, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_59757&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=IcF9hyD-gHdHLhjDsytcg6bSqw4TdXAx6QhebidTsh0&s=ONV5HAHhv7AlIwmV5h27wl6Om3AqC9oxT3RzMR3kqvA&e= To unsubscribe, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_settings&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=IcF9hyD-gHdHLhjDsytcg6bSqw4TdXAx6QhebidTsh0&s=b-KREFLQhPYnquCRdun_-fd49MdAp6AuHq8vmi1VqpM&e= Gerrit-MessageType: comment Gerrit-Change-Id: I690430622ecbdcaf099a6165844142841db436dd Gerrit-PatchSet: 15 Gerrit-Project: oom Gerrit-Branch: master Gerrit-Owner: Ramesh Parthasarathy <rp6...@att.com<mailto:rp6...@att.com>> Gerrit-Reviewer: Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>> Gerrit-Reviewer: Brian Freeman <bf1...@att.com<mailto:bf1...@att.com>> Gerrit-Reviewer: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>> Gerrit-Reviewer: Jun (Nicolas) Hu <jh2...@att.com<mailto:jh2...@att.com>> Gerrit-Reviewer: Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>> Gerrit-Reviewer: Marcus Williams <marcus.willi...@intel.com<mailto:marcus.willi...@intel.com>> Gerrit-Reviewer: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> Gerrit-Reviewer: Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>> Gerrit-Reviewer: ONAP Jobbuilder <onap-jobbuil...@jenkins.onap.org<mailto:onap-jobbuil...@jenkins.onap.org>> Gerrit-Reviewer: Ramesh Parthasarathy <rp6...@att.com<mailto:rp6...@att.com>> Gerrit-Reviewer: Roger Maitland <roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>> Gerrit-Reviewer: Seshu Kumar M <seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>> Gerrit-HasComments: No This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=VXOes6JIP1tI2gldL30ehg&m=3fnjrSZEVI89I2Yvh2KSk-lAUJ-HV9J4Se0Bs1ugtXI&s=gIUyd7E5MSTrsh4vnEht9ztwhVXZl-3zsc9qvacGt5o&e=> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12341): https://lists.onap.org/g/onap-discuss/message/12341 Mute This Topic: https://lists.onap.org/mt/25503005/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
