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_kub
ernetes_rancher.html>
https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kube
rnetes_rancher.html
       
    2.2 ONAP was setup by following this guide on ReadTheDocs:
 
<https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstar
t_guide.html#quick-start-label>
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>
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
  <http://www.gcgenicom.com/signature/Tel_genicom.png>  450 670-8383 x105
<http://www.gcgenicom.com/signature/Telec_genicom.png>  450 670-2259
 

 <http://www.gcgenicom.com/>
<http://www.linkedin.com/company/groupe-conseil-g-nicom>
<http://twitter.com/gcgenicom> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14722): https://lists.onap.org/g/onap-discuss/message/14722
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]]
-=-=-=-=-=-=-=-=-=-=-=-

Attachment: onap-values.yaml
Description: Binary data

Reply via email to