Hi,
- Are you using the integration-override.yaml file ? No - Did you update the image versions in the OOM clone using the script in the integration project ? No and According to Michael O'Brien, he recommends not to change it... thanks Dominique Deschênes Ingénieur chargé de projets, Responsable TI 816, boulevard Guimond, Longueuil J4G 1T5 450 670-8383 x105 450 670-2259 ----- Message reçu ----- De: Brian ([email protected]) Date: 02/01/19 10:19 À: [email protected], [email protected], Borislav Glozman ([email protected]) Cc: Jasmin Audet ([email protected]), Jacques Faucher ([email protected]) Objet: Re: [onap-discuss] OOM ONAP Deployment If its not up within a few hours then something in your configuration is wrong either images or access to the nexus repository. - Are you using the integration-override.yaml file ? - Did you update the image versions in the OOM clone using the script in the integration project ? https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins?focusedCommentId=48529890#comment-48529890 See the reference to the (update-oom-image-versions.sh) and the use of integration-override.yaml and public-cloud.yaml helm deploy dev local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml --namespace onap https://wiki.onap.org/pages/viewpage.action?pageId=29787124 also has some pointers. Brian From: [email protected] <[email protected]> On Behalf Of Dominique Desches Sent: Wednesday, January 02, 2019 9:33 AM To: [email protected]; Borislav Glozman <[email protected]> Cc: Jasmin Audet <[email protected]>; Jacques Faucher <[email protected]> Subject: Re: [onap-discuss] OOM ONAP Deployment hi, 13 days and we have the same result Thanks, Dominique Deschênes Ingénieur chargé de projets, Responsable TI 816, boulevard Guimond, Longueuil J4G 1T5 450 670-8383 x105 450 670-2259 ----- Message reçu ----- De: Borislav Glozman ([email protected]) Date: 30/12/18 02:59 À: [email protected], [email protected] Cc: Jasmin Audet ([email protected]) Objet: RE: [onap-discuss] OOM ONAP Deployment Hi, How long did you wait before doing the tests? PodInitializing state usually means docker is pulling images. So maybe you need to wait longer (hopefully by now all is downloaded…) Please try to make your environment with all pods in Ready state and then try robot tests. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 Amdocs aPlatinum member of ONAP From:[email protected] <[email protected]> On Behalf Of Dominique Desches Sent: Thursday, December 27, 2018 9:58 PM To: [email protected] Cc: 'Jasmin Audet' <[email protected]> Subject: [onap-discuss] OOM ONAP Deployment Hello, We have some issues in the deployment of ONAP Casablanca. 1. The setup we have: 1.1 OpenStack Pike (OS) - OpenStack Ansible - 1 Controller - 4 Compute nodes - 3 Ceph storage nodes All nodes are Dell R620 servers with 2 Xeon E5-2650v2 and 256GB of RAM. 1.2 Kubernetes, Rancher - Rancher v1.6.22, 1 node on OS, 4 vCPU 4GB RAM. - Kubernetes v1.8.3, Docker 17.03.2-ce, 4 nodes on OS, 16 vCPU 64GB RAM each. 1.3 ONAP Casablanca 2. The procedure we followed: 2.1 The k8s environment was setup by following this guide on ReadTheDocs: https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html 2.2 ONAP was setup by following this guide on ReadTheDocs: https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html#quick-start-label 2.3 I've joinded our version of onap/values.yaml 3. The results we get: 3.1 We can access the portal, but most pages return "refused to connect". 3.1.1 A&AI: aai.api.sparky.simpledemo.onap.org took too long to respond. 3.1.2 CLI: cli.api.simpledemo.onap.org refused to connect. 3.1.3 Policy: policy.api.simpledemo.onap.org refused to connect. 3.1.4 SDC returns the proper User Management page. 3.1.5 VID: The web page at https://vid.api.simpledemo.onap.org:30200/vid/welcome.htm?cc=1545938381291 might be temporarily down or it may have moved permanently to a new web address. 3.2 We can run the robot tests, but we get failures. 3.2.1 ete-k8s.sh portal test is passing. 3.2.2 ete-k8s.sh health test: 51 critical tests, 7 passed, 44 failed 3.3 Some containers are stuck in CrashLoopBackOff or in PodItinializing state. 3.3.1 onap-aai-aai-traversal-b5dc9895d-7gc5f: Readiness probe failed: dial tcp 10.42.68.214:8446: connect: connection refused 3.3.2 onap-aai-aai-sparky-be-75658695f5-m6kql: Waiting: PodInitializing 3.3.3 onap-aai-aai-traversal-update-query-data-zfvwb: Waiting: PodInitializing 3.3.4 onap-aai-aai-746f4ff754-c9b67: Waiting: PodInitializing 4. Questions: 4.1 Should we change anything in our onap/values.yaml file? 4.2 Is there another deployment procedure that can be followed? 4.3 Are there any known issues that results in ONAP being in a broken state like we are getting? 4.4 Is there any way for us as users to fix these issues in our deployment? 4.5 What's the most reliable way to get a basic deployment of ONAP up and running? Tks. Dominique Deschenes Ingénieur chargé de projet, Responsable TI 816, boulevard Guimond, Longueuil J4G 1T5 450 670-8383 x105 450 670-2259 This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review athttps://www.amdocs.com/about/email-terms-of-service -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14784): https://lists.onap.org/g/onap-discuss/message/14784 Mute This Topic: https://lists.onap.org/mt/28883609/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
