https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/onap-oom-heat.html#deploying-an-updated-docker-manifest
Is a pointer to documentation on the manifest update. Brian From: FREEMAN, BRIAN D Sent: Wednesday, December 05, 2018 11:49 AM To: [email protected]; [email protected]; Marcus G K Williams <[email protected]> Subject: RE: [onap-discuss] [E][onap-discuss][SO]Configuring SO with multi-VIM Did you rm the dev-so directory on dockerdata-nfs on the re-deploy. Typically in integration we no longer use the enable/disable approach to redeploy. https://wiki.onap.org/pages/viewpage.action?pageId=29787124 1. Helm del dev-so –purge 2. Kubectl -n onap get pods till all gone 3. Kubeclt -n onap get pvc /pv /secrets and clean up as needed 4. Rm dev-so and subtending directory on /dockerdata-nfs (this is wwhere the so mariadb is located) 5. Edit your helm charts and or integration-override.yaml * Image version should match docker-manifest.csv or docker-manifest-staging.csv depending on what you are trying to test. * Integration script update-oom-image-versions.sh will do that for you automatically if you run it i. ~/integration/version-manifest/src/main/scripts * if you edited / upated helm charts: i. make so ii. make onap 1. helm deploy dev local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml --namespace onap --verbose This should deploy dev-so and keep your current PODs / containers. Brian From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Gopigiri, Sirisha via Lists.Onap.Org Sent: Wednesday, December 05, 2018 11:02 AM To: Marcus G K Williams <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] [E][onap-discuss][SO]Configuring SO with multi-VIM Hi Marcus, I did a redeploy by setting so to false in onap/values.yaml and changing the images and then enabled so. I also tried with the fresh installation of complete ONAP by changing the SO images in OOM prior to deployment. But still I was facing the same issue, that is the three pods didn't come up. After creating the table that you pointed out in mariadb pod only the catalog-db-adapter and openstack-adapter pods came up, however the vfc-adapter pod didn't come up. When I tried instantiating the vf-module I got "template type not supported error". Please find the logs attached. Could you please let me know what configuration am I missing here? Thank you Best Regards Sirisha Gopigiri -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14292): https://lists.onap.org/g/onap-discuss/message/14292 Mute This Topic: https://lists.onap.org/mt/28238442/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
