[04:14] <mup> Bug #1633663 opened: Unlink interfaces creates a new link <MAAS:New> <https://launchpad.net/bugs/1633663>
[05:28] <ai114> Hi! I've just a (maybe stupid) question. Do I have to run the MAAS all the time or is it possible to deploy the OS on all the nodes and then shutdown the MAAS? What happens if I start the MASS again - will I see the nodes?
[06:18] <spaok> ai114: MAAS tends to be be DHCP and DNS for the nodes, so you would need to account for that lost
[06:20] <spaok> the new MAAS/Juju 2.0 HA uses DNS in MAAS, so that would also be lost
[06:20] <ai114> spaok: THANK you!
[06:20] <spaok> you can run MAAS ina container if you are trying to save resources
[06:21] <ai114> that's a good idea!
[06:21] <spaok> my dev env is MAAS in a container and a management VM, Juju VM, and two comp VMs in KVM, then the nova compute uses LXD
[06:21] <spaok> works pretty good
[06:25] <ai114> Thanks again - your config should work for me too.
[09:57] <mup> Bug #1633696 opened: regiond log leaks a lot of twisted <MAAS:New> <https://launchpad.net/bugs/1633696>
[12:39] <mup> Bug #1633717 opened: DHCP probe reports 'failure' when its really just completed <MAAS:New> <https://launchpad.net/bugs/1633717>
[12:57] <mup> Bug #1633726 opened: rackd tftp logging leaks a lot of python-isms <MAAS:New> <https://launchpad.net/bugs/1633726>
[13:27] <mup> Bug #1633727 opened: connectionpool leaks python-isms in log <MAAS:New> <https://launchpad.net/bugs/1633727>
[18:30] <mup> Bug #1633763 opened: MAAS wants to do a dhcp probe on a slave interface in a bond <MAAS:New> <https://launchpad.net/bugs/1633763>
[18:30] <mup> Bug #1633764 opened: MAAS dhcp probes on an internal bridge <MAAS:New> <https://launchpad.net/bugs/1633764>
[19:25] <mup> Bug #1633763 changed: MAAS wants to do a dhcp probe on a slave interface in a bond <MAAS:New> <https://launchpad.net/bugs/1633763>
[19:25] <mup> Bug #1633764 changed: MAAS dhcp probes on an internal bridge <MAAS:Invalid> <https://launchpad.net/bugs/1633764>
[22:57] <moparlakci> ola