-
Task
-
Resolution: Won't Do
-
Low
-
None
-
None
-
OOM-Offline Sprint 3
In some of our deployments it was detected that there is much bigger chance of having ONAP deployed successfully if not all components are deployed at once (in parallel). This is probably more visible in our deployments where number of k8s nodes is 3 and less.
In the past (Amsterdam) we were using similar approach which is visible also in cd.sh script
referenced probably here https://gerrit.onap.org/r/#/c/75843/
I think we should have some param in our offline installer, which (when set) will force deployment of various ONAP components in some chain based on dependencies specified.
This can be switched-off for some deployments where speed is more important and maybe more powerful k8s hosts are present