[OOM] SO port(s) not exposed #oom #so


DeWayne Filppi
 

After doing the Helm install (Beijing branch) in my environment, I notice that port 8080 (jboss) isn't exposed on the host network, although all the Dockerfiles I've seen (and even elm) charts seem to expose it.   Intentional?


Borislav Glozman
 

It is not supposed to be exposed on host network. NodePort is exposed.

 

Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726

amdocs-a

Amdocs a Platinum member of ONAP

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of DeWayne Filppi
Sent: Tuesday, July 17, 2018 1:55 AM
To: onap-discuss@...
Subject: [onap-discuss] [OOM] SO port(s) not exposed #oom #so

 

After doing the Helm install (Beijing branch) in my environment, I notice that port 8080 (jboss) isn't exposed on the host network, although all the Dockerfiles I've seen (and even elm) charts seem to expose it.   Intentional?

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


Borislav Glozman
 

Let’s step back.

What do you mean host network?

 

These are SO services and their node ports:

 

onap          so                          NodePort       10.43.102.170   <none>                                 8080:30223/TCP,3904:30225/TCP,3905:30224/TCP,9990:30222/TCP,8787:30250/TCP   1d

onap          so-db                       NodePort       10.43.221.16    <none>                                 3306:30252/TCP                                                               1d

 

Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726

amdocs-a

Amdocs a Platinum member of ONAP

 

From: DeWayne Filppi [mailto:dewayne@...]
Sent: Tuesday, July 17, 2018 6:10 PM
To: Borislav Glozman <Borislav.Glozman@...>
Cc: onap-discuss@...; dewayne@...
Subject: Re: [onap-discuss] [OOM] SO port(s) not exposed #oom #so

 

So NodePorts aren't exposed on the host network?  In any case, you're saying it's dynamic.

 

On Tue, Jul 17, 2018 at 3:29 AM, Borislav Glozman <Borislav.Glozman@...> wrote:

It is not supposed to be exposed on host network. NodePort is exposed.

 

Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726

amdocs-a

Amdocs a Platinum member of ONAP

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of DeWayne Filppi
Sent: Tuesday, July 17, 2018 1:55 AM
To: onap-discuss@...
Subject: [onap-discuss] [OOM] SO port(s) not exposed #oom #so

 

After doing the Helm install (Beijing branch) in my environment, I notice that port 8080 (jboss) isn't exposed on the host network, although all the Dockerfiles I've seen (and even elm) charts seem to expose it.   Intentional?

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,



 

--

 

DeWayne Filppi
Sr. Architect, CTO Office, Cloudify

(714)512-1706mailto:dewayne@...http://cloudify.co

 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


DeWayne Filppi
 

OK, I see the port is not on the host network.  Thanks.