The docker-compose file is under the oam repository

~[build=path]/sdnc/oam/installation/src/main/yaml/docker-compose.yml

I believe docker requires you to remove the containers and re-build them 
“docker-compose up -d” to see the new ports but I may be wrong.

You may also need to expose ports in the Dockerfile for the sdnc container 
which is under sdnc/oam/installation/sdnc/src/main/docker/Dockerfile


Brian





From: [email protected] 
[mailto:[email protected]] On Behalf Of Abdelmuhaimen Seaudi
Sent: Saturday, May 27, 2017 7:49 PM
To: ROSE, DANIEL V <[email protected]>
Cc: [email protected]
Subject: Re: [onap-discuss] Exposing a port on SDNC ODL container

Hi.

The sdnc_contoller_container has exposed port 8282 --> 8181.

How can I add another exposed port, for example 4189 --> 4189 to allow routers 
to synchronize with the ODL in the running sdnc_controller_container ?

Do I need to shutdown the sdnc_controller_container and rerun it again with 2 
exposed ports 8282:8181 and 4189:4189 ?

If yes, what is the full command to run the sdnc_controller_container ?

The sdnc_vm_init.sh script shows only "/opt/docker/docker-compose up -d", so I 
don't know what was the full command to run the sdnc_controller_container.

root@vm1-sdnc:~# docker container list
CONTAINER ID        IMAGE                                   COMMAND             
     CREATED             STATUS              PORTS                     NAMES
86092805e713        openecomp/dgbuilder-sdnc-image:latest   "/bin/bash -c 'cd 
..."   41 hours ago        Up 41 hours         0.0.0.0:3000->3100/tcp    
sdnc_dgbuilder_container
4caa9aefae1d        openecomp/admportal-sdnc-image:latest   "/bin/bash -c 'cd 
..."   41 hours ago        Up 41 hours         0.0.0.0:8843->8843/tcp    
sdnc_portal_container
885c56b1b1d9        openecomp/sdnc-image:latest             
"/opt/openecomp/sd..."   41 hours ago        Up 41 hours         
0.0.0.0:8282->8181/tcp    sdnc_controller_container
fdbdfc8aa306        mysql/mysql-server:5.6                  "/entrypoint.sh 
my..."   41 hours ago        Up 41 hours         0.0.0.0:32768->3306/tcp   
sdnc_db_container

Abdelmuhaimen Seaudi, CCIE # 25265
Email: [email protected]<mailto:[email protected]>
Skype: aseaudi
LinkedIn: 
www.linkedin.com/in/aseaudi<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_aseaudi&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YkcQtl8hYzIokQQ0UCr6-5rT3VIzh5KwY8pxRO4g6ow&s=m2PN-Rl-7HSilLAktKC9lMUs_iUV3FP_FXnIs_O2aPQ&e=>
Telephone: +2012 84644 733


On Sun, May 28, 2017 at 12:03 AM, ROSE, DANIEL V 
<[email protected]<mailto:[email protected]>> wrote:
It runs on docker so you would also need to expose the port in docker after you 
install it

On May 27, 2017, at 4:13 PM, Abdelmuhaimen Seaudi 
<[email protected]<mailto:[email protected]>> wrote:
Hi.

I want to install the BGPPCEP feature on the ODL running in a container on the 
SDNC VM.

This means I need to expose the default PCEP port 4189 out of the container so 
that routers can synchronize with the PCE plugin running in ODL.

How can I do that ?

Thanks.

Abdelmuhaimen Seaudi, CCIE # 25265
Email: [email protected]<mailto:[email protected]>
Skype: aseaudi
LinkedIn: 
www.linkedin.com/in/aseaudi<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_aseaudi&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=UrenvZ-0k1Sz20stfv9af-tlmNTaSvhf_gQkIPcrR2w&s=-J64A4PM_MvV9S6iX5pca06QADpaKXQnMrxkxeNnY0M&e=>
Telephone: +2012 84644 733

_______________________________________________
onap-discuss mailing list
[email protected]<mailto:[email protected]>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=UrenvZ-0k1Sz20stfv9af-tlmNTaSvhf_gQkIPcrR2w&s=YEw3RtyTNDfB8VybL8nRPvxxFM5GSD363k6sQpDHkuQ&e=

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to