Description of problem: The masters/workers instance parametes should be customized using the machine pool. Today all of the parameters are set on the initial template creation, and can only be overriden by export TF_VAR_xyz, which is a bad way of exposing this capability. Expected results: oVirt's machinepool object should have mem/cpu/disk size parameters, and they should be used to create the instances, if they are set.
Roy, is that even desirable capability for IPI? I don't know how other platforms handle this, but as far as I understand, the point of IPI isn't really to be customizable.
Other platforms allow that degree of customization. It's a reasonable balance because not all clusters have the same needs, and not all ovirt/rhv clusters have the same capabilities.
Hi Roy, could you please comment about how users can consume this functionality? I tried deploying OCP4.5 cluster (using the latest nightly) with this specified in install-config.yaml: controlPlane: architecture: amd64 hyperthreading: Enabled name: master platform: ovirt: memory_mb: 12 replicas: 3 However, the created master VMs still had only 8GB of memory. Could you please attach some detailed info on the usage?
this is bug is only the cluster api provider component. To complete this should be in as well Bug 1820300
I cannot really verify that until https://bugzilla.redhat.com/show_bug.cgi?id=1820300 is merged.
Roy, I suppose this is pretty much verified by verifying https://bugzilla.redhat.com/show_bug.cgi?id=1820300, right?
yes. once you verify it.
Thank you for clarification, Michal :) Chat response from Roy: the answer is yes for the question you can use it without the istaller you can edit the machineset object oc edit machineset <name of the worker pool set>
(In reply to Jan Zmeskal from comment #8) > Roy, I suppose this is pretty much verified by verifying > https://bugzilla.redhat.com/show_bug.cgi?id=1820300, right? Actually we must verify this first, to unblock its cherry pick to 4.4 [1] once [1] is merged I will be able to complete the 4.4 cherry-pick to the installer. The installer is dependent on the cluster-api-provider-ovirt repository.
Verified this alongside 1820300, see here: https://bugzilla.redhat.com/show_bug.cgi?id=1820300#c9
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409