Comment 1 for bug 1842896

Are you saying that you have other machines in different zones that would
have capacity, but you are explicitly requesting zone-1 ? Or is the issue
that provisioning 3 machines from zone-1 is not being spread to the second
and 3rd maas nodes?
I don't believe Juju explicitly requests the KVM host, but would set the
zone constraint. Have you tried doing a similar request without Juju?

John
=:->

On Thu, Sep 5, 2019 at 1:30 PM Pedro Guimarães <email address hidden>
wrote:

> Public bug reported:
>
> We are testing Juju as VM scheduler and provisioner with MAAS KVM pods.
> In this testing scenario we had Juju 2.6.4 + MAAS 2.6.
>
> We set 4 nodes as KVM hosts on MAAS.
> 3 nodes on zone-1 / 1 node on zone-2
>
> If we set a VM with restriction:
> machines:
> # KVMs
> "1":
> constraints: cores=2 mem=4G root-disk=8G spaces=oam-space,testspace
> zones=zone-1
>
> Juju will pick the nodes from the right zone to compose the VM but it will
> always pick the same node over and over again.
> It will schedule VMs in disregard to any overcommit limitations that we
> may have set on MAAS.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> ** Affects: maas
> Importance: Undecided
> Status: New
>
> ** Also affects: maas
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1842896
>
> Title:
> [VM Provisioning] If constraints: zones=<ZONE> causes Juju to
> provision new VMs on same node of correct zone in disrespect of
> overcommit restrictions
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1842896/+subscriptions
>