Closed booxter closed 6 years ago
Full disclosure: I haven't tested it in my tripleo-quickstart setup because I can't make devmode.sh to not reset roles in ~/.quickstart each time I call it. Ideas on how to validate the fix?
For the record, I now deploy with https://review.openstack.org/#/c/518888/ instead, and it works fine. But I believe the change should be everywhere where we specify memory / cpu constraints for undercloud node since 8gb is just not enough.
As you discovered, the OVB defaults aren't actually used anywhere in TripleO. The tooling sets appropriate flavors already.
That said, I do think 16 GB is a more sane default now for anyone directly using OVB to stand up an environment. Even if they're not using the defaults verbatim, it provides better guidance on the sizing of the flavors that should be used.
Minimal requirements for undercloud nodes are described here: https://images.rdoproject.org/docs/baremetal/requirements.html
Specifically, it says:
"The undercloud VM or baremetal machine requires: [...] 16 GB free memory"
It's not just documentation that asks to change default flavor. If you try to deploy using tripleo-quickstart in RDO cloud / OVB, you will hit both tripleo-validations failures like:
There are 4 cores in the system, but there should be at least 8. The RAM on the undercloud node is 7822 MB, the minimal recommended value is 16384 MB.
And even when validations are ignored, the resulting environment fails because mariadb (or another crucial service) is killed by oom-killer. I personally experienced mariadb killed and as a result, heat-api failing when listing stacks with ECONNREFUSED from db server, which finally resulted in overcloud deployment failure.
xlarge is the smallest default flavor that provides 16gb ram, and so this patch uses this flavor.