[00:13] <bladernr_> Does anyone know if there are issues with django and maas on Trusty?
[00:19] <bladernr_> I have a system running trusty and just installed MAAS on it (system is fully updated).  After installing MAAS and setting the IP address, I tried accessing the dashboard at 10.0.0.10/MAAS and got an "Internal Server Error".
[00:20] <bladernr_> The following is from apache's error log: http://paste.ubuntu.com/6597120/
[00:20] <bladernr_> any ideas what's going on here?  Looks to be an issue with django of some sort, but I have no idea what...
[17:31] <andre118> hi
[17:32] <andre118> I am having problems using WoL power management on MaaS
[17:32] <andre118> can somebody help me out please?
[17:42] <andre118> I can't poweroff any node using the maas-cli stop
[17:42] <andre118> or using the web interface
[17:42] <andre118> the node goes from 'Allocated' to 'Ready', but doesn't shut down
[17:43] <rbasak> andre118: I'm not sure that WoL power management supports shutdown at all.
[17:45] <andre118> I know that, unlike IPMI, WoL is meant to only boot up machines
[17:47] <andre118> But considering the fact that it does not support, wouldn't it be easy for MaaS to take over the shutdown process?
[17:47] <rbasak> I don't think MAAS has credentials.
[17:47] <rbasak> (to individual nodes)
[17:48] <rbasak> But it's (relatively) trivial to write your own power management plugin to MAAS, so if there's some way that will work on your setup, you could modify the WoL hook.
[17:49] <andre118> I can give it a try
[17:49] <andre118> but I thought that, having the option for WoL, all minimum features would be supported
[17:50] <andre118> I mean, one can't use MaaS at all without having it shut his nodes down
[17:50] <andre118> so WoL power management isn't actually an option
[17:51] <rbasak> I think the intention was that you could experiment with MAAS. But in production, I'd expect you to have production server hardware. With WoL you can still do it, but you'll have to run around turning machines off.
[17:53] <andre118> ok, I will try to customize the WoL hook just like you suggested, thank you :)
[17:53] <andre118> one more thing related to WoL
[17:54] <andre118> I guess it is related to my hardware, but WoL only manages to boot up machines where I previously run a 'ethtool -s eth0 wol g' command
[17:55] <rbasak> evilnickveitch: ^^ do we have any documentation on node system requirements, and what users should expect depending on what they have? It seems to me that andre118 was surprised, and I can't find anything relevant in the documentation.
[17:55] <andre118> if I'm not missing any configuration, is it reasonable to put this command on a customized preseed?
[17:58] <rbasak> andre118: once you've run that command, does WoL stay persistently enabled? Then you could do it with a commissioning script. However, you'd need to manually boot each machine into commissioning to make that work.
[17:59] <rbasak> andre118: if it works then maybe you could do it during enlistment phase instead, to save that extra step. It's a hack on top of what enlistment is supposed to do though (touch the machine as little as possible).
[18:03] <andre118> I'm sorry, I lost your last comments
[18:04] <andre118> WoL will remain persistently until the node is reallocated (and subsequently installs a fresh OS)
[18:06] <andre118> so the solution is something like editing the comission script AND the preseeds so enables WoL whenever it allocates?
[19:01] <bladernr_> what is the proper way to import the PXE stuff when setting up MAAS now?  is it maas-cli or maas-import-pxe-files?
[19:25] <bladernr_> what is the proper way to import the PXE stuff when setting up MAAS now?  is it maas-cli or maas-import-pxe-files?
[19:26] <bladernr_> maas-cli didn't seem to do anything and maas-import-pxe-files has called maas-import-ephemerals but that just seems to be stalled and doing nothing
[19:27] <_bjorne> do you want to import boot files to? im using maas-cli maas node-groups import-boot-images
[19:28] <bladernr_> _bjorne: I tried that first and it didn't do anything... sat for well over an hour and there was no indication that anythign had happened
[19:29] <bladernr_> the "no boot files found" message still appears on the UI login
[19:29] <_bjorne> have you route to wan? so you is not only on lan? :)
[19:29] <bladernr_> yep
[19:30] <_bjorne> iptraf or tcpdum so you see something happend on ethernet?
[19:30] <bladernr_> when I ran maas-import-pxe-files, it did show downloading of all the various PXE files, but then it kicked off maas-import-ephemerals and just stopped.
[19:31] <bladernr_> _bjorne: heh, heres the kicker... this is on a laptop... eth0 (gigE) is on a private network, wlan1 is connected to the internet.
[19:31] <_bjorne> for me that take a long time to get all files, if you have slow internet.
[19:31] <bladernr_> hrmmm it could be just that...
[19:31] <bladernr_> maybe I'll hook the gigE back up to the wan side and retry then set the network back up as it should be.
[19:31] <_bjorne> im have 100mbit and that is some files that need down, like 1gb files or so :)
[19:32] <bladernr_> ahh... that's a good point... I could be just impatient as well...
[19:32] <bladernr_> do you happen to know where it dumps the files so I could at least monitor progress that way?
[19:33] <_bjorne> ../var/lib/maas
[19:34] <bladernr_> ahhh yeah...
[19:34] <_bjorne> locate maas :) and you see all maas dirs.
[19:35] <bladernr_> yep, thanks
[19:35] <_bjorne> or tcpdump -nvi ethX X=0 or what card you have
[19:36] <_bjorne> and you see if something happend there on network card.
[19:38] <bladernr_> yep.  I'll let that run a bit and see what happens
[19:41] <_bjorne> bladernr_ you see something?
[19:41] <bladernr_> _bjorne: yes... but I also restarted the import so it's downloading the PXE stuff again
[19:42] <bladernr_> so once it gets passed that to where it's downloading ephemerals, I'll look for stalled traffic or something
[19:43] <_bjorne> ok... put it going under the night, if you have slow connection :) so you have the files in the morning :) or edit import_ephemerals so that looks like this RELEASES="precise"
[19:43] <_bjorne> ARCHES="amd64/generic i386/generic"
[19:44] <_bjorne> if you using precise :) and you take down only that :) or what dist you using.
[19:44] <_bjorne> that files can you find in /etc/maas
[19:47] <bladernr_> _bjorne: awesome. thanks!  It is downloading the ephemerals now... I was just being impatient
[19:48] <_bjorne> hehe :)