-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
I know that even if we change the order of the pods - they still essentially come up together and the only way to fully bring them up in dependency order is to wait between each pod deploy until it is finished before starting the next.
However, I have had a couple requests to at least not use an alphabetical order when deploying
https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins
ubuntu@a-osn-cd:~/oom/kubernetes$ sudo helm deploy onap local/onap --namespace onap -f ../../dev.yaml fetching local/onap release "onap" deployed release "onap-aaf" deployed release "onap-aai" deployed release "onap-appc" deployed release "onap-clamp" deployed release "onap-cli" deployed release "onap-consul" deployed release "onap-contrib" deployed release "onap-dcaegen2" deployed release "onap-dmaap" deployed release "onap-esr" deployed release "onap-log" deployed release "onap-msb" deployed release "onap-multicloud" deployed release "onap-nbi" deployed release "onap-oof" deployed release "onap-policy" deployed release "onap-pomba" deployed release "onap-portal" deployed release "onap-robot" deployed release "onap-sdc" deployed release "onap-sdnc" deployed release "onap-sniro-emulator" deployed release "onap-so" deployed release "onap-uui" deployed release "onap-vfc" deployed release "onap-vid" deployed release "onap-vnfsdk" deployed
- duplicates
-
OOM-1547
ONAP consistent deployment of pods in dependency order - to avoid failed random deployments
-
- Closed
-