How to update MSO configuration to use existing OpenStack region

 
1
0
-1

Hi,

I'm using ONAP in Kubernetes cluster on top of OpenStack. I would like to create new VF-module using VID. I have problem that currently MSO is not configured properly.

Durnig operation i have an error in /var/log/onap/MSO/VnfAdapter that shows that MSO is trying to connect to wrong URL = 1.2.3.4:5000

How to update MSO configuration to be sure that is pointing to valid openstack instance?

2018-03-09T15:47:16.130Z|e1189d31-ca11-4b62-aa91-3de0cc59e17c|Thread-296|CreateVfModule|BPELClient|Openstack||ERROR|AvailabilityError|Connection Exception|MSO-RA-9202E Exception communicating with OpenStack: Openstack Exception on Token request: org.openecomp.mso.openstack.exceptions.MsoIOException: Connect to 1.2.3.4:5000 [/1.2.3.4] failed: Connection timed out (Connection timed out)

2018-03-09T15:47:16.130Z|e1189d31-ca11-4b62-aa91-3de0cc59e17c|Thread-296|CreateVfModule|BPELClient|OpenStack|queryStack|ERROR|DataError|Exception - queryStack|MSO-RA-9227E Exception while query VNF:vFirewall-0309-1 in RegionOne/390a384dabf34c33a0b997d7292c3cbd


2018-03-09T15:47:16.130Z|e1189d31-ca11-4b62-aa91-3de0cc59e17c|Thread-296|CreateVfModule|BPELClient|OpenStack|queryStack|ERROR|DataError|Exception - queryStack|MSO-RA-9200E Exception: org.openecomp.mso.openstack.exceptions.MsoIOExcepti

on: Connect to 1.2.3.4:5000 [/1.2.3.4] failed: Connection timed out (Connection timed out) -  at org.openecomp.mso.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:1000) -       at org.openecomp.mso.openstack.utils.MsoHeat
Utils.queryStack(MsoHeatUtils.java:646) 
-   at org.openecomp.mso.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:788) -  at org.openecomp.mso.adapters.vnf.VnfAdapterRest$CreateVfModuleTask.run(VnfAdapterRest
.java:388) -      at java.lang.Thread.run(Thread.java:748) - Caused by: com.woorea.openstack.base.client.OpenStackConnectException: Connect to 1.2.3.4:5000 [/1.2.3.4] failed: Connection timed out (Connection timed out)
    CommentAdd your comment...

    1 answer

    1.  
      2
      1
      0

      Lukasz Urbanski

      Look into /docker-nfs/onap/mso/mso-docker.json to configure KEYSTONE and Regions and modify. You will require to remove the MSO docker container (not the pod) to make the changes effective.

      1. Lukasz Urbanski

        kranthi guttikonda Thanks for response,

        Currently my /docker-nfs/onap/mso/ doesn't contain mounted mso-docker.json file. How to mount this direrectory to be visible in MSO's containers?

      2. kranthi guttikonda

        Lukasz Urbanski That mean configuration was not generated properly. Did you run ./createconfig.sh -n onap before starting the containers? It will run a pod which create the configuration file for all components. 

        kubectl -n onap get pods -o wide -a

        kubectl -n onap logs -f config

        Check the logs of the config pod and see if anything wrong there. 

        If you inspect the mso docker container directly you should see something like below. If not something is really wrong at configuration itself.

        {
        "Source": "/dockerdata-nfs/onap/mso/mso",
        "Destination": "/shared",
        "Mode": "",
        "RW": true,
        "Propagation": "rprivate"
        },

      3. Lukasz Urbanski

        kranthi guttikonda
        Yes, we have run createconfig.sh.
        We found that file is monted in different dir:

        {
                        "Type": "bind",
                        "Source": "/var/lib/kubelet/pods/ba1d10dd-2377-11e8-8033-02e15047d0cd/volumes/kubernetes.io~configmap/mso",
                        "Destination": "/shared",
                        "Mode": "",
                        "RW": true,
                        "Propagation": "rprivate"
                    }

      4. kranthi guttikonda

        Lukasz Urbanski Which version of OOM are you using? I guess you are using Master branch. So, you have to change the configmap then. If it is in master then you need to perform the following

        cd oom/kubernetes/mso/resources/config/mso

        edit mso-docker.json

        helm delete --purge onap-mso

        cd oom/kubernetes/

        helm install --name onap-mso mso //this will create the new configmap with modified values and pods

      5. Lukasz Urbanski

        kranthi guttikonda Yes, we are using OOM from master branch. I will try to follow this steps.

      CommentAdd your comment...