[08:00] <rvba> bigjools: I can do this: https://code.launchpad.net/~rvb/maas/ipaddresses3/+merge/221988.  But I'm not sure how to improve the readability of the condition.  It's not easy to split because each check depends on the previous check being true.
[08:01] <bigjools> looking
[08:02] <bigjools> rvba: I think a nested for might be better here
[08:02] <bigjools> the nested list comp is uuuugly
[08:03] <rvba> A nested for would be much slower though.
[08:03] <bigjools> why?
[08:04] <rvba> Using list comprehension means the iteration is done at a lower level.
[08:04] <bigjools> also why not use itertools.chain?
[08:04] <rvba> I can do that.
[08:04] <bigjools> are you just using sum to expand the query set?
[08:04] <rvba> It's basically the same.
[08:04] <rvba> Yes.
[08:04] <bigjools> right
[08:05] <bigjools> sum obfuscates it a bit
[08:05] <bigjools> it's a bit like me getting a MatchError earlier today because "[] != []"
[08:05] <bigjools> the joy of repr :)
[08:55] <bigjools> rvba: https://code.launchpad.net/~julian-edwards/maas/deallocate-static-ip/+merge/221825 if you fancy it
[08:55] <rvba> bigjools: sure
[08:55] <bigjools> rvba: and https://code.launchpad.net/~julian-edwards/maas/macaddress_to_ngi/+merge/221984 is easy karma
[09:25] <rvba> bigjools: reviews done.
[09:48] <rvba> I'm landing jtv's lint branch.  It looks pretty safe but I'll deal with any fallout.
[10:15] <xperia> Hi All. i was able to successful install Maas on my Ubuntu Server and to Commision my first Node. Maas Show now that the Status of my Node is Ready. When i Try however to PXE Boot my new Node Nothing Happens if i do however try to PXE Boot the Node over my Router however it works!
[10:15] <xperia> What could be the Problem and how can i fix it? I would love to be able to Start Up the Nodes with MaaS itself instead over the Router.
[13:36] <smoser> designated, the .dist was created by that shell snippet.
[13:36] <smoser> hm..
[13:36] <smoser> interresting.
[13:36] <smoser> i wonder if htat is busted.
[13:36] <smoser> nah. we are using hard links there, which might make it ocnfusing, but the script does a cp to the .dist, and then modifies the original so that should be ok.
[13:45] <gmb> rvba, allenap, jtv: Can I get a review for https://code.launchpad.net/~gmb/maas/fix-commissioning-page-distro-list-bug-1312844/+merge/222010? I’m losing the ability to tell if it passes the smell test, so I’m perfectly happy with informed rejection :)
[13:45] <allenap> gmb: Sure.
[13:45] <gmb> Ta
[13:46] <rvba> Code smell detector activated.
[14:21] <allenap> rvba: Are you taking a look at that branch too then?
[14:21] <rvba> allenap: no, since you're reviewing it.
[14:21] <allenap> rvba: Would you mind casting your eye over it for the forms stuff?
[14:21] <rvba> allenap: sure
[16:35] <designated> smoser, I'm not sure what happened but I'm going to save off all of our custom preseeds and blow maas away.  I'm going to do a fresh install.  One of the interesting things I was seeing on nodes being commissioned, the hwclock was being adjusted to the correct local time but the timezone was still being reported as UTC.
[16:36] <smoser> designated, time zones dont really matter.
[16:36] <smoser> the only thing that really matters is the bios clock.
[16:36] <designated> is there a way to get a list of all ipmi addresses of all nodes in maas from the CLI?  'maas <profile> nodes list' doesn't list the ipmi ip address.
[16:37] <smoser> once you're up, a reboot will have ubuntu set the hardware clock to be utc.
[16:38] <smoser> designated, no. there is not. you can probalby get it fairly easily with python
[16:39] <smoser> https://bugs.launchpad.net/maas/+bug/1233158
[16:39] <designated> word
[16:40] <designated> I'll just dump them from the arp table on one of my routers and write a quick shell script to power cycle each one using ipmitools
[18:19] <designated> smoser, should the DNS zone name under cluster controller be a FQDN?
[18:20] <smoser> i'd tihnk so. like example.com
[18:20] <smoser> i think
[18:24] <designated> smoser, thanks
[20:39] <designated> smoser, so I have a fresh load of maas, finished importing boot images, added backdoor login and tried enlisting a node.  the node boots and sits at login screen, it never finishes and powers off, and is not showing up in maas.
[20:40] <designated> smoser, i do see some failure messages in cloud-init.log such as: 2014-06-04 14:24:42,994 - importer.py[DEBUG]: Failed at attempted import of 'ubuntu' due to: No module named ubuntu
[20:42] <smoser> was this always the problem? that it was failing to enlist ?
[20:43] <designated> smoser, no, it was working previously
[20:43] <designated> smoser, running 1.5.1+bzr2269-0ubuntu0.1
[20:44] <designated> smoser, like i said this is a fresh build.
[20:49] <smoser> there is some output going somewhere probably. not sure whats happening, but if it turns off then some code ran. that output would have been to the vga console i think. so you should have seen it.
[20:49] <smoser> it will sit doing nothing for a while
[20:50] <designated> smoser, it doesn't power off.  i can try powering it off via ipmi
[20:53] <designated> smoser, i powered it off and it showed up in maas.  it must have failed to detect ipmi.
[20:54] <smoser> designated, oh. if it doesnt power off, then you should be albe to ssh in and look around.
[20:55] <smoser> (since you back-doored it)
[20:55] <smoser> and apt-get install pastebinit and then pastebinit /var/log/cloud-init*
[20:58] <designated> smoser, i manually set ipmi settings, trying to commission it now to see if that will work.
[21:00] <designated> smoser, and right back to where i was yesterday during commissioning.
[21:00] <designated> OAuthUnauthorized: 'Expired timestamp: given 1401893824 and now 1401915424 has a greater difference than threshold 300'
[21:22] <magicrobotmonkey> is there a way to read the power settings from the maas cli tool?
[21:23] <magicrobotmonkey> on the gui i can see the ip, user, and pass
[21:23] <magicrobotmonkey> but i cant get it from the cli
[21:27] <magicrobotmonkey> i have power_type in read
[21:28] <magicrobotmonkey> but not the other information
[21:41] <designated> magicrobotmonkey, 'maas <profile> nodes list' will show you the power type but there is no CLI command to show ipmi, ip address, username or password.
[21:46] <magicrobotmonkey> ok thanks
[23:29] <designated> blake_r, smoser either one of you around?
[23:30] <designated> during commissioning, it looks like it never finishes because it cannot apt-get update.  I see a process running: root      1413  0.0  0.0  29008  2376 ?        S    17:13   0:00 apt-get --assume-yes -q update
[23:30] <designated> if i try to update it manually, i get the following:
[23:31] <designated> $ sudo apt-get update
[23:31] <designated> sudo: unable to resolve host vn-mgmt-0
[23:31] <designated> E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
[23:31] <designated> E: Unable to lock directory /var/lib/apt/lists/