[00:43] SpamapS, sweet! [00:44] SpamapS, i think you meant cs:~clint-fewbar/oneiric/munin-node ;-) [00:44] hmm.. that brings up some interesting questions that the implementation doesn't take into account [00:45] namely subordinate charms from one series deployed onto a primary of a different series [00:45] niemeyer, ^ === WALoeIII_ is now known as WALoeIII === robbiew1 is now known as robbiew [06:26] hazmat: re the series question for subs.. it would be pretty stupid of people do that IMO. ;) [06:27] hazmat: perhaps we can just trust people to make wise decisions. [06:30] <_mup_> Bug #981387 was filed: juju status does not respect JUJU_ENV < https://launchpad.net/bugs/981387 > [07:21] * SpamapS feels like a mad scientist right now.. creating a puppetmaster and puppet subordinate charms [07:46] SpamapS, nice [08:01] got certificate signing working [08:02] time for sleep [08:02] subordinates are so awesome [08:02] bcsaller: seriously, ^5 on getting this done [08:03] SpamapS: really nice to hear :) [08:11] I'm following the 12.04 guide on wiki.ubuntu.com/ServerTeam/MAAS/juju. It's a bit out of date, should I install from the ppa or from the repository? [08:22] Morning juju ! [08:32] jkyle: i'm not 100% on this, but https://juju.ubuntu.com/ says if you have 11.10 then use the repos one, which might be fine for 12.04 [09:15] Is there a way to have juju choose a given flavor/arch/ vms instances instead of picking the default one define in environment.yaml ? [13:19] question [13:19] would something like rsnapshot make a good charm? [13:21] or maybe an rsnapshot frontend [13:21] hmm [13:27] I suppose rsnapshot would defeat the purpose of juju, which seeks to encapsulate services [13:27] so you don't have to hoard over precious config files [13:28] irc is a great scratch pad for talking to yourself :p === nijaba_ is now known as nijaba [15:10] melmoth: yes, that is called constraints [15:10] melmoth: https://juju.ubuntu.com/docs/constraints.html [15:10] melmoth: you will need the latest juju from the PPA for that. [15:11] shazzner: rsnapshot is still useful I think [15:11] shazzner: it would be a fantastic subordinate charm. [15:11] hmm SpamapS any idea how can i chekc if there s an "image-type" constraint of some sort ? [15:12] i would like to be able to change the defautl-image-id, i see there s a ec2-instance-type constraint, but it s not the thing i want to choose [15:13] melmoth: they're listed at that url [15:14] melmoth: image id is not used, and default-image-id is not recommended unless you're using a private cloud, since juju will automatically look up the arch/release/region/etc. to find the official ubuntu image for you [15:20] what i would like is, to be able to get a vm matchin a given release/arch so that s what i need. [15:20] the idea would be, you work in support, you got a core file you need to run gdb on. What you want is access to a machine with the same os version/arch and lib version as the one [15:20] used to generate the core [15:21] melmoth: right, --constraints "arch=amd64" cs:oneiric/foo [15:22] melmoth: the release is determined by the charm [15:22] melmoth: so that charms can be written without lots of conditional logic for changes between releases, they're maintained as a branch per release of Ubuntu. [15:23] hmmm. [15:23] i would love to be able to call a charm with arguments. [15:23] or may be, should i write a on the fly charm generator script ? :) [15:24] i think you might be missing some other subleties if you want to do that [15:26] oh, i m sure i missing a lot of juju subtelty. I only start to look at it seriously today [15:26] a charm really isnt a machine, its most like a service that runs on that macine, so you arent deploying ubuntu your deploying apache , apache detaermines if it wants ubuntu or not [15:29] now with your given example above, i think one step higher in the feed chain may be what your looking for, as in MAAS [15:30] hmm, havent looked at it right now (but i though it was to deploy bare metal boxes) [15:30] or a combo of MAAS for the OS/lib versions then a charm with gdb tools etc [15:32] melmoth: yes , but your wanting to manuipulate the bacre metal os features, so it makes sense, juju is service orchastration , there is a fine line, but i think your gonna end up with a combo of them [15:34] i need to think about it. but there sure seems to be something that wants to be use there. [15:34] e.g. if i need to provision a i386 box with glibc5++ thats a MAAS task , if i need gdb with all its goodies setup thats a juju task :) [15:35] but juju will happlily setup an os underneith its self [15:36] if needed, just what it needs though, maybe not what you do [15:37] i was just thinking of having a way to have the installed box get a copy of the "customer" /etc/apt-sources.list and dpkg -l to re apt-get everything it can. [15:37] plus gdb and all debug symbols package on top of that [15:38] melmoth: yea i mean dont get me wrong, it probably could be wrangled into doing it, just as MAAS could probably do a little orcastration [15:38] (wich is also why i was hoping there was a way to give arguments to a charm) [15:38] i was just giving ya another piece to the puzzle :) [15:38] that s good, i need to look at maas anyway. [15:39] and you can give it options [15:39] i wouldent say arguments [15:39] but charms have options [15:40] juju set blah -e amazon [15:40] or something like that [15:43] and dont forget that maas and juju work as a team, so dont try to shove it all in one or the other either :) there is some gray area IMHO , but also i'm still very new to this too, only been charming about a month now [15:46] i ll need to talk about it with the support guys anyway :) [15:46] i think there s a beer calling for me downstair...will be back later on [15:46] :) [15:48] melmoth: charms can have arguments, defined by config.yaml [15:50] hrm we need to move this out of drafts.. [15:50] https://juju.ubuntu.com/docs/drafts/service-config.html [15:50] been implemented for about 9 months :) [15:50] SpamapS: its so nice to be back on linux, i forget how easy it is to setup everything, like i've got my zend studio back installed, dev env's going , my ~/Projects git tree back etc etc etc , if i could just get used to the damned hotkeys again [15:50] melmoth: anyway that details it [15:50] imbrandon: :-D I know, I felt the same way [15:51] any puppet fans, check out cs:~clint-fewbar/oneiric/puppetmaster and cs:~clint-fewbar/oneiric/puppet .. subordinates ftw :) [15:51] * SpamapS disappears [15:51] l8tr [16:54] thanks for the url ! === daker is now known as daker_ [18:13] good place to ask maas+juju questions? [18:15] I've got a maas server up, registered two nodes, they pxe booted. But now I'm stuck. they show as "commissioning" in the maas webui, but the docs say I have to click "accept and commission". An option that does not exist in my UI [18:15] https://wiki.ubuntu.com/ServerTeam/MAAS/AddNodes [18:23] i dont see where it says to click accept and commision, it looks like under the heading where it says "In order to use Juju you have to Accept & Commission the nodes for use." there is a "add node" [18:24] pictured [18:25] jkyle: in other words your fine, they will finish commissioning hopefully and you read an extra word in there in panic :) [18:26] imbrandon: check the very bottom image [18:26] imbrandon: "Click the Accept & Commission button" [18:26] with image [18:26] sure thats once you can click on them [18:26] you have not made it that far have you ? [18:26] they were pxe'd last night, and my ILOM shows it's completed successfully and has a prompt [18:27] ahhh [18:27] imbrandon: yep, that's teh step I'm at. I've added them, I have 2 nodes in a list, I pxe booted them, they've installed 12.04...but web ui still has them in "commissioning" mode [18:28] I suspect the network isn't set up right, but I don't know how to get shell access to the node (e.g. default username/passes) [18:28] tried ubuntu/ubuntu [18:28] i doubt you can at this point, leaste i would hope not [18:29] have you tried rebooting the webuinode ? [18:29] force it to refresh [18:31] just restarted. no effect. [18:32] fun, might poke robbie when he is around but i'm guessing its not a network issue as maas controls all that [18:32] its just plain dhcp [18:33] imbrandon: true, but I'd wager maas makes a lot of assumptions...like a flat network. mines a bit more complicated. I tried to see what ip was served by doing a dig @localhost [18:33] but it doesn't resolve [18:34] jkyle: well that is likely the issue then maas controls the network [18:34] as it stands, I can't even delete the nodes (button grayed out). [18:34] if it dont you end up with this :) [18:34] so, it'd be helpful to get into the node's shell and manually fix the network (and confirm that's the issue) then I can integrate some post flight scripts knowing what the problem is ;) [18:35] guess single usermode is always an option hehe [18:35] i highkly doubt thats possible, if it is its a glaring security hole [18:36] the passwd hash is in the preseed. I bet dollars to donuts that the default pass is somewhere in the maas settings file [18:36] really though to confim it just spin it up with it controlling the network like it wants [18:36] jkyle: i'm sure [18:37] imbrandon: it's not that maas is not controlling the network config, it's that my network is not a flat network [18:37] right, i dont see the diffrence here, put it on its own [18:37] it dont matter what your current setup is, i'm not talking about that [18:38] just isolate maas and see if thats the issue [18:40] trying to figure out too many variables at one time will give you grey hair, get maas working the way IT wants to, then if you want to try and intergrate it into a non standard setup cool, but you konw the ropes at that poit [18:40] point* [18:40] see what i'm getting at ? [18:42] anyhow its the weekend and i'm the only chicken in the house atm it seems, sorry cant be much more help than that, but yea short of a MAAS dude poppin up i'd break it down to the simplest terms instead of trying to smash into a node, thats just my 0.2c [18:43] should just have to unplug, reconf the ui and re-pxe boot, hour-ish [18:43] pxe install dont take long [18:49] imbrandon: yeah, I getcha. quicker to boot to single user though than reconfigure switch and router profiles [18:50] :) [18:51] interestingly enough, when I rebooted the node, it loaded the _old_ OS. even though it was showing a 12.04 prompt. maas must use a headless boot as a holding phase or something [18:54] pxe stops at: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [19:11] might have to fall back to just cobbler and my own scripts for initiali orchastration [19:11] jkyle: IIRC, maas works like orchestra, and they shouldn't install the OS until you've bootstrapped with juju [19:12] SpamapS: what I'm stuck at is the node is booted, it's in the maas interface, but it just says "commissioning" and the docs don't reflect the options I have at this point [19:12] e.g., it says click "Accept & Commision" button before moving forward with juju...but no such button exists [19:13] I'll just move forward a bit and assume it's not necessary...see if juju just "works" [19:15] jkyle: perhaps the docs are out of sync w/ late changes [19:21] k, I'm at juju status here: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju [19:21] juju status returns "Could not find AWS_ACCESS_KEY_ID" [19:22] is your env still type ec2 ? [19:22] juju status -e maas returns => Invalid environment 'maas' [19:22] ppa juju ? [19:23] jkyle: dpkg -l juju, you need at least bzr504 [19:23] ah, my bad, dropped an 's' on the environment conf [19:25] I have 504 [19:26] jkyle: I'd recommend trying the PPA. The version in the PPA *should* land in 12.04 before the release, and has a number of minor fixes for the maas provider. [19:27] alrighty, now I get: juju environment not found: is the environment bootstrapped? [19:27] SpamapS: I'm using the ppa version [19:27] so is it bootstraped ? heh [19:28] well, I've followed all the directions to date [19:28] jkyle: I'm guessing your environments.yaml is not quite right [19:28] I copied and pasted from https://wiki.ubuntu.com/ServerTeam/MAAS/Juju and replaced with the appropriate values [19:29] it return success ? when you ran juju bootstrap -e maas ? [19:30] lemme take it from the top. I probably missed a step [19:30] :P [19:31] jkyle: if the docs are wrong, please do suggest fixes (or just edit the wiki directly :) [19:32] I get this from bootstrap => Unexpected Error interacting with provider: 409 CONFLICT [19:32] and, whaddya know, bug with my _exact_ situation hehe: https://answers.launchpad.net/maas/+question/193473 [19:33] I'll totally edit if i figure out what's amiss [19:34] are maas and juju tightly coupled? [19:34] that bug describes what I had yesterday, with teh start node button. but the latest maas update removes the start button. now just a grayed out delete [19:37] jkyle: they should be independent, though juju is the only way to acquire/provision nodes in maas right now IIRC [19:37] maybe I should just fall back on cobbler and play with juju or chef [19:38] maas looks promising, but without docs to back it it's a guessing game [19:39] true, its still only days old too :) [19:40] I'll be hanging with some maas folks @ the Openstack conference [19:43] jkyle: the maas folks often hang in here of #juju-dev [19:45] jkyle: conflict usually means you don't have enough nodes, or you haven't accepted the enlistment in the webui [19:45] ie, not enough nodes in Ready state [19:45] yeah, I was talking with the package maintainer yesterday. very helpful [19:45] Daviey: right, problem is...there's no button to accept them ;) [19:46] jkyle: yes there is :) [19:46] Daviey: backscroll, he's run into some confusion in the docs [19:46] ah [19:46] jkyle: Daviey can help you :) [19:47] \o/ [19:48] https://bugs.launchpad.net/maas/+bug/981845 [19:48] <_mup_> Bug #981845: "Accept & Commission" button does not exist < https://launchpad.net/bugs/981845 > [19:48] jkyle: Remember that MAAS isn't yet included in a supported release.. So be fair :) [19:48] * imbrandon trails off to provision 10 servers in hp cloud and start a ndb charm maybe [19:48] Daviey: oh, I realize I'm on the bleeding edge of the bleeding edge [19:48] jkyle: ok.. i know your problem :) [19:50] Daviey: even as new as it is, so far it's easier to grok than crowbar when the information is found :) [19:50] sudo mount /var/lib/maas/ephemeral/precise/server/amd64/20120328/disk.img /mnt/ ; sudo chroot /mnt ; sudo apt-get update ; sudo apt-get install cloud-init ; exit ; sudo umount /mnt [19:50] restart the node. [19:51] Daviey: oh I think I saw that bug.. pre-seed is messed up? [19:51] jkyle: super! [19:51] SpamapS: No.. it's a self fixing bug at release time. [19:51] :) [19:52] SpamapS: We can't make people update the daily ephemeral image on a daily basis, so we are using milestones.. The most recent milestone is beta-2, which doesn't have a recent enough cloud-init. [19:52] So when final is canned, it'll fix itself. [19:52] on a side, there could be issues with pulling images from ephemeral for some companies [19:53] I mean for the bootstrap phase. are there plans to pull those in locally? [19:53] jkyle: right.. next cycle we are going to make it so it can run entirely offline. [19:53] Daviey: *ahhhhh* [19:53] (TBD at UDS>) [19:54] jkyle: it's a one time process, right.. it only imports them when you run command. You could work around it if needed, by importing from usb media, or something [19:55] apt-get update fails on most of the mirrors [19:59] [19:59] Expires header problems. :-P [19:59] ok, back to my Saturday [19:59] jkyle: good luck :) [20:01] thanks! [21:26] hmm, stuck too with https://answers.launchpad.net/maas/+question/193473 (and me too, i did not have a Accept & Commission button)