[VM Provisioning] If constraints: zones=<ZONE> causes Juju and MAAS to provision new VMs on same node of correct zone in disrespect of overcommit restrictions
Bug #1842896 reported by
Pedro Guimarães
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
Undecided
|
Unassigned | ||
MAAS |
Expired
|
High
|
Unassigned |
Bug Description
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.5.
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=
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.
Related branches
~pguimaraes/maas:kvm-overcommit-fix-lp1842896
Rejected
for merging
into
~blake-rouse/maas:fix-1843493
- Blake Rouse: Pending requested
-
Diff: 110 lines (+72/-2)2 files modifiedsrc/maasserver/forms/pods.py (+55/-2)
src/maasserver/models/bmc.py (+17/-0)
summary: |
- [VM Provisioning] If constraints: zones=<ZONE> causes Juju to provision - new VMs on same node of correct zone in disrespect of overcommit - restrictions + [VM Provisioning] If constraints: zones=<ZONE> causes Juju and MAAS to + provision new VMs on same node of correct zone in disrespect of + overcommit restrictions |
Changed in juju: | |
status: | New → Invalid |
description: | updated |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Blake Rouse (blake-rouse) |
milestone: | none → 2.7.0alpha1 |
Changed in maas: | |
milestone: | 2.7.0b1 → 2.7.0b2 |
Changed in maas: | |
milestone: | 2.7.0b2 → none |
Changed in maas: | |
assignee: | Blake Rouse (blake-rouse) → nobody |
To post a comment you must log in.
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: oam-space, testspace /bugs.launchpad .net/bugs/ 1842896 /bugs.launchpad .net/juju/ +bug/1842896/ +subscriptions
>
> 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=
> 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:/
>
> 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:/
>