[02:09] <mup> Bug #1753874 opened: machine can be compose in a full pool because  of typo  <MAAS:New> <https://launchpad.net/bugs/1753874>
[02:18] <mup> Bug #1753874 changed: machine can be compose in a full pool because  of typo  <MAAS:New> <https://launchpad.net/bugs/1753874>
[02:21] <mup> Bug #1753874 opened: machine can be compose in a full pool because  of typo  <MAAS:New> <https://launchpad.net/bugs/1753874>
=== edmz_ is now known as edmz
[12:23] <mup> Bug #1754012 opened: wsman dependency on older curl will cause issues in bionic for maas <MAAS:New> <https://launchpad.net/bugs/1754012>
[12:36] <cnf> how do you make a maas setup multi region?
[12:38] <roaksoax> cnf: https://docs.maas.io/2.3/en/manage-ha
[12:38] <roaksoax> xygnal: lvm for centos is not within our plans atm
[12:39] <cnf> roaksoax: isn't that one region in a redundant setup?
[12:39] <roaksoax> cnf: ah so you want to setup a single maas for multiple site locations ?
[12:39] <cnf> yes
[12:39] <roaksoax> cnf: we recommend a MAAS per DC
[12:39] <cnf> yeah, we don't look forward to 35 maas instances and UIs
[12:41] <cnf> we have a meeting with canonical people on this in about 2 hours for our MVP, but i want to get some ideas checked before we go into that one
[12:42] <cnf> atm, we are considering "abusing" zones as DC locations
[12:43] <cnf> so run one HA region controller, and put each DC rackd's into a separate zone
[12:45] <cnf> roaksoax: why do you not support this, btw?
[12:50] <cnf> hmm
[14:05] <mup> Bug #1754034 opened: improvements for UI around users <MAAS:New> <https://launchpad.net/bugs/1754034>
[14:35] <mup> Bug #1754041 opened: [2.4]  /run/lock/maas:networks-monitoring prevents discovery of networks <MAAS:Triaged> <https://launchpad.net/bugs/1754041>
[14:35] <mup> Bug #1754045 opened: [2.4] MAAS sometimes fails to insert subnets in maas-proxy.conf <MAAS:Triaged> <https://launchpad.net/bugs/1754045>