Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-115

createAll.bash should run or warn on missing config-init pod (missing /dockerdata-nfs)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Low Low
    • None
    • None
    • None
    • None

       we need to combine the 1-time config pod creation with the other pods

      see docs in the wiki

      https://wiki.onap.org/display/DW/ONAP+on+Kubernetes

      Wait until all the hosts show green in rancher, then run the script that wraps all the kubectl commands

      run the one time config pod - which mounts the volume /dockerdata-nfs contained in the pod config-init. This mount is required for all other ONAP pods to function. Note: the pod will stop after NFS creation - this is normal.

      cd oom/kubernetes/config

      Before running pod-config-init.yaml - make sure your config for openstack is setup correctly - so you can deploy the vFirewall VMs for example

      vi oom/kubernetes/config/docker/init/src/config/mso/mso/mso-docker.json

      replace for example

      "identity_services": [{
      "identity_url": "http://OPENSTACK_KEYSTONE_IP_HERE:5000/v2.0",

      ~/onap/oom/kubernetes/config# kubectl create -f pod-config-init.yaml

      pod "config-init" created

            david.sauvageau david.sauvageau
            michaelobrien michaelobrien
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: