diff options
author | Tim Rozet <trozet@redhat.com> | 2017-02-20 12:38:54 -0500 |
---|---|---|
committer | Tim Rozet <trozet@redhat.com> | 2017-02-22 18:53:51 +0000 |
commit | 1ef3c3600d5b1692f65a445cf9e1c2e10a46314e (patch) | |
tree | 82fb89b104482c842c89b9805f4bcb0cbdf5e134 /lib/overcloud-deploy-functions.sh | |
parent | e1a633529c06a63f9c710317f25e63b8bd574812 (diff) |
Allows for specifying compute node RAM
Currently we allow specifying ram per Overcloud VM. If the node is
detected as ODL, we bump the RAM to a minimum of 10GB. There is a need
to be able to specify the RAM per compute node in cases where we need
controller RAM to be high, but want compute nodes to be low (like CSIT)
- in order to keep the memory footprint as small as possible.
Changes Include:
- Adds '--virtual-compute-ram' argument that will override the
'--virtual-ram' param for compute nodes
- Fixes a bug where if ODL is used and RAM is overridden to 10GB for
Control nodes, it was also accidentally being set for compute nodes
- Modifies '--virtual-ram' to be '--virtual-default-ram' in order to
clarify this parameter sets the default amount of RAM for all
overcloud nodes which may be overridden by a role specific arg
Change-Id: Ia36082aa2167d9897f3ec6753d08804352301c63
Signed-off-by: Tim Rozet <trozet@redhat.com>
Diffstat (limited to 'lib/overcloud-deploy-functions.sh')
0 files changed, 0 insertions, 0 deletions