Moshe Hoadley, Currently we use docker-compose to bring up both vnfmarket(FE-BE) dockers and PostGres DB docker.
The postgres-docker IP Address is passed to vnfmarket(FE-BE) docker dynamically(docker-compose) and before the docker is run, the JDBC string is changed to the postgres -docker IP address using docker-entry scripts. The database connection, UI and backend works fine. Please let me know if you find any issues or have any suggestions. FYI .. vnfmarket (refrepo) docker contains both front-end and backend. With regards, Murali From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley Sent: 31 October 2017 12:47 To: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [vnfsdk] - Docker packaging issues Hi In addition, I found that the portal docker doesn't have access to the db docker. After investigation I found that portal uses '172.0.0.1' in the db connection string - the db docker has a different IP even though they run on the same host. The solution is to use a host name like 'marketdb' in the connection string and deploy the db container with the same name. docker will use its internal DNS to resolve the db docker ip. With your permission I would like to go ahead and commit this fix. Thanks Moshe Hoadley * 972-9-77-62712 [cid:image001.png@01D2F989.346CD870] From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley Sent: Sunday, October 29, 2017 3:41 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [vnfsdk] - Docker packaging issues Hi I've started to play around with vnfsdk, I found that some .sh files contain a windows flavor end of file characters (CR LF). Is it work in progress? If not, I would like to commit the fix for this issue. Thanks Moshe Hoadley * 972-9-77-62712 [cid:image001.png@01D2F989.346CD870] 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 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
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
