Hi Hector A, thank you for your response.
*Santiago Rodríguez García* | Senior Analyst T/ + 34 986 410 091 (ext) 227 www.optaresolutions.com [image: Optare Solutions] <http://optaresolutions.com/> 2018-04-25 1:13 GMT+02:00 ANAPAN-LAVALLE, HECTOR A <[email protected]>: > Hi Santi, > > > > For the Amsterdam release: > > > > - I have come across that same error when I deployed ONAP in a > multi-node/vm HA Kubernetes version of Rancher > (https://rancher.com/docs/rancher/v1.6/en/kubernetes/resiliency-planes/) but > not when the K8S cluster is hosted on a single VM only, so wondering if you > tried doing this. One thing to make sure is to try using the latest supported > version of docker for rancher which is 17.03.x I believe > (https://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions). > > - Also, I used the README.md when installing ONAP using the OOM Amsterdam > release (running createConfig.sh -n onap to create the namespace first, then > running createAll.sh -n onap to create the ONAP instance) > > > > > > For the Beijing release: > > > > - While the code is not stable enough yet, there was an issue with the > docker image registry (nexus3.onap.org) for the past few weeks but my > understanding is that it has been solved. > > - Also, you may want to look into having a local docker proxy that pulls > the images from the LF docker registry to pull the images faster and more > consistently (https://docs.docker.com/registry/recipes/mirror/). Another > option is to download your own local nexus3 OSS repo in its own instance, and > use it as a docker registry to proxy the images from nexus3.onap.org. > > > > ===================================================================== > > ===================================================================== > > ===================================================================== > > > > > > > > Hi all, > > > > I've been trying to deploy the ONAP entire platform in my local environment > > following the official documentation without the desired results: > > > > - First, I tried the amsterdam release installation: > > - kubectl 1.7.7 > > - rancher 1.6.10 > > - helm 2.3.0 > > - docker 1.12 > > - onap deployment using oom: > > - install/deployment/cd.sh > > - oom/kubernetes/oneclick/createAll.sh > > > > Some of the pods are returning errors like: > > > > Error syncing pod > > Back-off restarting failed container > > (combined from similar events): Error: failed to start container > > "filebeat-onap-aai-model-loader": Error response from daemon: > > {"*message":"invalid > > header field value* \"oci runtime error: container_linux.go:247: starting > > container process caused \\\"process_linux.go:359: container init caused > > \\\\\\\"rootfs_linux.go:53: mounting > > \\\\\\\\\\\\\\\"/dockerdata-nfs/onap/log/filebeat/logback/filebeat.yml\\\\\\\\\\\\\\\" > > to rootfs > > \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/5c0516a9e0641c993fda14a5818d53b59ff4342da146d52a3b58aaf045ce6295\\\\\\\\\\\\\\\" > > at > > \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/5c0516a9e0641c993fda14a5818d53b59ff4342da146d52a3b58aaf045ce6295/usr/share/filebeat/filebeat.yml\\\\\\\\\\\\\\\" > > caused \\\\\\\\\\\\\\\"not a directory\\\\\\\\\\\\\\\"\\\\\\\"\\\"\\n\""} > > > > > > - Then, I tried with beijing/master: > > - kubectl 1.8.6 > > - rancher 1.6.14 > > - helm 2.6.1 > > - docker 17.03 > > - onap deployment using helm install local/onap > > > > Some of the pods are not starting because they cannot pull the image. It > > seems that large images produces a timeout. I found something related with > > increasing a kubelet config parameter, but the followed k8s installation > > guide does not produce any kubelet installation. > > > > It seems that the code is not stable enough, but i saw that many people are > > working with the platform so is possible to deploy it. > > > > How did you deploy the platform? Is there any hidden step that I'm missing? > > > > Thanks, > > > > BR, Santi > > *Santiago Rodríguez García* | Senior Analyst > > T/ + 34 986 410 091 (ext) 227 > > www.optaresolutions.com > > [image: Optare Solutions] <http://optaresolutions.com/> > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > <http://lists.onap.org/pipermail/onap-discuss/attachments/20180412/e0b51f7b/attachment.html> > > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-discuss > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
