Hi Peter, I think that for your immediate needs you can do 'sed' on the values.yaml files and replace nexus3.onap.org with your docker registry. Do not forget the oneclick/setenv file, there is an environment variable ONAP_DOCKER_REGISTRY as well.
There is a change in the oven that should make this easier in the future, you are welcome to look at the reviews in oom gerrit. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Piotr Jaszczyk Sent: Thursday, December 14, 2017 11:43 AM To: [email protected] Subject: [onap-discuss] [oom] Setup "local" Docker registry for Kubernetes-based installation Hello, We are trying to install ONAP on our internal Eucalyptus-based cloud (AWS interface). So far we've created a Terraform setup which is creating "Kubernetes on Rancher" cluster, as described in the wiki. To minimize startup time I want to prepull docker images to our cloud-local Docker registry. I'd like to avoid prepulling all images to all K8s nodes every time a new cloud is created. The CI pipeline is already defined (docker pull using script from OOM-328 + docker tag + docker push) and is able to synchronize images. Now I want to use Helm setup so I can deploy apps on a specific K8s cluster but I want to use our local registry as the image-source. AFAIK images' names are defined in `values.yaml` files but there I can see no strict convention about the naming of keys in "image" section, ie. sometimes the value contains full docker image with version and sometimes version is specified separately. My initial thought would be to convert existing `values` files using some script. Without any clear convention such script would be prone to errors in the future. A cleaner solution would be to prepare OOM@K8s for such scenario, eg. by specifing a variable (like dockerRegistry) in one place. How would you suggest to proceed? Best regards, Peter J. -- Piotr Jaszczyk Engineer, Software Development Java MANO SOAM 1 R&D WRO 12 - ONAP squad Nokia Poland, Wrocław, West Gate _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss 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> _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
