[00:37] <marcoceppi> Term1nal: juju status?
[02:32] <mhall119> holy crap it worked!
[02:32] <jose> mhall119: what? what? I just heard an explosion!
[02:32] <mhall119> jose: it was my head
[02:33] <mhall119> juju just blew my mind :)
[02:33] <jose> haha, what did it just do?
[02:34] <mhall119> I deployed 5 services to 5 machines with all relations and it "just worked"
[02:35] <mhall119> even using haproxy, which I've never used before, I just deployed it, added a relation to my summit charm, and boom, it's scalable
[02:36] <mhall119> after fighting with charms and juju and lxc all week, I'm so happy right now
[02:36] <mhall119> jose: http://paste.ubuntu.com/7419267/ :)
[02:36] <mhall119> it's so pretty
[02:36] <rick_h_> mhall119: woot!
[02:37] <jose> cool!
[02:37]  * jose is excited to see that summit charm
[02:38] <sarnold> oooo
[02:38] <mhall119> jose: https://code.launchpad.net/~mhall119/summit/charm
[02:38] <jose> awesome!
[02:38]  * jose <3 summit
[10:56] <Tug> I have an error when running debug-hooks: duplicate session: shard1/0   Connection to ... closed.
[10:56] <Tug> I have no other session opened
[11:09] <Tug> Ok, I found a workaround here: https://bugs.launchpad.net/juju-core/+bug/1255502
[11:09] <_mup_> Bug #1255502: juju debug-hooks can fail with duplicate session <debug-hooks> <juju-core:Triaged> <https://launchpad.net/bugs/1255502>
[13:03] <cjohnston> marcoceppi: ping
[13:33] <lazyPower> cjohnston: he's out today
[13:34] <cjohnston> lazyPower: ack.. how good are you with amulet ;-)
[13:39] <lazyPower> Moderately good - I can try to answer your question :)
[13:40] <_benoit_> Any juju-core developper here ?
[13:40] <_benoit_> I am trying to find how I could reuse bits of the ec2 implementation in the outscale implementation
[13:41] <_benoit_> I saw that the types names of the ec2 implementation where not capitalized (exported) so I don't see how I could embed them for reuse
[13:45] <cjohnston> lazyPower: /27
[13:45] <cjohnston> sorry for the ping
[13:45] <lazyPower> no worries
[13:45] <lazyPower> whats up
[13:47] <cjohnston> lazyPower: so I have a test running.. and I am attempting to get the IP and port for the instance.. I get a KeyError on open-ports
[13:47] <cjohnston> lazyPower: L77 http://paste.ubuntu.com/7417300/ I guess it shows complete, then 2 seconds later is starts another deployment... L78 shows the output of a command that is being run by the test, where we are trying to get the IP address and the open ports.. the open ports dont exist yet for some reason.. L84 is that same command, and they exist there
[13:48] <lazyPower> can you link me to your test code?
[13:49] <cjohnston> lazyPower: http://bazaar.launchpad.net/~canonical-ci-engineering/uci-engine/trunk/view/head:/tests/test_ppa_assigner.py
[13:50] <lazyPower> interesting use of amulet
[13:51] <lazyPower> It may be running through the code before it's finished standing up. try adding a d.sentry.wait()
[13:51] <lazyPower> that will ensure the sentry units hang the text execution until the topology has 'settled'
[13:51] <cjohnston> how should we be using amulet?
[13:51] <lazyPower> s/text/test
[13:51] <lazyPower> this is by no mean's wrong, but you're the first person i've seen introduce an amulet wrapper class like this :) i like it
[13:52] <cjohnston> ack.. it wasn't me.. lol.. I can't take the credit
[13:52] <lazyPower> this is cool stuff, i'm going to pass this off to my team so they can take a look as well
[14:51] <rbasak> frankban: I cannot get juju-quickstart 1.3.2 as packaged working in Utopic. I've filed a bug on this.
[14:51] <rbasak> frankban: it may be a juju bug, I'm not sure. But this blocks an SRU to Trusty.
[14:59] <frankban> rbasak: what's the problem?
[15:01] <_benoit_> niemeyer: Hi
[15:01] <niemeyer> _benoit_: Heya
[15:01] <_benoit_> niemeyer: you seems to be owner of juju core so I would like to ask you what is the best way to integrate the Outscale cloud in juju-core
[15:01] <rbasak> frankban: details in bug 1317939. It just doesn't work.
[15:02] <_benoit_> niemeyer: It's mostly ec2 compatible but without s3
[15:02] <niemeyer> _benoit_: Hmmm.. can we catch up in ~1h?
[15:02] <_benoit_> niemeyer: yeah sure
[15:03] <niemeyer> _benoit_: I need to step out for lunch imminently
[15:03] <niemeyer> _benoit_: Thanks!
[17:30] <jcastro> ERROR state/api: websocket.Dial wss://10.0.3.1:17070/: dial tcp 10.0.3.1:17070: connection refused
[17:30] <jcastro> does anyone remember how to get around this?
[18:51] <avoine> oh oh, I think Rodney Quillo's new ansible release breaks all the charms that use it...
[18:59] <_benoit_> niemeyer: re
[18:59] <niemeyer> _benoit_: yo
[18:59] <_benoit_> niemeyer: should we go private to discuss this ?
[19:00] <_benoit_> niemeyer: first question do you have time right now ?
[19:00] <niemeyer> _benoit_: I do have some
[19:00] <niemeyer> _benoit_: If it's about juju, we can stay here, or go to #juju-dev
[19:09] <tvansteenburgh> avoine: how so?
[19:10] <avoine> in 1.6 ansible try to read file that starts with { as json
[19:10] <avoine> but charm-helpers use yaml
[19:10] <avoine> tvansteenburgh: ^
[19:12] <lazyPower> well this is weird, the rails-charm references vim-rails as it's upstream counterpart? https://code.launchpad.net/charms/+source/rails
[19:16] <tvansteenburgh> avoine: thanks for the heads-up
[19:16] <tvansteenburgh> avoine: i wonder if there's an option to use the old behaviour?
[19:16] <lazyPower> avoine: When did that land?
[19:17] <tvansteenburgh> yesterday it looks like
[19:17] <lazyPower> urgh so its in the debian package then?
[19:17] <tvansteenburgh> yep
[19:17]  * lazyPower deploys gitlab-ci to validate its not broken
[19:19] <avoine> the error is like: 2014-05-09 19:08:00 INFO install fatal: [localhost] => /etc/ansible/host_vars/localhost: Expecting property name: line 1 column 1 (char 1)
[19:21] <avoine> I think it could be fix in charm-helpers/contribs/templates/context.py by removing the parentesis around the yaml
[19:23] <avoine> * contrib/templating/contexts.py
[19:25] <lazyPower> sinzui: was vim-rails registered against the rails charm to share bugs? Is it going to peeve anyone off if i remove this uplink?
[19:25] <sinzui> lazyPower, 99% chance it was an error
[19:25] <lazyPower> awesome. Thanks
[19:26] <sinzui> most people who link to distros do more harm than help
[19:37] <avoine> tvansteenburgh: fyi https://bugs.launchpad.net/charm-helpers/+bug/1318036
[19:37] <tvansteenburgh> avoine: thank you!
[19:58] <tvansteenburgh> avoine: did you want to propose your branch for merging? your change lgtm assuming all the tests pass, but i don't have the power to merge it
[19:59] <tvansteenburgh> avoine: will probably need to wait for marcoceppi to merge
[19:59] <avoine> tvansteenburgh: yeah, should I create a merge request?
[19:59] <avoine> ok
[19:59] <tvansteenburgh> avoine: yes, please do
[20:03] <lazyPower> tvansteenburgh: ping me once your +1's are on the MP
[20:03] <lazyPower> i'll do a quick review and ack it if it's good
[20:03] <avoine> tvansteenburgh: done https://code.launchpad.net/~patrick-hetu/charm-helpers/default_flow_style/+merge/219063
[20:05] <lazyPower> dude, perfect
[20:05] <lazyPower> avoine: thanks for this fix!
[20:41] <marcoceppi> jcastro: sudo start juju-db-local-jorge
[22:33] <jose> lazyPower: still around?
[22:35] <lazyPower> for a minute or two, whats up jose?
[22:36] <jose> lazyPower: hey! you said your owncloud tests passed when you did them, would you mind pastebinning the test so I can see if they work for me?
[22:36] <jose> (in the case you still have those changes)
[22:36] <jose> I'm getting these random timeouts
[22:36] <lazyPower> jose: it's whatever is in trunk of the owncloud charm
[22:36] <jose> hmm... ok(?) (that shouldn't work)
[22:37] <lazyPower> jose: running them against amazon now
[22:37] <lazyPower> i'll stick around until they complete running
[22:38] <jose> thanks! I'm running my tests once more to see if they for any magic reason work
[22:52] <jose> lazyPower: unit relation-sentry failed hook install
[22:52] <lazyPower> did you --set-e?
[22:53] <lazyPower> if you did, can you ssh-import-id on the unit so i can remote in and take a look at the logs?
[22:53] <lazyPower> actually, i got that too, so nevermind. I'll re-run it with --set-e
[22:53] <jose> sorry, nope :(
[22:53]  * lazyPower scratches head
[22:53] <lazyPower> they worked at one point... otherwise they wouldn't have been acked.
[22:54] <jose> I find it weird... *that's* the one which shouldn't fail!
[22:54] <lazyPower>  (╯°□°）╯︵ ┻━┻
[22:55] <lazyPower> well mine filed on deploying the relation sentry
[22:55] <lazyPower> so
[22:55]  * lazyPower looks shifty
[22:55]  * lazyPower breaks for food while this runs its course
[23:12] <jose> lazyPower: got the timeout again, even though seconds was set to 3000, which is 50mins
[23:13] <lazyPower> jose: http://paste.ubuntu.com/7425609/
[23:14] <jose> so that's the thing?
[23:14]  * jose grrs
[23:19] <lazyPower> jose: looks like the tests tanked after the merge to update owncloud
[23:20] <lazyPower> i just reverted back to rev 23 and they work
[23:20] <jose> so, what should we do?
[23:21] <jose> I'm not entirely sure on what do to now
[23:25] <lazyPower> jose: the tests are going to have to be updated. The update got merged without checking the tests
[23:25] <jose> I personally don't see what could've changed
[23:25] <lazyPower> file a bug, assign to me, note in the MR that the tests need updated unless you feel like starting from square 0 and rewriting them.
[23:26] <lazyPower> i'll get to them when I get some time to cycle on it. Possibly later this weekend depending on whats going on
[23:26] <jose> hmm, will do
[23:27] <lazyPower> Thanks jose
[23:27] <jose> thanks to you!
[23:27] <lazyPower> I'm goign to head out for the evening. o/ appreciate the cycles on trying to discover whats wrong with the owncloud tests
[23:28] <jose> you have a good rest of your day!
[23:28] <Term1nal> question about juju, trying to wrap my head around: say for example I do something dumb easy like wordpress and mysql in juju. If I set 2 mysql units for 1 wordpress unit, if one of the mysql units goes down, it's already good to go?
[23:31] <jose> I'm not exactly sure about how that would go
[23:32] <Term1nal> I guess I don't understand what the purpose of deploy more units of mysql would do exactly. Do they already replicate at that point?
[23:32] <jose> I personally don't know, someone else should be able to help around
[23:34] <sarnold> Term1nal: in general, I think you'd have to check the charm's README to know the capabilities of each charm.
[23:34] <sarnold> Term1nal: for mysql, it looks like you can deploy mysql slaves easily enough to improve read performance: http://manage.jujucharms.com/charms/precise/mysql
[23:35] <sarnold> off to walk the dog :) have fun
[23:36] <Term1nal> I can grok that, but in the juju-gui, what is the benefit of just increasing the amount of units deployed?
[23:42] <Term1nal> http://askubuntu.com/questions/369231/juju-mysql-adding-units-vs-adding-new-service-with-relation I think that sums up what I was wondering about.
[23:42] <Term1nal> So adding more units to the charm doesn't do anything :D