#maas 2013-02-01 <arbit_> hello all <arbit_> exit <roaksoax> bigjools: ping <roaksoax> bigjools: did maas constraints work on precise (cobbler) MAAS? <arbit_> bigjools: hi <AceFace1> hello all, good morning! <AceFace1> i have a small production rack that has several services running on it; apache, ejabberd, asterisk, mysql, php, etc. I'd like to try out maas+juju in a virtual environment before deploying it on hardware. i have made a virtual network in virt-manager without dhcp so that i can serve dhcp from the provisioning node. but when i try to pxe boot a second node, it doesnt boot. alternatively i have also booted a second node with the server12.10 disk and tried use <roaksoax> AceFace1: it seems that you need to configure MAAS for DHCP/DNS <roaksoax> AceFace1: though, you could let libvirt manage DHCP for you by telling it where to PXE boot from <AceFace1> i, being the noob that i am, am mostly unfamiliar with libvirt and am using virt-manager, libvirts GUI. i just dont know how to configure it to have a tftp and boot images etc <AceFace1> are there such options for libvirt? <roaksoax> AceFace1: yes <roaksoax> AceFace1: virsh net-list <roaksoax> from the command line: <roaksoax> virsh net-list will give you a list of networks <roaksoax> there should be the network you created <roaksoax> virsh net-edit <network-name> <roaksoax> would allow you to edit it <roaksoax> AceFace1: http://pastebin.ubuntu.com/1598438/ <roaksoax> that a sample config <roaksoax> i use <roaksoax> for maas <roaksoax> and sudo virsh net-destroy <net name> && sudo virsh net-start <net name> will allow you to apply the changes <roaksoax> and that should be it <AceFace1> roaksoax: thank you so much for helping me with my problem and for the config, i greatly appreciate it! im pretty excited about getting this working, thanks! <roaksoax> AceFace1: you're welcome ;) #maas 2013-02-03 <Peter_______> Anybody known when Maas will be included in the LTS release? #maas 2013-02-04 <roaksoax> rvba: howdy! the "fix" is merely to not list raring on etc/maas/import_pxe_files thogh i expected they would be available by now <roaksoax> smoser ETA on raring ephemetal? <rvba> roaksoax: Hi, thanks for your reply. <rvba> It's a bit weird to add support for raring before the images are available :). <roaksoax> rvba: it was requested :) <rvba> Okay :). <rvba> But now the automated testing is broken :/ <roaksoax> they want to test raring deployment <roaksoax> rvba: just disable raring by default on import_pxe_files forbthe time being <rvba> roaksoax: you mean revert your change? <roaksoax> rvba: not completely <roaksoax> rvba only etc/import_pxe_files <roaksoax> rvba or in import_ephemerals only list precise and quantal <roaksoax> i think the latter is better <roaksoax> or i can do it :) <rvba> roaksoax: if you don't mind, that would be great ;) <roaksoax> rvba: this should do it: http://paste.ubuntu.com/1608483/ <rvba> roaksoax: if the images are going to be available presently, it might not be worth itâ¦ <roaksoax> rvba: yeah I asked smoser last week, he said that he was hoping to have them soon that's why I didn't disable it by default <rvba> Ok, I could also fix etc/import_pxe_files in the integration test for now. <roaksoax> yeah that too :) <roaksoax> rvba: btw... http://pastebin.ubuntu.com/1608495/ <rvba> roaksoax: that's a weird one, I'm going to ask allenap to have a look at this one ;) <roaksoax> cool :) <roaksoax> thanks <roaksoax> rvba: that seems to be quantal archive error <roaksoax> rvba: so no owrroes as the SRU should cover that <roaksoax> rvba: or maybe is my machine which is broken <roaksoax> weird <roaksoax> since I upgraded ot the SRU version <roaksoax> anyway <roaksoax> wXgs3Ra4yWsNY3aRSw:S5EWzC8uc6mJxFvvcp:YLGfy3ZSZZMUuepwdeDPwBRgLznPf4gR <roaksoax> err <roaksoax> rvba: how can I change the power parameters of a node from the cli? <roaksoax> 22 575.979.1648 <roaksoax> err <allenap> roaksoax: maas-cli(8) has an example of setting power params; search for power_parameters. There's no documentation of the parameter names themselves though, afaict :-/ <roaksoax> allenap: yeah i got it :)! though the problem is that I only want to update 1 field, but it clears out everything else <allenap> roaksoax: Mmm, sorry :( <roaksoax> allenap: heh no worries :) I'll work around it :) <PeterVink> Question: When setting up PXE boot with only option 66 in the DHCP (as my router only supports 66, not 67), will it work to PXE boot the systems for MAAS? <PeterVink> Question: When setting up PXE boot with only option 66 in the DHCP (as my router only supports 66, not 67), will it work to PXE boot the systems for MAAS? <PeterVink> Anybody? <smoser> rvba, could you review https://code.launchpad.net/~smoser/maas/iscsi-root-equal/+merge/146016 for me ? <smoser> or, because it is 'approve', can i just set it so <smoser> i just forget what the rules are <rvba> smoser: you've got a +1 vote so you can mark it approved and it will get landed. (also, I created a package with that branch and had a run in the lab) <rvba> lgtm btw ;) <smoser> rvba, gracias. i'll mark approved. <rvba> smoser: will you need to backport it to 1.2 ? <smoser> rvba, i'm sure its trivial to do. <smoser> i'd consider it a low priority bug fix. <smoser> it is arguably security releated, in that a user of a instance in maas could "take over" a node as it is right now. <rvba> smoser: it is trivial to do. Then you can self-approve that 1.2 branch as it will be a simple backport. <smoser> rvba, ok. i'll do that. thanks for your help. <smoser> rvba, is there a "correct" way to do the 1.2 cherry pick ? <smoser> ( cd ../trunk.iscsi-root-equal && bzr log -r -1 -p ) | patch -p0 <smoser> is easy enough, but clealry would not maintain any bzr knowledge of what was cherry picked <rvba> smoser: the simplest way is to use bzr to do the work for you. <smoser> this is where you tell me how to do that. <rvba> smoser: cd maas-1.2 && bzr merge -c <revision_id> ../maas && bzr commit -m "Backport of revision <revision_id>" <smoser> ah. '-c' . i tried '-r' and it wasn't so happy. #maas 2013-02-05 <shang__> bigjools: ping, curious if the new maas has been backported to 12.04 yet? <bigjools> shang__: you'll have to ask roaksoax, he's sorting that out <shang__> bigjools: thanks <shang__> roaksoax: thoughts? :) <dholbach> hiya <dholbach> can somebody reply to https://code.launchpad.net/~racb/ubuntu/precise/squid-deb-proxy/cloud-archive/+merge/142088 or let me know if bug 1087145 can be closed? <ubot5> bug 1087145 in squid-deb-proxy "maas proxy prevent nodes access cloud archive " [Undecided,New] https://launchpad.net/bugs/1087145 <dholbach> hey rbasak <dholbach> I asked this earlier - maybe you can help: <dholbach> can somebody reply to https://code.launchpad.net/~racb/ubuntu/precise/squid-deb-proxy/cloud-archive/+merge/142088 or let me know if bug 1087145 can be closed? <ubot5> bug 1087145 in squid-deb-proxy "maas proxy prevent nodes access cloud archive " [Undecided,New] https://launchpad.net/bugs/1087145 <dholbach> (trying to get the sponsoring queue cleaned up) * rbasak looks <rbasak> dholbach: we've had the discussion on conffile updates in SRUs now, and my understanding is that we can do it here if needed. Daviey thought an SRU to Precise was appropriate for this which is why I prepared the merge. But I don't have permissions to create that sort of bug task. Daviey, do you think we still need this? <rbasak> ^^ <dholbach> rbasak, did you see mvo's response in the merge proposal? <rbasak> Yes <dholbach> ok <dholbach> thanks :) <rbasak> The issue is that MAAS users in Precise are presumably affected, hence the desire for an SRU <dholbach> sure <roaksoax> dholbach: cold u please assing the bug to me :) <roaksoax> shang__: soon after we fix few moew issues <dholbach> done <roaksoax> dholbach: thanks ;) <roaksoax> rvba: howdy <roaksoax> how can we delete all nodes from maas (without accessing the shell) <allenap> roaksoax: I shall attempt to help! Do you mean from the web UI? <roaksoax> allenap: from anywhere (just looking for a user friendly) <allenap> roaksoax: Right, so "without accessing the shell" means "no hackery", so maas-cli is okay. Let me see... <roaksoax> bigjools: ping <bigjools> roaksoax: yo #maas 2013-02-06 <roaksoax> bigjools: yo! so we have some serious DNS issues <smoser> bigjools, i'm not able to reproduce roaksoax's problem locally <smoser> bigjools, see what you think about my comment on https://bugs.launchpad.net/maas/+bug/1116700 <ubot5> Launchpad bug 1116700 in MAAS "MAAS 1.2 no longer auto generates a MAC based hostname" [Critical,Incomplete] <EntropyWorks> once I add node and it MAC I chose the Power type IPMI. filled in the parameters and saved. should the node reboot right? It never sees to do that. If I manually force it to boot off the network it grabs the pxelinux.0 but doesn't seem to have a pxelinux.cfg/default <bigjools> EntropyWorks: maas is responsible for starting the node, if you start it manually it won't work <bigjools> because the tftp server won't realise it's getting booted as the node is not in the right state <jtv> Code review needed! https://code.launchpad.net/~jtv/maas/bug-1116700/+merge/146835 <rvba> jtv: I'll have a look presently. <jtv> Thanks. <jtv> I see you have replaced the word "momentarily" in your lexicon. :) <rvba> Well, I still use it, just to piss Julian off. <rvba> :) <jtv> :) <jtv> I had a call with another tall man called Julian earlier. <rvba> I hope you managed to piss him off too. <jtv> I almost got his name wrong because Edwards somehow claims the mental monopoly on that slot in my brain. <jtv> So yes, I almost pissed him off. <jtv> I should add "British expat" to round out the similarities. <smoser> rvba, https://code.launchpad.net/~smoser/maas/lp1103716/+merge/146863 if you'd like <rvba> smoser: sure, I'll have a look in a sec <smoser> allenap, wanted to folow up a bit on fast path installer... <allenap> smoser: What's up? <smoser> how are we doing there.. do we/i/roaksoax need to do anything? <allenap> smoser: We've not done anything on it, so, no, you don't need to do anything I don't think, we do. Is there a deadline? <smoser> i dont have a deaadline, no <smoser> but should we set one ? <smoser> feature freeze is march 7. <smoser> lets say i'd like to have necessary bits into maas by feb 21 ? <allenap> smoser: That sounds sane to me. I'll email Julian, and CC you, as this is his decision. <GTFr0> I'm having a problem with MAAS, where nodes stay in the "commissioning" state. I think it maybe a NIC issue (not sure), but is there any way of verifying what NIC drivers are in the PXE booted kernel? <GTFr0> (I originally through the issue was oath-related time skew, but I updated the ephemeral disk image to run ntpdate on boot, and that didn't seem to help) <GTFr0> the kicker is that I can't find any indication in any logs on the MAAS server that any of the commissioned nodes are connecting <smoser> GTFr0, are you able to see console logs ? <smoser> if you enlisted correctly, then that is the same initramfs that is used for commissioning. <smoser> (ie, same modules and dthe like) <smoser> but it is quite possible that you're just missing nodes <smoser> er... missing modules <smoser> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1115710 <ubot5> Launchpad bug 1115710 in MAAS "Mellanox mlx4_en network driver is not automatically loaded" [Critical,Triaged] <smoser> GTFr0, http://paste.ubuntu.com/1617332/ is how you can get yourself a new initramfs <GTFr0> smoser: I added the nodes manually on the MAAS server <smoser> then i suspect you are right. <smoser> about the netowkr drivers <smoser> if you can see console (serial consoel or vga) you can probably verify that <GTFr0> hrm, not using Mellanox ethernet cards. Oddly enough, these are Proliant Gen8 servers with i350 ethernet onboard <GTFr0> afaik, i350 uses the standard igb driver, and if I do the standard Ubuntu server install, it sees the ethernet interfaces just fine <GTFr0> and I don't think it's a DHCP issue, because the nodes will boot PXE <GTFr0> smoser: when they boot PXE, I can see the console, but all I see is a ubuntu login prompt and am not able to login to get dmesg or other diagnostic info <smoser> ah. <smoser> GTFr0, ok. so if you pxeboot in commissioning and get to a ubuntu login prompt <smoser> then you're definitely getting networking, as that is coming over iscsi <smoser> you can "backdoor" the ephemeral image so you can login <smoser> see info on how to do that at https://lists.launchpad.net/maas-devel/msg00817.html <smoser> and https://code.launchpad.net/~matsubara/maas/ephemeral-img-debugging-doc/+merge/143927 <matsubara> thanks smoser, that ping reminded me I need to chase evilnickveitch for a review :-) <evilnickveitch> oops! I'll do it tomorrow matsubara ! <matsubara> evilnickveitch, thanks! <michaela_> what exactly is a node? <EntropyWorks> bigjools: that makes sense. but it never sends the reboot command via IPMI. so I'm stuck now with 4 nodes waiting saying Commissioning. <EntropyWorks> Nice to see the Mellanox mlx4_en is going to be added. that has been a major headache <smoser> EntropyWorks, did you ever test that for me ? <smoser> EntropyWorks, https://code.launchpad.net/~smoser/ubuntu/raring/kmod/lp-1115710/+merge/146760 . put that mlx4.conf file in /etc/modprobe.d and then un-do any of the hacks you'vae done to get it loaded <smoser> then reboot and make sure networking works as expected <smoser> if we dont get that fix in, then you'll have the modules in your initramfs but you'll still not have networking because the _en wont get loaded. <EntropyWorks> smoser: haven't tried that but in precise and quanta the initrd.gz didn't actually contain the drivers so just adding that to /etc/modprobe.d wouldn't have done it. <smoser> understood <smoser> i'm asking you to test an installed system, really. <smoser> just to see if it comes up right if you dont have your custom udev rule or entry in /etc/modules (or some other manual way) <EntropyWorks> my fix was this for straight pxe installing. http://goo.gl/PfOZd now I'm looking at MAAS but haven't had much luck getting it to work. <smoser> EntropyWorks, right. <smoser> bu tafter you install <smoser> then what? <EntropyWorks> smoser: ok let me see about doing that. just grabbing your branch now bzr branch lp:~smoser/ubuntu/raring/kmod/lp-1115710 <smoser> all you really need is that mlx4.conf file into /etc/modprobe.d <smoser> that should be enough <smoser> EntropyWorks, and *thank you* for your help <EntropyWorks> I will also rem mlx4_en from /etc/modules which is something I believe i did in my late_command.sh <EntropyWorks> these machine take about 3 min to reboot. so here we go <smoser> right. <EntropyWorks> humm. mlx4_core 000:05:00.0: comand 0xc failed: fw status 0x40 <smoser> EntropyWorks, where do you see that ? <EntropyWorks> on the console <smoser> dmesg ? are the modules loaded? (lsmod | grep mlx4) <EntropyWorks> mlx4_core loaded but nothing else <EntropyWorks> I have a meeting so be back after that and will chat again <smoser> ok. can you try one other thing for me ? <smoser> ok. thank you. <EntropyWorks> smoser: back, what would you want next to be done? <smoser> hooray <smoser> ok <smoser> so you rebooted and mlx4_en was not loaded, right? <EntropyWorks> correct <smoser> so lets replace that mlx4.conf with <smoser> # mlx4_core should load mlx4_en (LP: #1115710). <smoser> install mlx4_core /sbin/modprobe --ignore-install mlx4_core; /sbin/modprobe mlx4_en; /sbin/modprobe mlx4_ib <ubot5> Launchpad bug 1115710 in MAAS "Mellanox mlx4_en network driver is not automatically loaded" [Critical,Triaged] https://launchpad.net/bugs/1115710 <smoser> and then reboot and see how we fare. <EntropyWorks> so just that whole line. and remove the softdep line? <smoser> remove the soft dep <smoser> and, yeah, one full line <EntropyWorks> ok rebooting again <EntropyWorks> nope. btw I wish I could see more than just this on the serial console http://paste.ubuntu.com/1618052/ . It hangs there until I get a login prompt <EntropyWorks> still not luck loading the mlx4_en <EntropyWorks> and in desg [ 8.031717] mlx4_core 0000:05:00.0: command 0xc failed: fw status = 0x40 <EntropyWorks> no mention of mlx4_en in desg <EntropyWorks> s/desg/dmesg/ <smoser> EntropyWorks, hm.. <smoser> so to see more on the console there, i tihnk you'll need to append console=ttyS0 <smoser> and that should function <smoser> but then you wont see the stuff on the vga console <smoser> can you try now rebooting after removing ml4x.conf entirely? <smoser> err... first can you just try running 'modprobe mlx4_core' <smoser> and seeing if networking _en gets loaded <EntropyWorks> let me unload mlx4_core and mlx4_en again ( did that by hand just a moment ago ) <smoser> i just dont get it. <smoser> with either of those mlx4.conf in place, i get both modules loaded in my vm. <smoser> (granted i dont have the hardware, but ... ) <EntropyWorks> doing that loaded both and the mlx4_ib and some other ib_mad ib_core <EntropyWorks> but doesn't seem to do the trick when rebooting <smoser> right. <smoser> and if we remove that, we *do* get mlx4_core loaded, right? <smoser> EntropyWorks, ^ . lets try <smoser> removing the mlx4.conf file entirely <smoser> and rebooting <smoser> see if we still see the message in dmesg <EntropyWorks> Ok removing that conf completely and will reboot <smoser> EntropyWorks, i really appreciate your time <smoser> i'm gonna have to run for a while. <smoser> if you can just fill me in here. <EntropyWorks> np, I'll be back tomorrow just /msg me and I will get it <EntropyWorks> this mlx4 issue has been a problem for a long time for me. <EntropyWorks> now if I could get MAAS to reboot a node... LOL <EntropyWorks> rebooted and mlx4_core was loaded but not the others <EntropyWorks> smoser: without /etc/modprobe.d/mlx4.conf only mlx4_core loaded <EntropyWorks> humm... <EntropyWorks> The directory containing the ephemeral images/info is missing (u'/var/lib/maas/ephemeral/quantal/ephemeral/amd64'). Make sure to run the script 'maas-import-pxe-files'. <EntropyWorks> but I do have a dir in there /var/lib/maas/ephemeral/quantal/ephemeral/amd64/20121017/ with disk.img, info, initrd.gz, linux, tgt.conf <EntropyWorks> and have run maas-import-pxe-files <EntropyWorks> what gives <bigjools> it takes a while for the re-scan of the files to happen <bigjools> the message should disappear within a few minutes <EntropyWorks> ok, I'll let it sit for a but and watch the logs. but why won't MAAS actually send the IPMI to the node to reboot? I have HP servers with iLO3 which is on a network reachable from the MAAS box. <bigjools> EntropyWorks: maas doesn't do "reboot", it does power on and power off <bigjools> power on when allocated and power off when deallocating <EntropyWorks> ok so I need to power off the machine so it can power it on then... <bigjools> EntropyWorks: what are you trying to achieve, at a higher level? <EntropyWorks> higher lever. get a rack of HP ProLiant SL390s into MAAS <bigjools> why do you need to reboot outside of the normal commissioning/allocation cycle? <EntropyWorks> well I just installed MAAS on one machine in the rack. I then went to add a node. but it never gets past Commissioning <smoser> EntropyWorks, yeah, that message doesn't like to go away some times. <smoser> EntropyWorks, and without any mlx4.conf, do we still see the "command 0xc failed" message in dmesg? <EntropyWorks> I know the machine work and could see each other because I had my own PXE setup that with a patch initrd.gz for the mlx4 <EntropyWorks> smoser: I think you do [ 7.955801] mlx4_core 0000:05:00.0: command 0xc failed: fw status = 0x40 <smoser> ok. so thats just a red herring then. <smoser> but our changes to that ocnfig file seem not to be doing anything. <smoser> just to be sure, you're p utting that file into '/etc/modprobe.d/mlx4.conf' <smoser> right? <EntropyWorks> bigjools: I need MAAS to actually do the commissioning/allocation cycle, it doesn't want to add any of the nodes. 2 nodes in this MAAS, 2 nodes offline <bigjools> EntropyWorks: oh is this part of ther trouble you're having with the mlx4? <EntropyWorks> bigjools: nope different problem <bigjools> smoser: we probably ought to put together a faq "why is my node not commissioning?" <EntropyWorks> smoser: when the file /etc/modprobe.d/mlx4.conf contains "install mlx4_core /sbin/modprobe --ignore-install mlx4_core; /sbin/modprobe mlx4_en; /sbin/modprobe mlx4_ib" it does not load the cisneroselizabeth@example.net. it will load the modules when "modprob mlx4_core" <EntropyWorks> by hand <smoser> right. <smoser> i just dont understand that. <EntropyWorks> the way I've been making life work is adding mlx4_en to /etc/modules <smoser> hm.. <smoser> maybe your initramfs has the 'modules' entry in it? <smoser> and the driver is then getting loaded in initramfs when it doesn't have that file <smoser> (i'm kind of grasping at this point, but i really dont understand it otherwise) <smoser> i just did this: <smoser> sudo modprobe "pci:v000015B3d00001010svfsdfbcfscfif" <smoser> and i get the mlx4_en loaded <smoser> (that matches one of the aliases) <EntropyWorks> so I could open my initrd.img-3.5.0-23-generic and poke inside I guess <EntropyWorks> but that should be stock. <smoser> EntropyWorks, well, if you update-initramfs <smoser> well, since you had that /etc/modules entry <smoser> it could/might get pulled into there <smoser> on an update-initramfs <EntropyWorks> I have not run that command yet <smoser> right <smoser> but it happens on kenrle install and such <EntropyWorks> humm. the kernel is installed before I add to /etc/modules <EntropyWorks> I'm betting <smoser> well, yes, but it gets updated lots of times. <smoser> do this: <EntropyWorks> yep I do it in my late_command.sh <smoser> lsinitramfs /boot/initrd.... | grep mlx <smoser> and i suspect/hope we see it there. <smoser> my theory is that if its there, then when modprobe comes up in root, it doesn't find it. <smoser> well, its already been loaded <smoser> so nothing tries to load it <EntropyWorks> it is there. both mlx4_core.ko and mlx4_en.ko <smoser> right. but you do not have the mlx4.conf in there. <smoser> so, put mlx4.conf in place <EntropyWorks> correct <smoser> then 'update-initramfs -u -k $(uname -r)' <smoser> and reboot <smoser> and again, thank you <smoser> i have to run <smoser> will check in later. <EntropyWorks> so I should put the file back in /etc/modprobe.d/mlx4.conf and then just run the command 'update-initramfs -u -k $(uname -r)' <EntropyWorks> bigjools: having some info for why a node is not Commissioning would be wonderful <bigjools> EntropyWorks: yes! It's a complicated area, a whole lot of stuff can go wrong :( <EntropyWorks> doing a tcpdump I know MAAS is sending something to the IP of the IPMI device. but what ever it is doesn't power on the server. <bigjools> was the bmc detected at enlistment? <bigjools> or are you configuring manually? <EntropyWorks> bigjools: using ipmitool -I lanplus -H 10.X.X.X -U Administrator -P foobar chassis power on <EntropyWorks> does turn the server on. <bigjools> ok compare with the power script that maas is using <EntropyWorks> where should I look for that :-) <bigjools> provisioningserver/power/templates IIRC <EntropyWorks> humm. I wonder if MAAS is expecting IPMI to be on the same interface as the machines network card. my IPMI is in iLO which is an out of bandwidth daughter card. which is on a different netwok than the machines NIC. the iLO has an IP address already and doesn't need one from MAAS <bigjools> no it doesn't expect that <bigjools> it just stores IP address <EntropyWorks> ok cool <bigjools> I expect it's a v1 / v2 problem #maas 2013-02-07 <EntropyWorks> it looks like your using bmc-config <EntropyWorks> which I don't know if I can get it to work right with iLO3 <bigjools> that's roaksoax's work :) <bigjools> he would know better than I <EntropyWorks> bigjools: humm /usr/share/maas/preseeds/enlist_userdata looks to be the place. but if I'm reading this it wants to modify the IPMI setting not just power off and on a machine <bigjools> that's the detection stuff <bigjools> not the power template <bigjools> you'll have an ipmi.template somewhere <EntropyWorks> ah <EntropyWorks> bigjools: I think I got it! without modify the template <EntropyWorks> modified /etc/freeipmi//freeipmi.conf and added driver-type LAN_2_0 <bigjools> nice <EntropyWorks> I think the IPMI config in the webgui should have a choice since someone may be in a mixed env <bigjools> well it is on a per-node basis <bigjools> we used to have more choice for ipmi IIRC but roaksoax changed it <EntropyWorks> yes and that is why it should be in the webgui so you could provision a driver-type LAN and then add another node and do driver-type LAN_2_0 <EntropyWorks> with out login into the MAAS server and modifying that /etc/freeipmi/freeipmi.conf to override the default of LAN <EntropyWorks> the underlying tool is ipmipower <EntropyWorks> great... note to self do not delete the last MAC address for a node. now I can't select it to remove it... <bigjools> oops <bigjools> please file a bug <bigjools> (you could add a dummy mac) <EntropyWorks> from the webgui I can't I only see the "(name)" which isn't a link <EntropyWorks> when a mac is there its "93:73:71:73:c1:47(name)" <EntropyWorks> and you have to click the mac address to delete or modify the node <bigjools> damn <smoser> EntropyWorks, so you still around ? <smoser> yeah, what i was saying was to just try putting that file into place and update-initramfs <smoser> and then reboot <EntropyWorks> yes <EntropyWorks> ok I think that worked. I'm rebooting that machine again just to check <EntropyWorks> bigjools: the link is there in the HTML but nothing for it to underline as a link. <bigjools> EntropyWorks: ok thanks <EntropyWorks> https://bugs.launchpad.net/maas/+bug/1117875 <ubot5> Launchpad bug 1117875 in MAAS "Removed MAC leaves node but can't edit or remove" [Undecided,New] <smoser> EntropyWorks, ok. this makes sense now. <smoser> at least i think. <smoser> after adding that rule (and removing entry in /etc/modules) we need to run 'update-initramfs'. <smoser> otherwise, the module would get loaded in the initramfs <smoser> and then the modprobe.d rules that we were applying only are put into affect when that module (mlx4_core) is installed. <smoser> and since it was already getting installed in the initramfs, the changes were not doing anything. <smoser> so... <EntropyWorks> $ lsinitramfs /boot/initrd.img-3.5.0-23-generic | grep mlx4 <EntropyWorks> etc/modprobe.d/mlx4.conf <EntropyWorks> lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/mellanox/mlx4 <EntropyWorks> lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_core.ko <EntropyWorks> lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko <smoser> i'd really apprecate it if you would put the soft dep one in place <smoser> then update-initramfs <EntropyWorks> ok <smoser> then reboot <smoser> and, cross your fingers, please <smoser> :) <EntropyWorks> humm <EntropyWorks> $ update-initramfs -u -k $(uname -r) <EntropyWorks> update-initramfs: Generating /boot/initrd.img-3.5.0-23-generic <EntropyWorks> FATAL: modprobe: softdep dependency loop encountered inserting mlx4_core <EntropyWorks> still want me to reboot? <EntropyWorks> it appears that it did not add mlx4_en to the image... <EntropyWorks> rebooting anyway... <smoser> hm.. <smoser> shoot. i remember that. <smoser> that is odd. <EntropyWorks> only the mlx4_core was loaded <EntropyWorks> so that didn't work <bigjools> EntropyWorks: which version of maas are you using? I cannot reproduce your bug <smoser> right. EntropyWorks so lets try the whole update-initramfs process with the 'modprobe'. <smoser> er... with the 'install version <smoser> of mlx4.conf <EntropyWorks> bigjools: 0.1+bzr1269+dfsg-0ubuntu1 i'm running on quantal 12.10 <bigjools> EntropyWorks: from the stable PPA? <bigjools> oh is that the version in quantal <EntropyWorks> yea its the default in quantal I'm not using another PPA except to mess around with salt <bigjools> for me, it's the names that are linkified on the node list <bigjools> not the macs, so I can click on it happily <EntropyWorks> weird <bigjools> can you try the PPA version? it fixes a LOT of bugs and is about to get SRUed <EntropyWorks> I only installed MAAS yesterday on a clean system too <bigjools> https://launchpad.net/~maas-maintainers/+archive/stable/+packages <EntropyWorks> smoser: modifying the mlx4.conf again and initramfs for you and reboot <EntropyWorks> bigjools: nice! this one has the @%#$$T@# IPMI settings that was causing me to scream at my monitor <bigjools> EntropyWorks: \o/ <bigjools> I wondered why you were having trouble! <bigjools> keep forgetting all the old versions differences <EntropyWorks> *head to desk* <smoser> EntropyWorks, sorry for your pain. <smoser> did we get our modules loaded ? <smoser> i'm about to push this and ask for it to be loaded into raring. <EntropyWorks> smoser: well if it wasn't for that you wouldn't have me to trouble shoot the mlx4 issues so... i don't mind since that is one that really pissed me off for a while <smoser> yeah, fwiw, people generally seem to think taht the driver itself is just being stupid here. <smoser> that it isn't automatically loading stuff itself. <EntropyWorks> that worked. <smoser> woowhoo! <EntropyWorks> now just have to fix the initrd.gz that will get used for MAAS too :-) <EntropyWorks> $ lsmod | grep mlx4 <EntropyWorks> mlx4_en 63080 0 <EntropyWorks> mlx4_core 173435 1 mlx4_en <smoser> oh <smoser> and one more thing, EntropyWorks <smoser> you have functional network based on that, right ? <smoser> (just a little thing like "does it actually give you network" :) <EntropyWorks> yes networking works. <EntropyWorks> I wanted to see what happens if I unload the both and reload mlx4_en <EntropyWorks> that added more modules then before <EntropyWorks> mlx4_ib 57930 0 <EntropyWorks> mlx4_en 63080 0 <EntropyWorks> mlx4_core 173435 2 mlx4_ib,mlx4_en <EntropyWorks> ib_mad 47134 3 mlx4_ib,ib_cm,ib_sa <EntropyWorks> ib_core 82363 7 mlx4_ib,ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad <EntropyWorks> what i did was <EntropyWorks> modprobe -r mlx4_en <EntropyWorks> modprobe -r mlx4_core <EntropyWorks> modprobe mlx4_en <EntropyWorks> well past time to leave the office. smoser catch you tomorrow if you need more mlx4 debugging <smoser> thanks again. <smoser> EntropyWorks, right. i tested that. <smoser> seems generally functional. <smoser> but thanks for thinking <EntropyWorks> what ports on the MAAS server need to be open by the way? would be nice to have a ufw config in /etc/applications.d/ <EntropyWorks> next problem I have to solve is what image has the /etc/apt/sources.list or where I need to add the http_proxy info for MAAS to work in my env <sam_one> morning kool kats <EntropyWorks> anyone have a quicker way to add machines then doing it via the webgui? <EntropyWorks> the nodes now have gotten Allocated but since they appear to not have working networking I'm suck. I can't delete the node from the gui either <EntropyWorks> lovely <EntropyWorks> btw this command just fails: sudo maas createsuperuser <EntropyWorks> http://paste.ubuntu.com/1622243/ <bigjools> EntropyWorks: eummmm that's really odd, I've never seen anything like that. Something is screwed in your system. <bigjools> you can add machines via the command line or API <EntropyWorks> bigjools: I was able to remove them via the maas-cli <bigjools> great <EntropyWorks> the createsuperuser thing however I have no clue. <bigjools> me neither <bigjools> my only guess is that somehow your PPA install clashes with the quantal package <bigjools> can you file a bug please and supply as much info as you can about your installation (versions etc) <EntropyWorks> maybe. it was happening before in the quantal packages too <EntropyWorks> sure <bigjools> oh weird <bigjools> matsubara, hi <EntropyWorks> bigjools: humm yea I'm think something just is wrong with my server. not sure what. going to just reload from scratch and try again. <bigjools> EntropyWorks: try LC_ALL=C sudo maas createsuperuser <EntropyWorks> nope <bigjools> you're missing locale info <bigjools> is it even set? <EntropyWorks> wonder if my python is screwed someplace <bigjools> echo $LC_ALL <EntropyWorks> not set <bigjools> ok C doesn't work <bigjools> set it to a valid locale <bigjools> en_US for example <bigjools> bugger <bigjools> you need sudo -E as well <bigjools> preserves env <EntropyWorks> yea, but no good either <EntropyWorks> something messed up with my install. check this out <EntropyWorks> $ maas-cli <EntropyWorks> Error: no arguments given. <EntropyWorks> Run /usr/lib/python2.7/dist-packages/maascli/__main__.py --help for usage details. <EntropyWorks> I'm got to do the sane thing and nuke this machine and try again :-) <bigjools> so, LC_ALL=en_US sudo -E maas createsuperuser <bigjools> doesn't work? <EntropyWorks> ah! yes that prompted me! <EntropyWorks> yea I see when I run locale <EntropyWorks> LC_ALL= <EntropyWorks> and LANGUAGE= <EntropyWorks> so thats causing me the issue i guess <EntropyWorks> just reset it to en_US.UTF-8 logged out then back in and tada command works <bigjools> cool #maas 2013-02-08 <EntropyWorks> which is the better doc to follow? http://maas.ubuntu.com/docs/quantal/install.html or https://maas.readthedocs.org/en/latest/_build/ <bigjools> the former <EntropyWorks> thanks <bigjools> no problem, I am interested in your progress <EntropyWorks> can I get away without have the squashfs image for quantal? since I had to set IMPORT_SQUASHFS=0 to get 'sudo maas-import-pxe-files' to complete with out error <bigjools> Yes, it should not be getting downloaded, it doesn't work <EntropyWorks> since I updated my initrd.gz to have the mlx4 drivers looks like i have some proxy issues since the commissioning needs to apt-get some items. is there a template that I could change so I could use my own internal mirror? <bigjools> if you're using the latest PPA package it has support to set a mirror or a proxy in the config page <roaksoax> robbiew: <roaksoax> err <roaksoax> sorry <roaksoax> rvba: <roaksoax> ping <EntropyWorks> bigjools: so the issue wasn't the proxy. looked closer it is bind / named requiring dnssec-validation. <EntropyWorks> bigjools: my setup also required me to setup a forwarder for dns. <EntropyWorks> bigjools: dang, dns works now but that didn't work for me. the first Commissioning stage doesn't seem to use the proxy settings <EntropyWorks> I need to find the initrd.gz and most likely tweek it <EntropyWorks> i would like to change which apt mirror its using since I have my own local mirror <EntropyWorks> ok ran 'juju bootstrap' and machines rebooted and 'Allocated to admin' but of course no mlx4_en driver so no networking... fustrating <EntropyWorks> what image is this booting? <EntropyWorks> I have tried to modify these but that didn't work <EntropyWorks> /var/lib/maas/ephemeral/quantal/ephemeral/amd64/20121017/ initrd.gz <EntropyWorks> /var/lib/maas/tftp/amd64/generic/quantal/install/initrd.gz <EntropyWorks> /var/lib/maas/tftp/amd64/generic/quantal/commissioning/initrd.gz <EntropyWorks> then tried the ephemeral disk.img too but still nada #maas 2013-02-10 <bigjools> smoser, roaksoax: can you confirm the solution mentioned here? https://bugs.launchpad.net/maas/+bug/1119594 <ubot5> Launchpad bug 1119594 in MAAS "Node install fails when sda has pre-existing md raid arrays" [Undecided,New] #maas 2013-02-11 <roaksoax> bigjools: we'll have to test that with machine with md raid arrays <bigjools> roaksoax: fair enough. <roaksoax> bigjools: and I don't know whether we wanna do that <roaksoax> bigjools: btw.. is there any ETA on the cluster url thing for the preseeds? <bigjools> roaksoax: this week <roaksoax> bigjools: ack! thanks <roaksoax> bigjools: btw.. are we going to start releasing trunk for precise? <bigjools> roaksoax: no! <roaksoax> bigjools: one of the things that came up last week was the ability to have custom kernel command lines <bigjools> I know <roaksoax> as they do some costumization some times <roaksoax> ack <bigjools> people want their cake and eat it - a stable LTS but at the same time all the shiny new features <bigjools> from my PoV I am happy to release trunk to precise but you'd have to work hard with the techboard, no? <roaksoax> bigjools: oh I meant PPA <roaksoax> not actually SRU it <bigjools> ok <bigjools> we can do a backports PPA <roaksoax> yeah that's what I meant <bigjools> no problems with that :) <bigjools> roaksoax: do you know anything about this? https://bugs.launchpad.net/maas/+bug/1087183 <ubot5> Launchpad bug 1087183 in maas (Ubuntu) "MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'" [High,Confirmed] <roaksoax> bigjools: i know the context, but I think the removal of it didn't really fix the issue james was having <roaksoax> you'll need to check with him and scott just to be sure <bigjools> ok I'll leave it incomplete, thanks <bigjools> hey, you have nothing better to do on a Sunday night? :) <roaksoax> bigjools: ok so this wewk I'll make sure all the MAAS dependencies are in precise, and then hopefully upload maas by thursday, wtih 2 fixes I want to fix. 1. ipmi stuff, 2. fix a packaging bug on upgrade <bigjools> woohoo <bigjools> roaksoax: what about testing with Django? <roaksoax> bigjools: heh.. was doing homework, then learning how to dj, and now preparing my notes from last week to send to you tomorrow <roaksoax> bigjools: I think we are good with that. ScottK did say he was fine with it if the techboard approved it.But i don't know who can test it apart from the maas team <roaksoax> bigjools: so i'll check on that this week too <bigjools> roaksoax: well we need to run up some other Django apps with the patched Django <roaksoax> yeah, bigjools horizon (openstack) could be a good example <bigjools> ok <roaksoax> bigjools: anyways, I'm off, have a good day! <roaksoax> oh btw.. thanks again for the help last week! <bigjools> roaksoax: pleasure, have a good evening <roaksoax> thanks! <Wout> I'm having an issue with maas where my node names are not consitent with the ip address <Wout> for example: 192-168-30-55.master = 575.979.1648 not 575.979.1648 <Wout> nslookup on maas master doesn't use local server <bigjools> you might be falling foul of a problem in the dhcp server <bigjools> where it assigns different IPs to the same machine <bigjools> depending on whether it's requesting IP from the BIOS or from the OS <Wout> The OS <Wout> what does maas use for dhcp? <Wout> sorry DNS <Wout> what does it use for dns <bigjools> bind <Wout> does maas create a mac <-> reserve somewhere? <bigjools> what do you mean by reserve? <Wout> I can see dns name in /etc/bind/maas/zone.30.168.192.in-addr.arpa <Wout> it say's ip 55 in range 192.168.30 is DNS name 192-168-30-55.master <bigjools> maas scans the leases file that the DHCP server maintains, and keeps track of IP vs MAC in its database <Wout> where does maas link 575.979.1648 to a mac address <bigjools> you probably have this issue with the dhcp server: https://bugs.launchpad.net/maas/+bug/1069570 <ubot5> Launchpad bug 1069570 in MAAS "1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think..." [Critical,Triaged] <Wout> I'l look at that <bigjools> someone is looking at a fix on the dhcp server <Wout> wow looking at the bu report... <Wout> this s*cks <Wout> I'm implementing this now <roaksoax> bigjools: btw we didn't experience that bug above <Wout> Anyone in heer been able to de pxe maas with uefi? <Wout> MAAS doesn't create the boot files foor uefi systems <Wout> I need to enlist a uefi only system <Wout> How would I do that? <Wout> Anyone there? <Wout> Hello?? <bigjools> smoser: can you respond to my comment here please? https://bugs.launchpad.net/maas/+bug/1116331 <ubot5> Launchpad bug 1116331 in MAAS "proxy not used in ephemeral or commissioning" [Medium,In progress] <bigjools> Oh I see you commented on the MP <bigjools> BTW if you open up the expander at the bottom of the MP page you can set it to WIP immediately so no emails get sent containing bogus diffs <bigjools> how can I help mwhudson? <mwhudson> bigjools: hello <mwhudson> bigjools: i have a task which i've just realized sounds very much like maas <mwhudson> or rather, one small part of maas <mwhudson> so i wonder if can reuse it or at least see how it does it <mwhudson> bigjools: basically i think i want a super dumb netinstaller <bigjools> this is pretty much what maas does, yes <mwhudson> that can be configured to say "when the device with mac address $foo boots, dump this disk image onto it" <bigjools> maas is in control of the boot <bigjools> it powers up the machine <bigjools> so if you can deal with that, maas will work nicely <bigjools> it'll even put your ssh key on there <mwhudson> this is for lava, automated testing stuff <mwhudson> i' <mwhudson> for now i'll be doing stuff over serial console to control the node after it boots the desired image i think <bigjools> so maas serves up different boot images depending on what state it thinks the node is in <bigjools> therefore unless maas thinks the node is booting, it won't do much <bigjools> maas also uses cloud-init <mwhudson> right <mwhudson> i think perhaps i only want a very small part of maas <bigjools> it would be hard to use maas in bits <mwhudson> there is always c-c c-v :) <bigjools> all you need then is a tftp server, a dhcp server, and some boot images <mwhudson> probably <mwhudson> but i don't want the default netinstaller initrd i think <bigjools> and frig the kernel options so it starts a net install <mwhudson> i just want something that splats a tarball into a partition <bigjools> we use iscsi <mwhudson> none of this packaging stuff <bigjools> ah <bigjools> maas doesn't do that - yet. should be ready RSN <mwhudson> oh ok <bigjools> it currently runs d-i <mwhudson> ah <bigjools> but work is afoot to splat an image <mwhudson> so you don't have anything like an "ami for maas"? <bigjools> no <mwhudson> ok <mwhudson> ffs <bigjools> not yet <bigjools> give it a week :) <mwhudson> why am i always at the bleeding edge of everything :) <mwhudson> bigjools: what does maas use for dhcp/tftp etc? <bigjools> internal TFTP implementation, but ISC DHCP <mwhudson> ok <bigjools> bleeding edge = on the curve man <mwhudson> bigjools: is pserv the tftp bit? <bigjools> mwhudson: yes, twisted process <mwhudson> cool <mwhudson> bigjools: and all this is doing the stuff that cobbler used to do? <bigjools> mwhudson: kinda. <roaksoax> bigjools: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2013-February/001012.html <bigjools> roaksoax: I saw that, good stuff <roaksoax> bigjools: ok cool, so what you think about the GeneircIPAddressField? <bigjools> roaksoax: yes we could pull that in. I don't like doing that though. <mwhudson> bigjools: generally maas uses the regular initrds that the distro provides? <roaksoax> mwhudson: it does <bigjools> mwhudson: yes <mwhudson> ok * mwhudson has found class TFTPBackend(FilesystemSynchronousBackend): now <roaksoax> bigjools: so what do you think we should do? <bigjools> mwhudson: the tftp server is tightly integrated to maas as it serves up different things depending on the state of the node <mwhudson> yeah <bigjools> roaksoax: do we have a choice? <bigjools> roaksoax: can we carry it as a quilt patch? <roaksoax> bigjools: yes <roaksoax> bigjools: that's what *should* be done <bigjools> roaksoax: probably easiest <bigjools> since it's easiest to remove <roaksoax> indeed <bigjools> and it's distro-specific, not upstream issue <bigjools> mwhudson: you could serve up an ephemeral image to a booting node and use a cloud-init script to splat a tarball <roaksoax> bigjools: yeah, so ;et's do that. That's the easiest, to ship it as a patch <bigjools> roaksoax: sweet <bigjools> mwhudson: then you can just boot something and maas will install it <bigjools> all highly unsupported :) #maas 2013-02-12 <mwhudson> i guess that's not _completely_ insane <bigjools> mwhudson: well normally each node needs a commissioning boot step before maas recognises it; but you want to just boot-n-go <mwhudson> bigjools: yeah, the more i think about it, i think i can only be inspired by maas, not directly use it <mwhudson> this week, at least <bigjools> mwhudson: if you let it do some lifting it may save you a lot of work <mwhudson> that is also true <mwhudson> i guess there is little harm in me spending half a day trying to implement it myself <mwhudson> because even if i throw all my code away, doing that will help me understand maas <bigjools> heh <bigjools> ping if you need help <smoser> roaksoax, bigjools i am pretty sure we do, by default, want to destroy all data on a machine. <bigjools> +1 <smoser> at least that is what we have been basically doing previously <smoser> so whatever debian preseed for "WIPE THE STUFF" is, we want that. <roaksoax> smoser: ack! cool <smoser> roaksoax, i dont think it would be a bad feature request at some point to have an option to leave persistent data on volumes specified somehow. <roaksoax> smoser: right, I agree it would be a nice to have feature <racedo> hi, i'm installing maas on precise, last version of it (1.2+bzr1351+dfs) and every time I do a maas-import-pxe-files, it seems it works but in the celery.log I get a HTTPError * racedo pasting that on pastebin <racedo> http://pastebin.ubuntu.com/1640257/ <racedo> and the actual maas-import-pxe-files <racedo> http://pastebin.ubuntu.com/1640265/ <racedo> any help appreciated <racedo> and I think because of this, this message sits in the UI forever: "The region controller does not know whether any boot images have been imported yet. If this message does not disappear in 5 minutes" <roaksoax> racedo: thgat;sbecause there are no raring commissioning images <roaksoax> racedo: check /etc/maas/import_pxe_files and disable raring <roaksoax> and see if it comes back again <racedo> hey roaksoax! raring wasn't there: http://pastebin.ubuntu.com/1640463/ <roaksoax> racedo: yeah I think there might be a bug. Could you please file one? <racedo> sure, will definitely do <racedo> thanks roaksoax #maas 2013-02-13 <snovaki> Hi! is there any docs about how to add high availability to a maas installation or how to backup/restore a maas instance? i don't want maas to be a single point of failure... <ingard> hi guys. Is there a way I can easily change the sources.list file that is installed on nodes? <roaksoax> allenap: howdy! so arenyou guys gonna do the FPI work? <roaksoax> rvba ^^ <roaksoax> (all of it?) <rvba> Hi roaksoax, allenap is working on this, he will reply to you in just a sec ;) <racedo> hey roaksoax morning <roaksoax> rvba: cool thanks <roaksoax> racedo: Hi Ramon <racedo> roaksoax: could it be that python-django-piston in precise doesn't get well with django 1.4 as someone has pointed out in maas-devel? <racedo> i think that's what's breaking my maas on precise <allenap> roaksoax: I'm going to do some of it, so that you & smoser can switch between the traditional and fp installers. <roaksoax> allenap: ack! thanks <roaksoax> racedo: uhmmm <racedo> roaksoax: your latest changelog for the quantal version mentions _is_string depending on the django version which is what i'm hiting i think <rvba> racedo: I came to the same conclusion, see my comment on https://bugs.launchpad.net/maas/+bug/1124085 <ubot5> Launchpad bug 1124085 in MAAS "HTTP Error in celery.log when maas-import-pxe-files is run" [Undecided,Invalid] <roaksoax> rvba: could you please take a look at ^^ <racedo> oh thanks rvba <roaksoax> racedo: he is probably best to help you with celery :-) <racedo> ok, so no django 1.4 for maas <racedo> roaksoax: gracias :) <roaksoax> :-) <rvba> racedo: the problem is the version of piston in precise. maas itself works with django 1.4. <racedo> but i cannot install the ubuntu2 version of piston <racedo> in precise <racedo> well, i can but it breaks something else <racedo> rvba: ok, i got it, my django 1.4 comes from the ubuntu-cloud repository, all i need then is to get the django 1.3.1 from maas-maintainers <racedo> rvba: thanks again <rvba> racedo: np <rvba> roaksoax: btw, I wanted to ask you, were are we at with the new images? (bug 1115178 and bug 1115175) <ubot5> bug 1115178 in MAAS "Raring ephemeral info not available on https://maas.ubuntu.com/images/" [Critical,Triaged] https://launchpad.net/bugs/1115178 <ubot5> bug 1115175 in MAAS "The armhf highbank installer for raring is not available on http://ports.ubuntu.com" [Critical,Triaged] https://launchpad.net/bugs/1115175 <roaksoax> rvba: I'm waiting on those images too :) <roaksoax> smoser: any ETA on the raring images? <rvba> roaksoax: okay :) <smoser> roaksoax, raring dailies are there now <roaksoax> rvba: ^^ <roaksoax> smoser: awesome thnaks! <smoser> roaksoax, by design, the released would not come until at least we claimed something as release (alpha or beta or release) <roaksoax> smoser: ack! <rvba> smoser: thanks <smoser> roaksoax, i'm interested in seeing/knowing if the raring ephemerals actually boot successfully now with mellanox <smoser> they should <roaksoax> smoser: are you going to SRU bug #1115710 ? <ubot5> bug 1115710 in module-init-tools (Ubuntu Quantal) "Mellanox mlx4_en network driver is not automatically loaded" [Medium,Triaged] https://launchpad.net/bugs/1115710 <roaksoax> smoser: heh :) <roaksoax> smoser: so this would not only work for the the ephemeral images, but also for the actual initrd right? <roaksoax> smoser: i think this needs to be SRU'd <smoser> well, the raring installer should have this fix <smoser> so raring should work all the way through. <smoser> now, the ephemeral image change, i think i've already shoved in to dailies for quantal and precise <smoser> but the installer changes will have to be sru'd. <smoser> (2 ephemeral changes: 1.) patch-or-have module-init-tools with fix 2.) build NETBOOT initramfs <rvba> roaksoax: I'm told raring won't have alpha releasesâ¦ and the beta is scheduled March 28th. Does this mean we will have to wait until that day to get a working MAAS package? <smoser> over time, the sru of module-init-tools will get into installer images so that should work for quantal and precise also <smoser> but, yeah, we need to verify that that works <smoser> and then also really verify that it works on precise <smoser> and then sur <smoser> sur <smoser> sru <roaksoax> smoser: right but for precise, if we SRU now it should become available for 12.03.2 <roaksoax> err <roaksoax> 12.04.2 <roaksoax> rvba: really? i though we were having alpha releases <smoser> roaksoax, i'm all for sru. lyou an fil out the sru template. <smoser> but really, i want to see that the fix *ACTUALLY WORKS* <smoser> before doing so <smoser> :) <roaksoax> smoser: yeah... which means that we need hardware to test it with :/ <smoser> EntropyWorks, ^ <smoser> EntropyWorks has such hardware.... <rvba> roaksoax: well, you tell meâ¦ Alpha 2 is tomorrow. But https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule says "for opt-in flavors". <roaksoax> rvba: i guess that would work for server then <rvba> roaksoax: then this is great news, it means we will have the images tomorrow :) <roaksoax> smoser: could you confirm ^^ <smoser> rvba, we can have "released" images of raring tomorrow if you want to do that. <smoser> those are not official ubuntu deliverables <smoser> (and there are not actually *any* required deliverables prior to release any more... odd.. but true) <smoser> if you want that, we can do it. we just basically promote a daily build to "released" and slap a label on it. <smoser> so we can do that for "alpha-2" tomorrow. <rvba> smoser: well, we need something to fix 1115178. Either we have images or we fix the script so that it does not blow up when some images cannot be found. <smoser> but i need someone to actually *test* stuff and verifiy it works. <smoser> rvba, well someone shouldn't have committed code that didnt work! <rvba> smoser: I'm 100% with you on this one. <smoser> it is good to get those images out, though, and if we can get an enlistment test with a daily from even today, then we can mark it "released" <smoser> i'd like to hvae the ame kernel as the cloud-images alpha-2, but other than that, i have no real concern. <rvba> roaksoax: what's
{'channel': 'maas', 'month': 2}