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

DevOps: OOM config reset procedure for new /dockerdata-nfs content

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • None
    • None
    • None
    • OOM Sprint 8

       we may want to add a script to clean up the config pod generated FS in the event of a pull of new content

      see

      https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-DeletingAllContainers

      # check for the pod
kubectl get pods --all-namespaces -a
# delete the config pod
cd ../config
kubectl --namespace onap delete -f pod-config-init.yaml --all
# delete the fs
rm -rf /dockerdata-nfs/onap
# rerun the config
./createConfig.bash -n onap

       

            mayankg2703 mayankg2703
            michaelobrien michaelobrien
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: