[04:14] Bug #1633663 opened: Unlink interfaces creates a new link [05:28] 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] ai114: MAAS tends to be be DHCP and DNS for the nodes, so you would need to account for that lost [06:20] the new MAAS/Juju 2.0 HA uses DNS in MAAS, so that would also be lost [06:20] spaok: THANK you! [06:20] you can run MAAS ina container if you are trying to save resources [06:21] that's a good idea! [06:21] 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] works pretty good [06:25] Thanks again - your config should work for me too. [09:57] Bug #1633696 opened: regiond log leaks a lot of twisted [12:39] Bug #1633717 opened: DHCP probe reports 'failure' when its really just completed [12:57] Bug #1633726 opened: rackd tftp logging leaks a lot of python-isms [13:27] Bug #1633727 opened: connectionpool leaks python-isms in log [18:30] Bug #1633763 opened: MAAS wants to do a dhcp probe on a slave interface in a bond [18:30] Bug #1633764 opened: MAAS dhcp probes on an internal bridge [19:25] Bug #1633763 changed: MAAS wants to do a dhcp probe on a slave interface in a bond [19:25] Bug #1633764 changed: MAAS dhcp probes on an internal bridge === zerick_ is now known as zerick === marcoceppi_ is now known as marcoceppi [22:57] ola