Michael, Hi, an update: forgot to re-view the comments on the page after our update friday Mike updated the wiki on Friday after Mike, myself, James and Mandeep went through the list after the clamp, so fixes. You will see his update on the list https://lists.onap.org/g/onap-discuss/topic/oom_improved_oom_nodeport/25310021?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,25310021
You can take one of "FREE_PORT" 30239, 40, 45, 50, 61-66 Make sure to edit the wiki and reserve your port until we get a manifest and an postscript https://jira.onap.org/browse/OOM-1383 running after the helm verify job (until we have a deploy job up at the LF) https://wiki.onap.org/display/DW/OOM+NodePort+List Essentially there is now several free ports you can use in 302 If you have non-core/demo/geo-redundant/temporary ports you wish to reserve in 304 there are 2 example patches put in. James added a global 304 prefix (nodePortPrefixExt) you can use in your charts. Using 302/304 are almost identical but 302 is the primary prefix James's nodePortPrefix https://gerrit.onap.org/r/#/c/65281/ example 30258 to 30453 https://gerrit.onap.org/r/#/c/65299/ /michael From: Michael Arrastia Sent: Friday, September 7, 2018 8:02 AM To: Michael O'Brien <frank.obr...@amdocs.com>; Borislav Glozman <borislav.gloz...@amdocs.com> Cc: Giulio Graziani <giulio.grazi...@amdocs.com>; Gabriel Sanchez <gabriel.sanc...@amdocs.com> Subject: Spike nodePortPrefix Hi Michael, Thank you for your response on the OOM NodePort List<https://wiki.onap.org/display/DW/OOM+NodePort+List> comments section with regards to using the 304 port range instead of 302 for the new AAI Spike microservice. I think that to use the 304 range I would need to fix the nodePortPrefix in the Spike chart and override the pre-existing global.nodePortPrefix value of 302. Borislav pointed out that this could be problematic because it would prevent a legitimate attempt, for example through the command line, to overwrite the global.nodePortPrefix. And hence the suggestion to borrow the unused OOF port. Are you thinking that fixing the range in the Spike chart may be acceptable at this stage? Maybe you are aware of a Helm implementation that could apply the 304 prefix but still allow it to be overwritten from the command line? Any thoughts would be greatly appreciated. Thank you, Michael 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 (#12338): https://lists.onap.org/g/onap-discuss/message/12338 Mute This Topic: https://lists.onap.org/mt/25502174/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
