[07:39] <bigjools> smoser: FYI I am just landing a branch in trunk that adds a maas command to manipulate api keys
[07:43] <rvba`> smoser: see "sudo maas apikey -h" (^)
[09:27] <epic_> i am getting TFTP open timeout when i boot my nodes
[09:27] <epic_> where can I see if my tftp server is running?
[10:21] <epic_> so I have my node booted from PXE, but after some PXE boots rounds I get:
[10:21] <epic_> Trying to load: pxelinux.cfg/01-00 (mac addr)
[10:21] <epic_> and it stops
[10:22] <epic_> and pserv.log spits out lots of error
[10:22] <epic_> s
[10:23] <epic_> exceptions.AssertionError: No PXE template found in '/usr/lib/python2.7/dist-packages/provisioningserver/pxe'!
[10:25] <epic_> status of the node is ready
[10:30] <epic_> http://pastebin.com/EHyZFZXf
[10:35] <bigjools> you're booting the node manually before maas thinks it needs booting
[10:35] <epic_> ok
[10:35] <epic_> it doesnt seem to have WoL
[10:35] <epic_> so how do i do it?
[10:36] <epic_> in the web interface the "start node" button is greyed
[10:36] <bigjools> If you have no way of auto-powering a node, then it diminishes the usefulness somewhat.   But you would need to work out which node maas wants to start (it'll be in an allocated state) and then power it up yourself
[10:37] <epic_> so how do i allocate it ?
[10:38] <bigjools> click start, or use juju
[10:38] <epic_> ah juju
[10:38] <epic_> because the start button is not clickable :)
[10:39] <bigjools> is it in a 'ready' state?
[10:39] <epic_> yeah
[10:39] <bigjools> hmmmm weird.
[10:39] <bigjools> rvba: ^ why would "start" be greyed out for a ready node?
[10:41] <rvba> epic_: don't you get a tooltip that explains why it's greyed out when you hover over the button?
[10:45] <epic_> huh after some fiddling with juju the status is now
[10:45] <epic_> Allocated to epic
[10:45] <epic_> (my maas username)
[10:45] <epic_> and start button is gone, trying to boot pxe again
[10:46] <epic_> so sorry i missed the grey button tooltip, dont remember it beeing any
[10:46] <epic_> it seems to boot fine now
[12:46] <smoser> bigjools, yeah, i saw that MP . thank you.
[14:05] <roaksoax> rvba: ping
[14:05] <rvba> roaksoax: hi
[14:05] <roaksoax> rvba: howdy! How's everything?
[14:05] <rvba> roaksoax: good… you all right?
[14:06] <roaksoax> rvba: iu'm ok, still getting used to the time.. lol
[14:06] <rvba> heh
[14:06] <roaksoax> rvba: so I was wondering if you have a list of things that you would like me (or the server team) to take care of on the maas team
[14:08] <rvba> roaksoax: well, I don't see anything urgent.  We're still debriefing the sprint with Julian.  We will probably be in touch next week about that.
[14:08] <roaksoax> rvba: right, doesn
[14:08] <roaksoax> rvba: right, doesn't have to be urgent but rather.. overtime...
[14:09] <roaksoax> rvba: since this week is vUDS.. i thought maybe could be a good idea to communicate the community what were the plans
[14:10] <rvba> roaksoax: the thing we want to do rather quickly where maybe you could give a hand is getting all the templates installed in /etc/maas.  But I must say I haven't looked into it precisely yet.
[14:11] <roaksoax> rvba: ok, I just wanna gather the list of things that I need to keep an eye on/help with so I can add it to "my" BP
[14:13] <rvba> roaksoax: we really need to debrief this with Julian (and we will do this on Monday) but the most accurate list of work items is the spreadsheet I've sent you the other day.
[14:13] <roaksoax> rvba: ok great!
[14:24] <roaksoax> rvba: if i'm around, you can consider including me into your meetings so I can stay up to date with the things you guys decide
[14:28] <rvba> roaksoax: We often met in my mornings (that's the only time suitable for all of us) but we will do our best to keep you in the loop.
[14:29] <roaksoax> rvba: cool thanks
[15:07] <roaksoax> rvba: http://summit.ubuntu.com/uds-1305/meeting/21833/servercloud-s-fastpath-install/
[15:10] <rvba> roaksoax: ta
[22:06] <mattrae> i'd like to answer this question about maas using the virsh power option: http://askubuntu.com/questions/292061/how-to-configure-maas-to-be-able-to-boot-virtual-machines
[22:07] <mattrae> anybody have an idea what the values for the virsh power parameters shoudl be?
[22:07] <mattrae> or where i should check the code
[22:07] <roaksoax> mattrae: the answer was provided by robie basak
[22:07] <roaksoax> mattrae: that's the correct answer
[22:08] <mattrae> roaksoax: cool, maas asks for 'Driver' as well but it isn't in the answer
[22:08] <roaksoax> mattrae: driver is not required
[22:09] <roaksoax> mattrae: mattrae nor is username
[22:10] <roaksoax> mattrae: htye are not used and they should probably be removed unless we add support for it
[22:10] <mattrae> roaksoax: great, thanks i'll clarify that. also the answer uses qemu:///system for the address. if i want to use qemu+ssh://10.0.0.1/ for example, do i need to generate a ssh key?
[22:14] <roaksoax> mattrae: yeah you would need to create an ssh key on the maas server, and and add the public one to the libvirt server so that maas connectes without authentication
[22:15] <mattrae> roaksoax: sweet, do you know where i'd need to put that private key for maas to use it?
[22:18] <roaksoax> mattrae: good question, I *think* you'd need to make the maas user have it
[22:18] <roaksoax> mattrae: but it doesn't have a home by default, so you;ll need to enable it
[22:18] <mattrae> roaksoax: cool, i'll play with that.. i can add a homedir for the maas user
[22:19] <roaksoax> mattrae: yeah you'll need to enable the user login, so you can sudo su into it
[22:22] <mattrae> roaksoax: sweet thanks, ill try it out :)
[22:24] <roaksoax> mattrae: cool :) let me know how it goes
[22:47] <mattrae> roaksoax: ok, it works :) i had to install libvirt-bin on the maas node to get virsh.. and then just needed Address:qemu+ssh://root@10.0.0.2/system and Power ID
[22:47] <mattrae> oh and i had to add the home directory and key for the maas user, and add the key to root's authorized_keys on the libvirt server
[22:49] <roaksoax> mattrae: cool :)