[09:20] <kyhwana> hrm, going through the juju getting started at https://juju.ubuntu.com/docs/getting-started.html in 12.04, trying to use lxc, in "In ~/.juju/environments.yaml, add a section for type "local":" I get error: environment "sample" has an unknown provider type "local" when I run juju bootstrap
[09:21] <kyhwana> (i've got LXC already setup with network bridging)
[11:24] <sidnei> kyhwana: the go port (1.x) does not support the local provider yet, you have to use the python version (0.7.x)
[13:04] <jcastro> Daviey: want to talk juju SRUs with me?
[13:05] <Daviey> jcastro: no.  But can do.
[13:05] <jcastro> hah
[13:05] <jcastro> G+?
[13:05] <Daviey> jcastro: OK
[13:05] <Daviey> jcastro: you initiate ?
[13:06] <jcastro> it's ringing
[13:06] <Daviey> is it?
[13:24] <jcastro> mgz: ping
[13:33] <fdehay> Hi Do you know if juju1.10 supports ec2-uri parameter in environments.yml for ec2 type cloud that are not ec2 (ie cloudstack)?
[13:52] <mgz> jcastro: hey
[13:52] <jcastro> heya
[13:52] <jcastro> so ... let's talk backport/SRU/whatever of everything to LTS
[13:52] <jcastro> https://news.ycombinator.com/item?id=5739061
[13:52] <jcastro> users are running into problems
[13:53] <jcastro> so I'm going to chase down the SRU for maas.
[13:53] <jcastro> and I'm thinking everything should be 12.04-able
[13:53] <mgz> so... we can probably take the juju-0.7 and juju-1.10 packages to backports, I don't see the value in working off older versions
[13:54] <jcastro> I agree
[13:54] <jcastro> Daviey had some concerns about the update-alternatives
[13:54] <jcastro> how would it work
[13:54] <jcastro> is it like the PPA where we'd still default to .7 but allow the switch to 1.10?
[13:54] <mgz> well, it currently leaves it on juju-0.7 by default
[13:55] <jcastro> that's fine
[13:55] <mgz> and reqires a user running a command to switch, so should be fine for the install from distro case with pyjuju
[13:55] <jcastro> that seems fine to me
[13:56] <Daviey> mgz: I was thinking it might make sense to backport co-installability aswell
[13:57] <mgz> yeah, we should just base off the raring work
[13:57] <jcastro> is .7 as an SRU and 1.10 as a backport a good idea? Or stick both in backports?
[13:58] <mgz> either sounds possible, whatever the distro guys prefer
[13:59] <jcastro> mgz: do you have time to drive this?
[13:59] <jcastro> I really have nothing to offer other than "we need to fix this, someone help me oh please god."
[14:01] <mgz> probably, but I can't do much past the putting a branch up for review, someone else with powers needs to do the kicking
[14:01] <jcastro> if you can get me a branch and CC me on it, I can hunt down and kick
[14:34] <fdehay> hi again, can someone help me with the differences between pyjuju and juju-core in terms of coverage in functionnality?
[14:37] <fdehay> ie: does juju-core support non-ec2 ec2 compatible cloud? (cloudstack) - I get an error using ec2-uri parameter in a new environemnt of type ec2
[14:45] <mgz> fdehay: don't think anyone has tested cloudstack specifically, but the ec2 and s3 endpoints are hardcoded to aws, yeah
[14:46] <mgz> if you want to install from source it would be reasonably easy to play with that, at least you can report a bug against juju-core
[14:47] <fdehay> thanks, we need to use cloudstack (internal cloud for now) so we will test juju using 0.7 for now I suppose
[14:48] <fdehay> I can try to report a bug againt  juju-core (never tried before :))
[14:50] <mgz> you have a launchpad account? just go to https://bugs.launchpad.net/juju-core/+filebug
[14:57] <fdehay> ok submitted https://bugs.launchpad.net/juju-core/+bug/1182508 hope it clear enough :)
[14:57] <_mup_> Bug #1182508: juju cannot connect to cloudstack (non-ec2 ec2 cloud) <cloudstack> <ec2> <juju-core:New> <https://launchpad.net/bugs/1182508>
[15:06] <wedgwood> marcoceppi: I remember at UDS we had someone offer to help with charm-helpers refactoring
[15:06] <wedgwood> marcoceppi: I can't recall who
[15:06] <marcoceppi> wedgwood: Was it one of the gui guys?
[15:07] <wedgwood> marcoceppi: may have been. if you don't know either I'll go back to the video
[15:07] <marcoceppi> wedgwood: Oh, during UDS. yeah, I can't recall but it should be in the video
[15:10] <wedgwood> marcoceppi: it's in the notes, thankfully. it was bac
[15:10] <marcoceppi> ah, perfect
[15:10] <wedgwood> bac: I'm ready to land a pile of changed in charm-helpers if you're interested in reviewing
[15:10] <wedgwood> s/changed/changes/
[15:11] <bac> wedgwood: otp.  be with you shortly
[16:04] <arosales> jcastro, I think roaksoax was motivated after yesterday's chat and wrote up
[16:04] <arosales> http://www.roaksoax.com/2013/05/getting-started-with-maas-and-juju
[16:20] <mattyw> in juju-core is there somewhere I can view the whole debug-log? I was supposed to watch my env come up using "juju debug-log" - but forgot and now it's bringing everything up
[16:28] <mattyw> ^^ /var/log/juju/all-machines.log
[16:40] <AskUbuntu> How can I see the juju-core debug-log without tailing it? | http://askubuntu.com/q/298273
[16:41] <marcoceppi> mattyw: thanks for documentating that on AU!
[16:46] <mattyw> marcoceppi, no problem, I was sure I'd been told to put stuff like that on AU
[16:46] <mattyw> marcoceppi, didn't realise there was a bot to put it here - that's cool
[16:46] <mattyw> AskUbuntu, I guess you're a bot?
[16:47] <marcoceppi> It is, but it's nice to have it in a "more visable" place, since Google doesn't index irclogs very well
[16:47] <sarnold> irc's only twenty years old, give them some time..
[16:54] <jcastro> sarnold: yeah but we also get metrics on AU
[16:54] <jcastro> so in say, 6 months if that question has 10k views, we know we suck at making that feature visible, etc.
[16:55] <sarnold> jcastro: heh, maybe, I've viewed a lot of questions just cause they sounded neat. :)
[16:55] <sarnold> 50 upvotes, yeah.. :)
[16:55] <jcastro> well then, a mindshare win on top of that, awww yeah!
[17:18] <mattyw> jcastro, you got a moment?
[17:24] <jcastro> I'm on a call but I can listen on IRC. :)
[18:11] <jcastro> hey marcoceppi
[18:12] <jcastro> with tinytiny rss almost done
[18:12] <marcoceppi> jcastro: yo
[18:12] <jcastro> all we're missing is a jabber charm
[18:12] <jcastro> "Big company shutting down services you use? No worries, I got your back."
[18:12] <marcoceppi> ejabberd would make a nice charm
[19:19] <sidnei> jcastro: did you see this one? http://www.holovaty.com/writing/aws-notes/
[19:21] <sidnei> jcastro: also unrelated, but i'd love to see a mention of juju on http://devopsweekly.com/
[19:23] <sidnei> marcoceppi: ^
[19:23] <marcoceppi> sidnei: Yeah, there was a HN article about it https://news.ycombinator.com/item?id=5738252 jcastro was all over it
[19:26] <sidnei> marcoceppi: what about the devops weekly one?
[19:27] <marcoceppi> sidnei: I'm not familiar with them, but it would probably be good to be mentioned on there
[19:28] <marcoceppi> Might be a good place to get mentioned when we have a stronger puppet/chef story since then seem to favor those a lot
[19:33] <adam_g> hmm
[19:34] <adam_g> hazmat, 0.7+bzr628+bzr629~raring1 from PPA is installing an empty package, similar to txzookeeper last week
[19:34] <hazmat> ugh
[19:34] <hazmat> adam_g, i don't think that's the issue here though, but noted, i'll take a look
[19:36] <adam_g> hazmat, nah, i just noticed a raring deployment failed because it was missing the config-get binary
[19:39] <adam_g> hazmat, actually maybe its not entirely empty (the agent at least is running) but the binaries are missing
[19:42] <adam_g> bins are going into /usr/lib/juju-0.7+bzr628+bzr629~raring1/bin/ instead of /usr/bin/
[19:43] <hazmat> looks like mgz tweaked the recipe...
[19:44] <hazmat> er.. the packaging. http://bazaar.launchpad.net/~juju/ubuntu/raring/juju/0.7/revision/41
[19:46] <hazmat> adam_g, i'm redoing the build now.. for precise since it failed..
[19:46] <hazmat> but i might need to revert on the packaging changes as well.. tbd
[19:50] <adam_g> hazmat, hmph, cant imagine how that packaging change would cause that
[19:51] <hazmat> adam_g, well it was previously doing 0.7+revno.. so there are some changes in there from the last 8hrs
[19:51] <hazmat> agreed its strange
[19:51] <hazmat> greetings KyleMacDonald
[19:51] <KyleMacDonald> hey dude
[20:39] <jcastro> marcoceppi: hey so
[20:39] <marcoceppi> jcastro: yeah?
[20:39] <jcastro> did the stack problem with removign drupal6 from the store get resolved?
[20:39] <marcoceppi> jcastro: no, I need lynxman to help out but he's not on IRC
[20:39] <marcoceppi> Since it's stacked on /his/ branch
[20:40] <jcastro> anyone have his contact info?
[20:41] <marcoceppi> jcastro: I don't, but based on his lp account I can assume his jabber is his email. If not I can just open a bug and assign it to him in hopes he gets it
[20:41] <jcastro> can you fire off an email?
[20:42] <jcastro> I think he'd just Do It.
[20:42] <marcoceppi> jcastro: yeah, firing now
[20:42] <jcastro> <3 thanks
[21:20] <arosales> marcoceppi, I don't see a drupal bug for the removal for the charm store
[21:20] <arosales> https://bugs.launchpad.net/charms/precise/+source/drupal6
[21:20] <arosales> marcoceppi, could you confirm
[21:21] <marcoceppi> arosales: created
[21:22] <arosales> marcoceppi, ok, perhaps it is taking some time to propagate to https://bugs.launchpad.net/charms/precise/+source/drupal6
[21:22] <marcoceppi> arosales: this is the actual link: https://bugs.launchpad.net/charms/+source/drupal6
[21:23] <arosales> ah ok so not specific to the precise branch
[21:23] <marcoceppi> the specific precise branch is "gone" due to unpromulgation, but it's still "technically" there because of the stacking issue
[21:24] <arosales> marcoceppi, gotcha. perhaps going forward we make the bug report and give x time for the maintainer to respond before pulling?
[21:25] <wedgwood> marcoceppi: bac: https://code.launchpad.net/~mew/charm-helpers/refactor-to-core/+merge/164980
[21:25] <marcoceppi> arosales: ack, though there are outstanding bugs since november ;)
[21:25] <arosales> marcoceppi, I think jcasto may also propose a similar idea to the list (for folks not here)
[21:25] <bac> wedgwood: thanks
[21:26] <wedgwood> it's enormous. for that I am sorry, but the individual commits are reasonable.
[21:26] <arosales> marcoceppi, true the meta name has been there for some time.
[21:26] <marcoceppi> wedgwood: I'll take a look as well for <standard peanut gallery> remarks
[21:26] <wedgwood> marcoceppi: you'll probably be more interested at the next round of commits where I add in the command-line tool
[21:27] <marcoceppi> wedgwood: definitely
[21:28] <arosales> marcoceppi, the main idea is to give maintainers a warning and an opportunity to respond.
[21:28] <marcoceppi> arosales: right, I understand as much
[21:30] <arosales> marcoceppi, thanks :-)
[21:30] <marcoceppi> Eager to start the store cleanup :)
[21:32] <arosales> marcoceppi, its all in the name of quality which is good.  :-) jcastro is tracking this particular work in https://trello.com/c/j2F2zsbY