This page is intended for discussions on the various ways of hosting the docker images locally and addressing the problem of re-pulling the images from the public ONAP nexus proxy every time ONAP OOM is installed. This would provide a local caching of images, minimizing the pod synchronization issues faced in a multi-node k8s setup which often prevents them from running successfully.
Local Docker registry setup
Follow the steps in following link to setup Rancher and k8s cluster:
https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html
Please note the Rancher, Helm, Kubernetes versions have changed for Casablanca release. So in case you are pulling Beijing release use the scripts ( openstack-rancher.sh, openstack-k8s-node.sh etc) from the oom/docs source directory.
Create a new VM from a ubuntu 16.04 cloud image with 6GB RAM, 5vCPUs, 300GB storage to host the docker registry
Add this VM to same network to which the Rancher and k8s nodes are attached.
Install docker on it
$apt update
$apt install docker.io
Pull and run the registry pointing to public ONAP nexus proxy
$docker run -d -p 5000:5000 --restart=unless-stopped --name registry -e REGISTRY_PROXY_REMOTEURL=https://nexus3.onap.org:10001 registry:2
Registry is listening on 5000 port
While launching the pods using "helm install" override the default repository settings as follows
$helm install/upgrade “--set global.repository=REGISTRY_VM_IP:5000”
Local Nexus proxy setup
<TBD>