[00:51] <bkerensa> marcoceppi: ping
[00:52] <bkerensa> 2013-05-23 17:51:54,962 INFO Starting networking...
[00:52] <bkerensa> status: Unknown job: lxc-net
[00:52] <bkerensa> 2013-05-23 17:51:54,967 ERROR Problem checking status of lxc-net upstart job.
[00:52] <bkerensa> any ideas?
[00:53] <marcoceppi> bkerensa: make sure you have 0.7 installed
[00:53] <bkerensa> marcoceppi: I do looks like I still had the ppa too
[00:53] <bkerensa> marcoceppi: ok still doing it with 0.7 and ppa purged
[00:53] <bkerensa> :D
[00:54]  * marcoceppi tries local provider with pyjuju
[00:56] <marcoceppi> bkerensa: raring? I'm not able to replicate
[00:56] <bkerensa> marcoceppi: saucy
[00:56] <bkerensa> :)
[00:56] <bkerensa> whats with people still using raring ;p
[00:57] <marcoceppi> Ah, I'd recommend opening a bug. I'll spin up a saucy vm to give it a shot but I wouldn't be surprised if lxc in saucy has changed
[00:58] <bkerensa> kk
[00:58] <bkerensa> marcoceppi: this would be a juju bug though
[00:58] <bkerensa> right?
[01:00] <marcoceppi> bkerensa: yeah, though I don't think it'll be fixed as local provider should (is scheduled to) be completed this cycle for juju-core. So that'd be what people use
[01:00] <marcoceppi> But it won't hurt to file a bug
[01:00] <bkerensa> marcoceppi: and until such time as its fixed how can i deploy locally?
[01:00] <bkerensa> :D
[01:01] <bkerensa> I need to fix my charm
[01:01] <bkerensa> ;p
[01:01] <marcoceppi> bkerensa: Raring :P
[01:02] <marcoceppi> Or, you could spin up a raring ec2 machine and deploy locally on that. Half joke/serious suggestion.
[01:02] <bkerensa> heh
[01:02] <bkerensa> if only rackspace was working
[01:02] <bkerensa> =/
[01:02] <bkerensa> I got free rackspace for two years and no juju support... first world problem
[01:04] <marcoceppi> bkerensa: You could spin up a free rackspace machine then deploy using the local provider on that. We do something similar on EC2 to test local provder in our automated testing
[01:04] <bkerensa> hmm
[01:04] <marcoceppi> Or any machine that supports LXC in the kernel
[01:05] <bkerensa> ahh a raring machine yeah
[01:05] <bkerensa> I guess I'll do that
[02:51] <mwhudson> um, using the haproxy charm were do log messages go?
[08:48] <ehg_> hi guys, i'm using go juju, but would like to switch to pyjuju to set ec2-zone constraints - is it possible to switch between them like that?
[11:40] <marcoceppi> ehg: You can switch if you have juju-0.7 installed. However, you can't switch on an already deployed environment. juju-0.7 and juju-core deployments aren't compatible but they can be installed side-by-side and managed using `update-alternatives --config juju`
[11:59] <ehg> marcoceppi: thanks - that's a shame, gojuju seems to be much more reliable - the only things i need from pyjuju are zone constraints
[12:00] <ehg> do you know if they're in the roadmap anywhere? if not, i might try and implement them myself :)
[12:00] <marcoceppi> ehg: While I'm sure they're aware of it (as they're always moving to make up for features that haven't been ported yet) if you want to open a bug for it it'll help prioritze that feature
[12:01] <ehg> cool, will do. i'm really liking juju btw, thanks!
[13:08] <paraglade> is it possible to install the keystone (openstack) charm with the grizzly release using Precise series (12.04 LTS)?  I have tried several different settings for the 'openstack-origin' config setting and have not been able to figure it out.
[13:13] <marcoceppi> jamespage: ahasenack ^
[13:13] <jamespage> paraglade, yes
[13:13] <jamespage> paraglade, but the updated version is still in final testing
[13:14] <jamespage> paraglade, lp:~openstack-charmers/charms/precise/keystone/ha-support
[13:17] <paraglade> cool thanks I will give that a try.  I have been having fun showing my peers how juju can standup openstack in 15 minutes as apposed to weeks :). Now I am getting the "now lets see you do that using grizzly"
[13:19] <jamespage> paraglade, hoping to get the grizzly updates landed this week
[13:20] <jamespage> paraglade, just working through upgrade testing (folsom->grizzly)
[13:20] <AskUbuntu> cannot get latest charm revision when ttying to deploy a local charm | http://askubuntu.com/q/299502
[13:37] <dpb1> Hi m_3: do you think you could finish up a review on: https://code.launchpad.net/~davidpbritton/charms/precise/landscape-client/add-landscape-relation
[13:39] <marcoceppi> dpb1: He's at a conference this week
[13:39] <dpb1> marcoceppi: thx, is there anyone else around that can review?  It's been sitting a month, and it's a pretty easy change. :)
[13:40] <marcoceppi> dpb1: Yeah, if you assign it to "charmers" for review it'll jump in the review queue. I'll see if I can give it a look over today though, given how old it is
[13:40] <dpb1> marcoceppi: done
[13:40] <dpb1> marcoceppi: and thx. :)
[14:43] <nfoata> Hi everyone, i'm trying juju (0.7 python) on Amazon EC2, I notice that the tag name stay empty and I do not see any juju constraint for tags. By any chance, someone lnows if this is possible or not, Thanks in advance
[14:58] <jamespage> nfoata, I don't think the ec2 provider supports tags
[15:03] <nfoata> thanks jamespage for your answer. indeed, i am seeing the python source code and I do not see anything concerning tag (/usr/share/pyshared/juju/providers/ec2/launch.py)
[15:03] <nfoata> so it's reaaly seem not provided for now (maybe later)
[15:03] <jamespage> nfoata, ec2 has no concept of tags
[15:03] <jamespage> tags are a MAAS provider concept
[15:04] <nfoata> when you create on amazon ec2 manually a VM you can add tag (key,value pairs)
[15:04] <jamespage> nfoata, ec2 supports the other constraints such as memory, cpu, instance-type etc....
[15:04] <jamespage> nfoata, hmm
[15:04] <jamespage> nfoata, that does not work so well with juju as its juju that creates the instances on ec2
[15:12] <nfoata> Thanks jamespage, for the other ones (cpu, instance-type, etc), I use the constraints and for the localization (region and default instance type) the environment.yaml and it works well. The tag name was just for improving the visibility into the amazon screen but it's not really important in the facts, so maybe at a next time. i had to go. Have a good weekend
[16:32] <rideh> what is this madness
[16:41] <jcastro> marcoceppi: got a sec?
[16:52] <marcoceppi> jcastro: finishing lunch. be with you in a few
[16:52] <jcastro> starting lunch
[16:53] <jcastro> https://juju.ubuntu.com/Events/
[16:53] <jcastro> basically  I added some text, but it's in the wrong spot, I need you to doublecheck my horrible tables on the wordpress page
[16:54] <marcoceppi> jcastro: np. will review in a min
[17:24] <marcoceppi> rideh: which madness do you speak of?
[17:37] <marcoceppi> jcastro: man you've really got to close your tags up
[17:41] <jcastro> hey so I inherited this page!
[17:41] <jcastro> was not my idea to use tables.
[17:41] <jcastro> but yeah I probably crufted it up
[17:48] <marcoceppi> tables are absolutely correct for displaying data in a grid
[17:48] <marcoceppi> but I still shame youuuuu
[17:49] <jcastro> that's fine, I'm not ashamed of not knowing how to use tables. :)
[18:30] <rideh> marcoceppi:  the entirety of this project, i just heard of it for the first time today… awesome project
[18:30] <jcastro> rideh: \o/
[18:44] <marcoceppi> rideh: welcome! Let us know if you have any questions!
[19:18] <wedgwood> marcoceppi: unless you've got anything to add to the reviews, I'm going to merge charm-helpers
[19:43] <marcoceppi> wedgwood: fire away
[19:47] <wedgwood> marcoceppi: thanks. done.
[21:11] <wedgwood> marcoceppi: m_3: where (if anywhere) is the integration testing work being done?
[21:12] <marcoceppi> wedgwood: what do you mean by that?
[21:12] <wedgwood> I mean is there any code yet to run integration tests?
[21:13] <marcoceppi> wedgwood: there's the juju-test (jitsu test) replacement, and there's charmtester which does our jenkins runs
[21:14] <marcoceppi> Which are you looking for exactly?
[21:14] <wedgwood> marcoceppi: just some idea of how things are shaping up.
[21:15] <wedgwood> marcoceppi: specifically, something to tell my team about organizing tests and how they'll run
[21:16] <marcoceppi> wedgwood: the charmtester is "stable" but there's lots of updates to be made to it this cycle. I just posted the first revision of the juju-test to the list, and will have an update about the whole testing harness framework thing next week - though that doesn't yet live in a repo. For the most part, executable in the tests/ directory, it can be whatever you want
[21:16] <marcoceppi> https://lists.ubuntu.com/archives/juju/2013-May/002478.html
[21:16] <wedgwood> ah. I hadn't gotten down to that mail folder yet
[21:17] <marcoceppi> wedgwood: it's more or less the same as the jitsu test stuff, very open ended. When your team starts using it I'm all ears for feedback
[21:19] <marcoceppi> I'm working on a testing "harness" which is basically exactly what charm-helpers is, just with functional testing in mind. So it's a python library with a shell interface that simplifies and abstracts a lot of the tedious testing stuff that currently lives in lib/test-helpers.sh
[21:19] <wedgwood> marcoceppi: thanks. we stayed away from jitsu to avoid depending on something that we knew wouldn't be maintained. I'm sure we'll have some feedback quite soon.
[21:20] <wedgwood> marcoceppi: awesome. I recommend you pull in the bits of the python helpers that were target at client-side.
[21:20]  * wedgwood gets the link
[21:21] <wedgwood> marcoceppi: marked "NOT IMPLEMENTED" http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/charmhelpers/__init__.py
[21:21] <marcoceppi> wedgwood: fantastic
[21:21] <marcoceppi> thanks for the link
[21:26] <wedgwood> ctrl-?ctrl-?meta-j