[00:15] <mwhudson> bigjools: hey, can you give me a clue how commissioning works
[00:15] <mwhudson> bigjools: is it a custom initrd you serve up?
[00:15] <bigjools> mwhudson: what's hard in the morning
[00:15] <bigjools> oh not that sort of clue
[00:16] <bigjools> mwhudson: yes, the images live in /var/lib/maas/ephemeral IIRC
[00:17] <mwhudson> oh hm, it mounts a rootfs over iscsi?  or am i reading this wrong?
[00:29] <bigjools> mwhudson: that's the installer image
[00:29] <bigjools> but yes
[00:29] <mwhudson> oh hang on
[00:29] <mwhudson> i think i meant enlistment
[00:29] <mwhudson> that thing where you boot a node for the first time
[00:29] <bigjools> it uses the same image
[00:29] <mwhudson> ok
[00:29] <bigjools> as commissioning
[00:30] <bigjools> just different options
[00:51] <mwhudson> ok
[00:52] <mwhudson> what i was trying to find out (as well as learning a bit more about MAAS) was how the name of a enlisted node was determined
[00:52] <mwhudson> i guess ultimately it must come (in my case) from the hostname supplied via dhcp
[00:54] <bigjools> mwhudson: it's a uuid
[00:54] <mwhudson> sorry not name
[00:54] <mwhudson> fqdn
[00:55] <bigjools> mwhudson: from memory, if you don't have a domain on the name already it uses the cluster's name as the domain
[00:55] <bigjools> so if you have your cluster called example.com then you'll end up with node.example.com
[00:56] <bigjools> maas creates dns zone called example.com and ensures the node's name is in it
[00:56] <mwhudson> right, but where does the "node" bit come from?
[00:56] <bigjools> the name of the node, either the auto-generated one or whatever you change it to
[00:56] <bigjools> acutally it's not a uuid any more, there was a change to give it a random 5-char name
[01:49] <Dr{Who}> Q. I am trying to limit the physical connections to my metal. I have 2 ports but using 1 is better. I have it setup as a vlan tagged port on my switches and I have configured the onboard nic to pxe using vlan 10. now it connects and downloads the startup image but at that point it fails because eth0 is not on a vlan. Can i tell maas to make sure to setup vlan on 10 during the next step?
[02:09] <Dr{Who}> also for some reason it keesp trying to iscsi up to the trusted side of my maas server not the other side. I have tried to figure out how to make that perm I have been editing the pxe config files by hand and it keeps reverting back or finding new places where that wrong ip is used.
[02:38] <Dr{Who}> also running dpkg-reconfigure maas does ask for the correct interface ip but it does not do anything. When I rebuild using 'maas-import-ephemerals' it uses the other ip.
[03:05] <bigjools> which version of maas are you using?
[04:07] <Dr{Who}> it is ubuntu 12.04 LTS and what ever came with it.
[04:07] <Dr{Who}> im still a bit confused as to do I use LTS or do I run the latest stuff that just came out the other day in 13.what ever it was.
[04:08] <Dr{Who}> i understood the point of LTS is well it will be "supported" long term : )
[04:08] <bigjools> Dr{Who}: the release in 13.04 is much superior
[04:08] <bigjools> 12.04 is basically broken, there's a pending SRU which brings it up to the same code as quantal
[04:09] <bigjools> you can use the stable PPA which has a more recent release, until the SRU is done
[04:10] <Dr{Who}> sounds like if I want to wait then 12.04 will be patched or I can use unstable I saw that someplace how to use that. Or I can just use 13.04. I vote 13.04 WAY too many problems and I am not doing production just testing anyway. Will 12.04 have all the latest stuff someday? because in production I like LTS
[04:13] <Dr{Who}> ok. Well anway I will try 13 out tomorrow. but I do hope all these goodies come to LTS soon.
[04:20] <bigjools> Dr{Who}: 12.04 will get an improved version in the near future
[04:20] <bigjools> we're just promoting some components to main from universe to be able to complete it
[04:20] <bigjools> but the version in the stable PPA is identical
[04:20] <bigjools> but 13.04 would be ideal, yes
[16:57] <mgz> allenap: how are manual uploads to maas file storage meant to work?
[17:28] <racedo> ping roaksoax
[17:29] <roaksoax> racedo: here
[17:31] <racedo> hey roaksoax
[17:32] <racedo> quick one, how does maas know during enlisting about the IPMI IP
[17:32] <racedo> i don't know where to look at in an installation where the IPMI settings are not being picked up
[17:35] <roaksoax> racedo: during enlistment maas runs a script that tries to detect ipmi user/password, IP
[17:35] <roaksoax> racedo: in queries the BMC for it
[17:35] <racedo> ok
[17:35] <roaksoax> racedo: so if the BMC might be returning 0.0.0.0 for ip address
[17:35] <racedo> can i do it manually to debug why it doesn't work
[17:35] <roaksoax> racedo: /usr/share/maas/preseeds/enlist_preseed
[17:36] <roaksoax> racedo: yeah you can
[17:36] <roaksoax> racedo: first do this: https://lists.launchpad.net/maas-devel/msg00808.html
[17:36] <roaksoax> so you can debug the epemeral image
[17:36] <roaksoax> racedo: so during the enlistment process you can simply ssh into the image and prevent it from rebooting
[17:36] <roaksoax> racedo: and then you could run the script
[17:37] <roaksoax> racedo: unless you are thinking of something else?
[17:37] <racedo> ok, i was thinking about trying it from the maas node where the hardware is the same if possible
[17:37] <roaksoax> racedo: unless you want to install ubuntu on the machine and run the script independently
[17:37] <roaksoax> racedo: and you can too
[17:37] <racedo> yeah
[17:38] <roaksoax> racedo: so /usr/share/maas/preseeds/enlist_userdata
[17:38] <roaksoax> racedo: go to: add_bin "maas-ipmitool-autodetect" <<"END_MAAS_IPMITOOL_AUTODETECT"
[17:38] <roaksoax> and copy/paste that section in a script and run it with sudo
[17:38] <racedo> ok
[17:39] <roaksoax> racedo: what hardware is this?
[17:39] <racedo> this are the blade servers in the boston lab
[17:40] <roaksoax> racedo: what's their IP addresses?
[17:40] <roaksoax> racedo: hold on
[17:40] <roaksoax> racedo: don't given them to me
[17:40] <racedo> :)
[19:13] <AskUbuntu> Juju and MAAS: ERROR No matching node is available | http://askubuntu.com/q/289226
[19:41] <roaksoax> dho/win 9
[23:45] <TheChistoso> hello...
[23:45] <TheChistoso> i can't get maas to move a node from deployed to ready
[23:46] <TheChistoso> the machine looks like it's ready to go...
[23:46] <TheChistoso> but maas is showing the nodes as deployed only
[23:46] <bigjools> what are you doing to try and move it?
[23:46] <TheChistoso> the  node is up and it said at the end that cloud init had completed
[23:46] <TheChistoso> i'm not doing anything
[23:47] <bigjools> so you enlisted it and then clicked "accept and commission" ?
[23:47] <TheChistoso> i thought that after it was done commissioning it would update the state itself
[23:47] <TheChistoso> yes -- and it completed all of that
[23:48] <TheChistoso> (on that note, though -- it wasn't fully automated -- I had to intervene to specify the file system partition layout)
[23:48] <bigjools> in commissioning it uses the same mechanism at the end of enlisting to signal to maas that it's done
[23:48] <bigjools> so this is odd
[23:49] <bigjools> does it work if you don't specify your custom partition?
[23:49] <TheChistoso> i didn't specify a custom partition
[23:49] <TheChistoso> i told it to use the guided partitioning scheme w/ lvm
[23:50] <TheChistoso> now the default is set to use precise -- i assume that's still okay
[23:50] <bigjools> what happens on the node's console when it commissions?
[23:51] <TheChistoso> everything appears to be fine during that phase
[23:51] <Marlinc> Shoudn't MAAS install Ubuntu on one of my hosts?
[23:51] <TheChistoso> Marlinc: yes
[23:51] <Marlinc> Because it did two reboots to add it to MAAS and one to set it up
[23:52] <Marlinc> But it didn't overwrite the previous install
[23:52] <Marlinc> Or is there something I dont get right
[23:52] <bigjools> maas only installs Ubuntu when something requests to use a node
[23:52] <TheChistoso> i've had a lot of problems w/ maas if you mess any of your configuration up. the only way i can get it to work cleanly is if i blow the entire thing away and start from scratch. it's a real pain...
[23:53] <bigjools> which version of maas?
[23:53] <bigjools> the one currently in precise is broken
[23:53] <TheChistoso> whichever the latest one shipping w/ raring is
[23:53] <bigjools> that one is fine
[23:54] <bigjools> I am surprised you need to start from scratch, that was only necessary in precise
[23:54] <Marlinc> So how would I make MAAS install Ubuntu? Just to see if it works
[23:54] <Marlinc> Or what would I need to do to see if it works
[23:54] <bigjools> Marlinc: bootstrap with juju is easiest
[23:55] <TheChistoso> there are lots of little gotchas and the documentation isn't coherent -- i've had to piece things together. e.g. generating an ssh key using RSA and a 2048-bit cipher and adding that to your account before commissioning...
[23:55] <bigjools> you don't need to add an ssh key before commissioning
[23:56] <TheChistoso> well there is documentation out that that says you do...
[23:56] <bigjools> before deploying, yes, before commissioning no
[23:56] <Marlinc> You need to add your SSH key in the web interface
[23:56] <Marlinc> Thats the only place right?
[23:56] <bigjools> Marlinc: you don't need to do that if you use juju
[23:56] <TheChistoso> minor feature request -- option for maas to generate a jujuu environments.yaml
[23:56] <Marlinc> That would be very nice lol
[23:57] <bigjools> TheChistoso: that will be available in the next release of juju
[23:57] <bigjools> it's not a maas problem
[23:57] <TheChistoso> not saying it is :D
[23:57] <bigjools> if you find problems, please file bugs
[23:57] <bigjools> otherwise nothing will get looked at
[23:57] <bigjools> and there's not always people around on here
[23:57] <TheChistoso> i understand (c: i write software for a living myself
[23:58] <bigjools> we're quite receptive to fixing problems
[23:58] <TheChistoso> so where should i start looking for answers?
[23:58] <bigjools> but the nature of this beast makes it hard to diagnose stuff
[23:58] <bigjools> answers to what?
[23:58] <TheChistoso> why my node isn't transitioning to ready
[23:59] <bigjools> I asked earlier what you see on the console
[23:59] <TheChistoso> i see a login prompt