/srv/irclogs.ubuntu.com/2016/05/10/#maas.txt

=== frankban|afk is now known as frankban
neiljerrambrendand, roaksoax, FYI I just added a bit more investigation of my Xenial booting problem to https://bugs.launchpad.net/maas/+bug/157783808:59
=== dimitern is now known as dimitern|afk
youplabo1mHey :)11:10
youplabo1mIn few hours, I ll use MaaS to deploy 16.04 servers. Is it possible to configure zfs pools with it ? It will be perfect11:11
youplabo1mfor prepare LXD deploy :p11:11
youplabo1mto11:11
=== dimitern|afk is now known as dimitern
kikoyouplabo1m, not yet with MAAS, unfortunately -- but you can definitely set up ZFS once Ubuntu is deployed13:39
kikoyouplabo1m, we added XFS support in MAAS 2.0 (currently in beta)13:39
youplabo1mkiko: thx for this info :)14:05
kikoyouplabo1m, what will you use MAAS for?14:06
youplabo1mkiko: deploy ubuntu 16.04 and replace KVM by LXD. And for LXD, I want use ZFS as storage14:07
youplabo1mI ll configure zfs with ansible. no problemo :p14:08
kikoawesome14:08
kikoyouplabo1m, curious how well does ansible play with MAAS? can it drive the MAAS API?14:08
youplabo1mI never use it yet with MaaS. I am in my test periode phase14:09
kikointeresting14:09
kikolet me know what your experience is, a blog post would be killer14:09
youplabo1moki doki14:13
mupBug #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
mupBug #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>15:32
mupBug #1580260 opened: [2.0a4] Reserved IP ranges should be allowed to be created by standard users <MAAS:Triaged> <https://launchpad.net/bugs/1580260>16:51
=== frankban is now known as frankban|afk
mupBug #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
mupBug #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:03
mupBug #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:04
mupBug #1580285 opened: [2.0b5] Machines successfully commission but don't get marked 'Ready' <MAAS:New> <https://launchpad.net/bugs/1580285>18:33
mupBug #1580299 opened: Failed to monitor services and update database. <MAAS:New> <https://launchpad.net/bugs/1580299>19:03
mupBug #1580299 changed: Failed to monitor services and update database. <MAAS:New> <https://launchpad.net/bugs/1580299>19:33
bugrumIs there a reason why MAAS 2.0 no longer supports Wake-on-LAN? This is a really useful feature19:50
bugrumThe MAAS 2.0 Web UI no longer has it as an option19:51
bugrumon Ubuntu 16.04 LTS19:51
kikoroaksoax, see above wrt WoL21:05
kikoroaksoax, why was it removed, truly?21:05
mupBug #1580350 opened: [2.0b5] AMT machines using wsman do not netboot <MAAS:Confirmed> <https://launchpad.net/bugs/1580350>21:45

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!