=== frankban|afk is now known as frankban
[08:59] <neiljerram> brendand, roaksoax, FYI I just added a bit more investigation of my Xenial booting problem to https://bugs.launchpad.net/maas/+bug/1577838
=== dimitern is now known as dimitern|afk
[11:10] <youplabo1m> Hey :)
[11:11] <youplabo1m> In few hours, I ll use MaaS to deploy 16.04 servers. Is it possible to configure zfs pools with it ? It will be perfect
[11:11] <youplabo1m> for prepare LXD deploy :p
[11:11] <youplabo1m> to
=== dimitern|afk is now known as dimitern
[13:39] <kiko> youplabo1m, not yet with MAAS, unfortunately -- but you can definitely set up ZFS once Ubuntu is deployed
[13:39] <kiko> youplabo1m, we added XFS support in MAAS 2.0 (currently in beta)
[14:05] <youplabo1m> kiko: thx for this info :)
[14:06] <kiko> youplabo1m, what will you use MAAS for?
[14:07] <youplabo1m> kiko: deploy ubuntu 16.04 and replace KVM by LXD. And for LXD, I want use ZFS as storage
[14:08] <youplabo1m> I ll configure zfs with ansible. no problemo :p
[14:08] <kiko> awesome
[14:08] <kiko> youplabo1m, curious how well does ansible play with MAAS? can it drive the MAAS API?
[14:09] <youplabo1m> I never use it yet with MaaS. I am in my test periode phase
[14:09] <kiko> interesting
[14:09] <kiko> let me know what your experience is, a blog post would be killer
[14:13] <youplabo1m> oki doki
[15:32] <mup> Bug #1513485 changed: Commissioning doesn't update the IP of PXE interface UI, maybe due to lease parser failure <MAAS:Fix Released> <https://launchpad.net/bugs/1513485>
[15:32] <mup> Bug #1577863 changed: [1.9.2] Using Xenial Kernel by default to enlist/commission and can't seem to be able to change it <oil> <MAAS:New> <https://launchpad.net/bugs/1577863>
[16:51] <mup> Bug #1580260 opened: [2.0a4] Reserved IP ranges should be allowed to be created by standard users <MAAS:Triaged> <https://launchpad.net/bugs/1580260>
=== frankban is now known as frankban|afk
[18:03] <mup> Bug #1580279 opened: maas-cli 2.0 doesn't find 1.0 api <amd64> <apport-bug> <xenial> <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1580279>
[18:03] <mup> Bug #1580280 opened: [2.0a4] Disks less than 4MB in size cause a traceback on the MAAS server <storage> <MAAS:Triaged> <https://launchpad.net/bugs/1580280>
[18:04] <mup> Bug #1580279 opened: maas-cli 2.0 doesn't find 1.0 api <amd64> <apport-bug> <xenial> <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1580279>
[18:33] <mup> Bug #1580285 opened: [2.0b5] Machines successfully commission but don't get marked 'Ready' <MAAS:New> <https://launchpad.net/bugs/1580285>
[19:03] <mup> Bug #1580299 opened: Failed to monitor services and update database. <MAAS:New> <https://launchpad.net/bugs/1580299>
[19:33] <mup> Bug #1580299 changed: Failed to monitor services and update database. <MAAS:New> <https://launchpad.net/bugs/1580299>
[19:50] <bugrum> Is there a reason why MAAS 2.0 no longer supports Wake-on-LAN? This is a really useful feature
[19:51] <bugrum> The MAAS 2.0 Web UI no longer has it as an option
[19:51] <bugrum> on Ubuntu 16.04 LTS
[21:05] <kiko> roaksoax, see above wrt WoL
[21:05] <kiko> roaksoax, why was it removed, truly?
[21:45] <mup> Bug #1580350 opened: [2.0b5] AMT machines using wsman do not netboot <MAAS:Confirmed> <https://launchpad.net/bugs/1580350>