You can find the official documentation for installation and operation of ONAP with OOM here: http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html
The OOM documentation is broken into four different areas each targeted at a different user: * OOM Quick Start Guide<http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html#quick-start-label> - deploy ONAP on an existing cloud * OOM User Guide<http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#user-guide-label> - a guide for operators of an ONAP instance * OOM Developer Guide<http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_developer_guide.html#developer-guide-label> - a guide for developers of OOM and ONAP * OOM Cloud Setup Guide<http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_cloud_setup_guide.html#cloud-setup-guide-label> - a guide for those setting up cloud environments that ONAP will use The use of the ‘cd.sh’ script is not part of these instructions. Cheers, Roger From: <[email protected]> on behalf of Borislav Glozman <[email protected]> Date: Wednesday, June 6, 2018 at 11:04 AM To: Soumyarup Paul <[email protected]>, "'[email protected]'" <[email protected]> Cc: Syed Atif Husain <[email protected]>, Gopal Sabhadiya <[email protected]> Subject: Re: [onap-discuss] Install ONAP Beijing Release Looks like something happened to helm repo and it is not running on your host. Please run ‘nohup helm serve &’ and retry. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: [email protected] [mailto:[email protected]] On Behalf Of Soumyarup Paul Sent: Wednesday, June 6, 2018 1:47 PM To: '[email protected]' <[email protected]> Cc: Syed Atif Husain <[email protected]>; Gopal Sabhadiya <[email protected]> Subject: [onap-discuss] Install ONAP Beijing Release Hi All, I am facing a few issues while installing the Beijing release. 1. In the cd.sh script, should I uncomment this move file code if [ "$BRANCH" == "master" ]; then echo "moving values.yaml to oom/kubernetes/" #sudo cp values.yaml oom/kubernetes/onap If so, what is the encryption method used for password which I would need to provide here – openStackEncryptedPasswordHere: "c124921a3a0efbe579782cde8227681e" 2. If I try to install using the default values then I get the following error – List of ONAP Modules - look for terminating pods NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE kube-system heapster-76b8cd7b5-dl28v 1/1 Running 0 7d 10.42.34.140 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system kube-dns-5d7b4487c9-6d6m2 3/3 Running 0 7d 10.42.207.251 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system kubernetes-dashboard-f9577fffd-k5snh 1/1 Running 0 7d 10.42.149.137 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system monitoring-grafana-997796fcf-qdps2 1/1 Running 0 7d 10.42.132.98 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system monitoring-influxdb-56fdcd96b-xctvq 1/1 Running 0 7d 10.42.208.55 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system tiller-deploy-54bcc55dd5-scrbq 1/1 Running 0 7d 10.42.61.176 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net deleting /dockerdata-nfs chmod: cannot access '/dockerdata-nfs/onap': No such file or directory chmod: cannot access '/dockerdata-nfs/dev': No such file or directory pull new oom Cloning into 'oom'... remote: Total 16470 (delta 0), reused 16470 (delta 0) Receiving objects: 100% (16470/16470), 24.04 MiB | 14.89 MiB/s, done. Resolving deltas: 100% (8252/8252), done. Checking connectivity... done. moving values.yaml to oom/kubernetes/ start onap pods [common] make[1]: Entering directory '/root/oom/kubernetes' make[2]: Entering directory '/root/oom/kubernetes/common' [common] make[3]: Entering directory '/root/oom/kubernetes/common' ==> Linting common [INFO] Chart.yaml: icon is recommended 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /root/oom/kubernetes/dist/packages/common-2.0.0.tgz make[3]: Leaving directory '/root/oom/kubernetes/common' [mariadb-galera] make[3]: Entering directory '/root/oom/kubernetes/common' Hang tight while we grab the latest from your chart repositories... ...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts): Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused ...Successfully got an update from the "stable" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 1 charts Deleting outdated charts ==> Linting mariadb-galera [INFO] Chart.yaml: icon is recommended 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /root/oom/kubernetes/dist/packages/mariadb-galera-2.0.0.tgz make[3]: Leaving directory '/root/oom/kubernetes/common' [mongo] make[3]: Entering directory '/root/oom/kubernetes/common' Hang tight while we grab the latest from your chart repositories... ...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts): Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused ...Successfully got an update from the "stable" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 1 charts Downloading common from repo http://127.0.0.1:8879/charts Save error occurred: could not download http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: getsockopt: connection refused Deleting newly downloaded charts, restoring pre-update state Error: could not download http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: getsockopt: connection refused Makefile:37: recipe for target 'dep-mongo' failed make[3]: *** [dep-mongo] Error 1 make[3]: Leaving directory '/root/oom/kubernetes/common' Makefile:30: recipe for target 'mongo' failed make[2]: *** [mongo] Error 2 make[2]: Leaving directory '/root/oom/kubernetes/common' Makefile:39: recipe for target 'make-common' failed make[1]: *** [make-common] Error 2 make[1]: Leaving directory '/root/oom/kubernetes' Makefile:35: recipe for target 'common' failed make: *** [common] Error 2 [onap] make[1]: Entering directory '/root/oom/kubernetes' Hang tight while we grab the latest from your chart repositories... ...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts): Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused ...Successfully got an update from the "stable" chart repository Update Complete. ⎈Happy Helming!⎈ Error: aaf chart not found in repo http://127.0.0.1:8879/charts Makefile:42: recipe for target 'dep-onap' failed make[1]: *** [dep-onap] Error 1 make[1]: Leaving directory '/root/oom/kubernetes' Makefile:35: recipe for target 'onap' failed make: *** [onap] Error 2 Error: failed to download "local/onap" wait for all pods up for 15-80 min report on non-running containers No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. pending containers=0 check filebeat 2/2 count for ELK stack logging consumption sleep 5 min - to allow rest frameworks to finish The helm version gives the correct output but the make fails. Can you please help me on this? Any pointers on this would be highly appreciated. Thanks and Regards, Soumyarup Paul 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 <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
