Hi Brian, On Wed, Dec 12, 2018 at 01:26 AM, Brian wrote: > > Cross project helm chart readiness checks are difficult. There are timing > issues depending on the environment that seem to occur. Most times we see > success in the daily complete installs but in some environments there is > slowness that occurs. > > You might want to include the public-cloud.yaml overrides if you are not > already. > > helm deploy dev local/onap -f > /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f > /root/integration-override.yaml --namespace onap > > Brian >
Are these dependency issues being tested, measured and optimised in one of the S3P sections? Is it "resiliency"? https://wiki.onap.org/pages/viewpage.action?pageId=15998867 Startup dependencies should not rely on guesses for timing, since every environment will have different performance characteristics (even the same environment on a different day due to load, failures, latency, failovers, etc). ONAP should not be so fragile that it has trouble just initialising itself. Should the containers be tested with arbitrarily-variable pauses included, so as to force the dependency issues to be properly resolved? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14428): https://lists.onap.org/g/onap-discuss/message/14428 Mute This Topic: https://lists.onap.org/mt/28717981/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
