Need ability to retain VNC container state upon redeployment of ONAP via OOM. One option might be to separate the VNC container from the Portal so it can be managed as an independent "jumpserver" application by OOM. Then it can simply be removed from the setenv.sh list of apps after its first install. This way OOM will not try to delete it or redeploy it on subsequent attempts to redeploy ONAP.

I have been re-installing ONAP via OOM’s cd.sh script a couple times to test patches.

Turns out the jump server (VNC ) on a re-install loses all the data as expected. Its a bit of a pain.

Would it be feasible to preserve that container as an option on a re-install via cd.sh or put its file system into the dockerdata-nfs (preserving things like apt-get install vim, apt-get install wget , wget postman (and the collections for ONAP REST API calls), apt-get install libgconf-2-4,, etc)  ?

Either method would work for me but seems like not  deleteing vnc as an option might be the easiest ?

Brian