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