[03:03] <_mup_> Bug #1195537 was filed: "type: local" doesn't work in host with kernel option 'ds=nocloud' === defunctzombie is now known as defunctzombie_zz === efries_ is now known as efries [08:57] Anyone else seen this with juju-core? http://pb.daviey.com/WKch/ [09:01] evilnickveitch: Hey, I see the docs are updated.. but i noticed https://juju.ubuntu.com/resources/ the menu on the left doesn't work [10:15] Daviey -ok, will look at that [10:32] MAAS. Adding nodes | http://askubuntu.com/q/313790 [12:18] good morning and happy friday all, anyone around? [12:26] hmm perhaps not, I've got an issue, trying to update/upgrade a charm I have deployed due to additional config elements i've added to a config.yaml for that charm [12:27] turns out the /var/lib/juju/units//charm contents are not being updated === wedgwood_away is now known as wedgwood [13:05] still crickets? [13:08] Akira1: did you the value in the /revision file? [13:10] hmm actually no! [13:11] however, everytime I attempt an upgrade, it is incrementing the internal revision [13:11] i.e. this was earlier: 2013-06-28 08:01:54,406 unit:cdh4-master/0: charm.upgrade DEBUG: Replacing charm local:precise/cdh4-17 with local:precise/cdh4-18. [13:11] 2013-06-28 08:01:54,415 unit:cdh4-master/0: charm.upgrade DEBUG: Charm has been upgraded to local:precise/cdh4-18. [13:12] i'm honestly not entirely sure what is in the charm cache at this point, the hook scripts are missing things that should have been there in every revision [13:12] is there a way I can workaround this and force update the hooks on each deployed service unit manually? [13:14] well I am not sure. Might be a good idea to wait for one of the more seasoned folks to jump in. :) [13:14] fair enough ;) [13:18] everything had been working swimmingly until last night =/ [13:18] Akira1: my (go) juju upgrade-charm has a --force option, not sure what it actually does though :) [13:19] i bump the number in the revision file sometimes to get it to update stuff [13:19] (locally) [13:19] well my understanding was they'll hash out most things [13:20] basically what is happening here is we keep on needing to add config params [13:20] so we keep updating config.yaml, and updating the hook to deal with the new params [13:20] i've done it about 6 times now [13:20] we had to use juju set --config= to get the new config values in [13:20] but the params i added last night aren't getting picked up [13:21] I inherited all this stuff from someone else so I didn't do this from scratch [13:21] the hook script is missing a config-changed hook =/ [13:25] Akira1: the unit isn't in an error state is it? [13:25] it sure is now [13:25] i think juju queues up hook runs until you resolve it [13:25] so juju resolved may resume upgrades [13:26] not completely sure :) [13:26] im giving that a shot now too [13:26] i was doing resolve -retries all night [13:26] heh [13:28] so that does make things run again [13:28] and fail [13:28] it is so weird, I'm actually on the service unit itself, blowing up teh charm dir [13:28] forcing it to redownload it [13:28] and it redownloads the wrong one everytime [13:29] bit you increase the revision number in the revision file? [13:29] s/bit/did [13:31] you know [13:31] you might be on to something here [13:32] my revision # in the charm was out of sync with what juju thought it had [13:32] when you do a juju upgrade-charm it will increment the number no matter what [13:32] so I was on local:precise/cdh4-20 even though my revision file said 10 [13:32] i just bumped up the value in revision to 30 [13:33] and the juju dry-run says it will upgrade: 2013-06-28 08:31:29,783 INFO Service would be upgraded from charm 'local:precise/cdh4-20' to 'local:precise/cdh4-30' [13:33] we have problems because they are multiple people on different machines doing stuff with the local juju repo [13:33] *there [13:33] similar type of stuff? [13:33] well lets cross our fingers [13:33] well you guys don't have to, but I sure as hell am [13:34] yeah :) [13:34] omg omg [13:34] i think this worked! [13:34] that sure is messed up [13:34] woot [13:35] so in the juju docs somewhere it mentions local repos causing weirdness if you have multiple people using them [13:35] im going to have to dig that up [13:35] imho it's something that juju should just support [13:35] juju site got updated last night [13:35] so a bunch of google'd links are 404s now [13:35] although i was wondering if we could run our own juju repository [13:36] ooh [13:36] well anytime you have something like that, you could try and fake out the remote repo [13:36] or maybe use launchpad? [13:36] *shrug* [13:36] it'd be pretty neat to be able to pull from git or something too [13:37] since we obviously have our own git repo, svn, etc [13:37] yeah, no bzr pls :) [13:37] :) [13:37] you guys know if anyone is doing any consulting in this space? [13:38] i've got 6 days left with this team and I'm afraid juju is going to die with me when i leave [13:39] maybe canonical? [13:39] yeah im thinking of calling them on monday [13:39] as with any services org, I'm sure they will SAY they can do something [13:39] and then send someone out who never saw it before [13:39] I saw that soooo many times with IBM [13:39] "oh sure we're sending you an expert!, only $250/hr!" [13:40] haha, well i think juju is pretty important to them [13:40] so hopefully they can help [13:41] yeah, we shall see [13:42] while folks are feeling chatty... what platform are you running against, have you tried this stuff against MaaS? [13:42] i'm using maas and things are going sort of swimmingly, but I get occasional http 401 errors from juju commands due to oauth failures [13:42] ec2 for us [13:43] was MaaS easy to set up? [13:44] actually, yes [13:44] I ran into a couple weird things [13:44] hey so we should have the doc 404 links fixed soon [13:44] awesome :) [13:45] with maas you can theoretically install it right from the OS boot media [13:45] but it doesn't work [13:45] using PXE? [13:45] yeah [13:45] but if you install that way you run into some chicken/egg scenarios with services coming up in the right order [13:46] so I blew up the machine, just installed 13.04 on it [13:46] THEN installed maas and it worked fantastically [13:46] waas the maas in 13.04 different than the one you used before? [13:47] this was setting up a fresh cluster jcastro [13:47] also in today's news, Frank has an OSX build [13:47] nice [13:47] some folks had submitted a bug on what i saw, and the bug was supposedly fixed [13:47] but alas, such was not the case [13:48] goju compiles fine on OS X - pretty cool [13:50] I think all we need to do now is find out where to put it [13:54] my OS X using colleagues would love it if they could go "brew install juju-client" or something similar [13:56] yep, that's what we should do [13:57] has homebrew pretty much taken over the package manager space on osx? [13:58] i'm not the best person to ask that, but it seems homebrew is preferred to macports in our office at least [13:59] these homebrew formulas look pretty simple [14:03] has anyone used Tsuru - http://www.tsuru.io/ ? “juju” is the default provisioner used by Tsuru and claims that "It’s a extended version of Juju, supporting Amazon’s Virtual Private Cloud (VPC) and Elastic Load Balancing (ELB)." === danilos__ is now known as danilos [14:23] hey EvilBill [14:23] I mean evilnickveitch [14:24] https://juju.ubuntu.com/docs/write-charms.html [14:24] do you think we could toss a 404 page up in the meantime? [14:24] something like "We've redone our docs, click here to get to the main page" [14:27] jcastro, sure. well, we should have a redirects file [14:27] Yeah but I don't think Marco gets back to work until like Monday right? [14:32] jcastro, yeah, I can put a dummy page in there to do a quick redirect and get it in before the next sync, that should hold us off until monday. [14:32] jcastro - are there any others you can think of? [14:34] sounds like someone needs to write some redirect rules! [14:34] btw new layout looks nice, good work guys :) [14:35] Akira1, thanks! We have the rules, but they are in someone's draft folder until they get back from holidays === defunctzombie_zz is now known as defunctzombie [14:39] jcastro - done that one, btw [14:41] * jcastro nods [14:42] evilnickveitch: ok, so what am I to do with getting-started? [14:42] you wanted that to redirect to the doc page right? [14:42] jcastro - yeah, that would be best [14:42] and the other getting started too [14:42] what other getting started? [14:43] I thought there were 2 in different places on j.u.c [14:43] ? [14:43] or maybe I am mad [14:43] https://juju.ubuntu.com/get-started/ [14:43] you're probably thinking of the one on normal ubuntu.com [14:43] ah, ok [14:44] jcastro - can you change that link? === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === frankban_ is now known as frankban [16:55] juju charm school in 5 minutes! [16:55] follow along on http://ubuntuonair.com [17:01] o/ [17:07] PLease post questions in this channel once we get started with the walkthrough [17:12] one sec [17:13] jcastro, looks to be back now [17:18] charms *are* code...so document them well :) [17:19] the guy with the stable net connection ends up being the worst one [17:19] I guess I'm scaring the crowd :) [17:19] stand by please! [17:20] where are the docs for the juju-tools? (unit-get etc.) [17:21] jcastro: it's fine for me [17:21] jcastro, back now [17:21] http://jujucharms.com/charms/precise/mongodb/hooks/hooks.py [17:22] Talking about docs, two quick plugs: [17:22] jcastro: It's me ;-) Hi! https://launchpad.net/~henninge [17:22] 1) The technical documentation for juju was *just* updated, and looks so much better: http://juju.ubuntu.com/docs [17:23] niemeyer: Hi! Yeah, but I am missing stuff or not finding it. [17:23] 2) I've you've missed it, last week I've published a long due high-level blog post about what juju is: http://blog.labix.org/2013/06/25/the-heart-of-juju [17:23] s/I've you've/If you've/ [17:23] The hooks docs seem to be gone as well. === pretto is now known as Prett0 [17:24] henninge: Fair point, we'll look into this and see if the new documentation has dropped content [17:24] Yeah I think that page is missing [17:25] I can't find it anywhere [17:25] fyi, old docs are still available at [17:25] http://jujucharms.com/docs/ [17:25] The writing a charm document seems pretty light [17:25] arosales: Great, thanks! [17:26] so if you find a missing page please file a bug via https://bugs.launchpad.net/juju-core/+filebug [17:26] yeah it's still under construction [17:26] the write charms part [17:26] jcastro, but all content should be in the new docs ported from the new docs [17:26] specifically the old docs and new docs should have the same content [17:26] if something is missing that is a valid bug [17:28] henninge, thanks for trying out our docs :-) [17:29] There we go again [17:29] Oh, it's back [17:29] There is also pages like this that now have dead links: [17:29] http://askubuntu.com/questions/82683/what-juju-charm-hooks-are-available-and-what-does-each-one-do [17:29] the rewrites haven't been deployed yet [17:30] those will be fixed on monday [17:30] redirects that is [17:30] jcastro: I'm seeing negronjl [17:30] robbiew, fixed ? [17:30] fixed [17:31] Ah, good to hear ;-) Great work [17:31] not fixed for me [17:31] nope [17:31] bingo! [17:31] yeah [17:32] No, it's fine now [17:32] jcastro: Do we have a fallback deployment of the docs? [17:32] jcastro: Having no docs whatsoever about a lot of those topics is a step backwards :( [17:32] niemeyer, yes the old docs are still at http://jujucharms.com/docs [17:33] arosales: Sweet, thanks [17:33] arosales: We need a link from the new docs there [17:33] niemeyer, please file any bugs you find for missing content [17:33] arosales: Well, that sounds backwrads [17:33] arosales: The content is there.. whoever is rewriting it should make sure that things are being dropped on the floor [17:33] are not [17:34] niemeyer, yup we'll udpate jujucharms.com when the docs have some more run time on juju.u.c [17:34] I can read [17:34] niemeyer, agreed [17:34] niemeyer, I am saying we have tried to port all content over [17:34] however if you notice missing content please let us know via a bug report [17:34] I don't think we ever documented the juju tools did we? [17:35] niemeyer, the task before going live with the new docs was to make sure all "old" content was available in the "new" docs [17:35] so all content ~should~ be there, but I am sure we will find some issues here and there as we use the new docs :-) [17:36] Where does private-address get set? Is that automatic? [17:37] arosales: Sorry, but that's not realistic [17:37] arosales: Just look at https://juju.ubuntu.com/docs/authors-charm-writing.html [17:37] arosales: and compare that with jujucharms.com/docs/charm.html [17:37] arosales: A *ton* of important information was dropped [17:38] and formatting there is a bit off as well [17:38] Yeah [17:38] niemeyer, that new doc is a straight copy of.. http://jujucharms.com/docs/write-charm.html [17:39] so we are still polishing :-) [17:39] yeah I don't think Nick considers the Writing a Charm section complete [17:39] but please file a bug even if it is saying content is missing from this page and we'll track it down [17:39] https://bugs.launchpad.net/juju-core/+filebug [17:39] I think this first drop was to concentrate on the end user bits [17:39] formatting, or any isses you see :-) [17:40] the docs are html5, if someone wants to just mass copy and paste and then mark up the old content and submit a MP that would be awesome [17:40] What was the hook you were editing? [17:40] negronjl, i'm here huckleberry [17:40] The one on the left [17:42] -joined [17:42] hazmat: Yeah, but it has been repositioned to be the only content about charms [17:43] Thanks, I got it ;-) [17:43] arosales: Sure, but that approach has some serious issues. Important content just went away [17:43] arosales: and external links are now broken [17:43] the links will be fixed on monday [17:43] niemeyer, yes redirects land on monday [17:44] niemeyer, we'll review our process, and the feedback is much appreciated [17:44] arosales, jcastro: That doesn't solve the problem if the content is different! [17:44] niemeyer, what I am saying now is if you notice something let us know via a bug and we'll work to make it better [17:45] arosales: For example, have a look at http://askubuntu.com/questions/82683/what-juju-charm-hooks-are-available-and-what-does-each-one-do and try to imagine how little sense will that response make with the new content that the links will point to [17:45] niemeyer: nick is working fulltime on the issues you're talking about [17:45] and unfortunately the guy who wrote the redirects went on vacation, so the links will be busted for 2 days, tops [17:45] let's discuss this after the charm school [17:46] So, I just did something like that today but I put the lib (or rather a python package) inside the hooks dir. [17:46] Since the hook is excuting in that directory, it will find it. [17:46] w/o messing with pythonpath [17:46] jcastro: I don't really have much else to say.. as I responded on juju@, I appreciate the new work, but suggest rolling back the new docs until they cover at least the most relevant portions of the old documentation [17:47] henninge: The hook executes on the charm directory [17:47] henninge, CHARM_DIR is available to hooks [17:47] oh, ok [17:47] henninge: The documentation is misleading.. I sent a note about that to the list a couple of days ago [17:47] henninge, for adding libraries.. ie $PYTHONPATH=$CHARM_DIR:$PYTHONPATH [17:47] niemeyer, yeah.. that section part was wrong [17:48] hazmat: A good, I'll try that [17:48] I guess that's what I remembered [17:51] yep [17:51] yes [17:51] jcastro, yes [17:54] we've expanded the hadoop charm over here to work with the cloudera cdh4 distribution, btw [17:54] wait, what! [17:54] Akira1: dude, that is awesome! [17:54] i haven't really looked at the OG one yet [17:54] but i've been expanding the configs and stuff like that to make it work [17:54] somehow the charm is missing the config changed hook [17:55] it is pretty slick and works great [17:56] one thing we can't figure out is how to deploy a secondary name node on another instance, right now the secondary namenode stuff runs on the same box as the primary namenode which is kind of a no-no [17:57] yeah that'd be slick wouldn't it... [17:58] sadly im not sure we did it that way... [17:58] big paste inc: [17:58] configure_sources () { [17:58] source=`config-get source` [17:58] juju-log "Configuring hadoop using Cloudera repo..." [17:58] wget -q \ [17:58] https://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/cloudera.list \ [17:58] -P /etc/apt/sources.list.d [17:58] wget -O - \ [17:58] https://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/archive.key \ [17:58] | apt-key add - [17:58] apt-get update [17:58] } [17:59] sweetaction [18:03] you guys going to run out of time before you talk about the monitoring interface [18:03] ? [18:03] Akira1: yes [18:04] :) [18:04] bah, that is one thing i actually want to hear about as i've been struggling with it :) [18:05] may i suggest that as a topic for another one of these screencast thingies? [18:05] yes, absolutely!! [18:08] :) [18:09] yeah, do that [18:09] :-P [18:09] i've got nagios, nrpe, etc [18:09] lp:charm-helpers [18:11] Thanks guys! [18:11] yeah, epic presentation, thanks [18:11] \o/ [18:11] m_3: can you pass me along the youtube url for the recording? [18:11] hey [18:12] i've inherited all this juju stuff from a predecessor, he was working on sweet stuff [18:12] Are these sessions available for watching afterwards? I'll be on holiday in two weeks. [18:12] integration with saltstack for one [18:12] Akira1: cool! [18:12] henninge: yep, I keep a list here: https://juju.ubuntu.com/resources/videos/ [18:13] Akira1: that is awesome man [18:13] henninge: yes... we're working on an actual youtube channel, but they're all available from juju.ubuntu.com/resources/videos [18:13] ah, jinx [18:13] like i said WAY earlier, i've been left with a mess heh [18:13] well hopefully we can help! [18:13] i started touching this stuff 4 weeks ago [18:14] and now I'm moving on so i'm trying to leave the team with as much solidity as possible [18:14] m_3: I need the youtube url for the videos page please [18:15] jcastro, m_3: thanks [18:16] henninge: np... thanks for hanging! [18:16] jcastro: dude, I'm looking for it [18:16] http://www.youtube.com/watch?feature=player_embedded&v=08dOs3eO04M [18:16] aha [18:16] it's linked from ubuntuonair of course [18:16] I have a basic question: Is this all done using the new juju (juju-core)? I am still using 0.7 because I had some problems. [18:17] i still use 0.6.1 [18:17] so, *shrug*? [18:17] henninge: the one thing we don't have in -core is the local lxc provider [18:17] for everything else, you want to use juju-core [18:17] henninge: mixed actually... depends on which series you're on [18:18] Akira1: you'll want to upgrade to .7 [18:18] on precise, I run 0.7... on raring, I run 1.10.0 [18:18] Akira1: yes, definitely upgrade from 0.6.1 to 0.7! [18:18] ok, my workstation is raring, the server is precise. [18:19] henninge: haha, yeah... that's pretty common [18:19] but am i currently missing something using 0.7? Will it still get updates? [18:20] henninge: it's EOL'd, so we're trying to switch everybody to 1.x [18:20] all new development is happening in 1.x [18:20] hmmmmmmmmmmm [18:20] i'll have to check that out [18:20] what I expected ;) [18:20] i'll go look at a changelog [18:20] henninge: really it depends on what you're doing honestly... most things work fine in 1.x [18:20] no lxc support is the biggest gap atm [18:21] note that we now have a nice mac client for 1.x series! [18:21] is 1.x still python or is that go? [18:21] 1.x is go [18:21] cool [18:21] that coming along ok? [18:21] yup... it's moving nicely [18:21] sweet [18:21] m_3: will 1.x get lxc support eventually? [18:21] biggest problem atm is packaging... otherwise the juju bits are working fine [18:21] i've been giving a few presentations internally about juju, we're a kind of small company, only about 30k employees... [18:22] henninge: like this next month we hope [18:22] henninge: yup, it's on the nearterm roadmap... with us going "you done yet?" every day! [18:22] :-D [18:22] haha [18:22] You guys rock! [18:22] Akira1: let us know if we can help with presentation material or content [18:22] too late! :-P [18:23] I really like juju and it's exactly what I need here. So, thanks. [18:23] we can go over the monitoring stuff outside of regular charmschools too [18:23] I gave my last presentation to mumbai this morning [18:23] henninge: awesome! [18:23] I had a question way way way way earlier in the day, prolly before you guys were up [18:23] Akira1: dang, well we should totally hook you up [18:23] which of you work for canonical? [18:23] well yes :) I'm on US pacific time atm [18:24] I'm on monster energy drink time [18:24] several in the channel... I do as well as jcastro [18:24] since my cdh4 charm blew up on me last night but i fixed it this am ;) [18:24] are any of you affiliated with the consulting/services arm? [18:24] Akira1: I'm wondering what you did with the jdk version... [18:24] I submitted an inquiry out to them via their shoddy web portal, we might be looking for some paid assistance [18:25] right now everything is working with openjdk even if it isn't advised [18:25] Akira1: we're on the products side of the house... negronjl is canonical consulting though [18:25] Akira1: we can certainly put you in touch with the right folks [18:25] in fact, my juju deployed cluster is actually humming along smoother/faster than our older cluster that was manually deployed [18:25] that being said, i've made a bunch of hacks to get stuff working [18:25] Akira1: great news! I've been really dreading integrating the oracle versions [18:26] tons of things in the charm aren't necessary best practices for config [18:26] so my config.yaml is now... bigger... [18:26] yeah, that comes along [18:26] and i have some issues due to maas too [18:26] im sure i'll figure some of it out eventually [18:26] sometimes this hadoop stuff causes you to do things that arent very... shall we say, service orchestration-y [18:27] ha! was just going to ask you which provider you were running on [18:27] yeah i inherited about 170 legacy physical servers [18:27] hey so I don't know who you'd talk to wrt. consulting [18:27] Akira1: let us know what you had to do outside-of-paradigm... we can really cover a lot with config and constraints [18:27] negronjl: whom should Akira1 contact? [18:28] I think we made negronjl late to another meeting... soudned like he had to run [18:28] m_3: the maas template doesn't mount all the local storage, so I do use maas tags to constrain to a few known nodes [18:29] since my hadoop nodes have additional local storage [18:29] but I actually mount the storage after provisioning [18:29] it all works but it isnt' 100% automagical [18:29] right... gotcha [18:30] and the big thing that could use fixing is the secondary namenode thing [18:30] there're some specs in place for more control of local storage in the 1.x go versions [18:30] thing is im not sure what relation would define that [18:30] dunno where it landed in priority though [18:30] Akira1: pm me your contact info and I''ll have someone contact you asap [18:32]