Hi,

I opened [1]. If this is not the right place/component/product please change it accordingly.

Thanks.

Regards,

Nico

  [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1897532

El 12/11/20 a las 12:21, Nicolás escribió:
Hi Michal,

No, in the GUI it behaves as it should (ballooning is enabled after creating the pool).

Could you please point out where should I fill-in the bug? (bugzilla or github...)

Thanks!

El 12/11/20 a las 10:56, Michal Skrivanek escribió:
Hi Nicolas,
it does sound like a bug, ballooning shouldn’t be disabled in this case.
does it behave the same in GUI?

Thanks,
michal

On 12 Nov 2020, at 11:49, Nicolás <nico...@devels.es <mailto:nico...@devels.es>> wrote:

Sorry, I forgot to add the screenshot!

El 11/11/20 a las 12:32, Nicolás escribió:
Hi,

We're using oVirt 4.3.8 along with ovirt-engine-sdk-python (4.4.1) to handle our pools.

Pools are based on a template which has ballooning enabled. However, when deploying a VmPool based on that template, has the "Ballooning enabled" field disabled, uneditable and an icon which states: "The field is not attached to any instance type" (screenshot attached).

We're handling a big number of VMs based on pools (> 1500), and we think this should be enabled.

However, I don't see a field in the types.VmPool definition that allows that.

Is that even doable? Our Python code is similar to this:

    newpool = types.VmPool(name='test',
    cluster=cl,
    template=t,
    max_user_vms=1,
                                             size=1,
    type=types.VmPoolType.MANUAL)
    vmpool_serv.add(newpool)

  * cl is a types.Cluster instance with ballooning_enabled=True
  * t is a types.Template instance with Ballooning enabled.

Thanks.

Nico


_______________________________________________
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@ovirt.org
Privacy Statement:https://www.ovirt.org/privacy-policy.html
oVirt Code of 
Conduct:https://www.ovirt.org/community/about/community-guidelines/
List 
Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRWPZSNGX5UCZJW7NIT6XY72BFYTTHOL/

<Captura de pantalla de 2020-11-11 12-17-02.png>_______________________________________________
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email to users-le...@ovirt.org <mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PFO66W2AVDEPMZ74BG76IWJ4DRSY7TSF/



_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TQXOVXAJHSKKPC7DWRGKVZEUB4HBSV5D/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GS34TT7IMWCRMZQBS445AAMN6IPQOUJZ/

Reply via email to