[12:31] <pavel_> hi guys
[12:31] <pavel_> quick question, is there any way to configure ec2 root disk size?
[12:32] <pavel_> I mean when I launch it with juju
[13:18] <ehg> hmm, is there a way to manually remove a service that refuses to die?
[13:18] <ehg> with goju
[13:35] <ehg> e.g. do i have to manually edit a DB to remove zombie services? and how do i do that? :)
[13:57] <jcastro> marcoceppi: hey, the mysql charm, once you flavor=percona, there's no going back is there? I get a config-changed error
[13:57] <marcoceppi> jcastro: I guess so, haven't written tests/checked that yet
[13:57] <marcoceppi> what do the logs say?
[13:58] <jcastro> I didn't look, it was a few days ago
[13:58] <jcastro> I just remembered
[14:11] <marcoceppi> jcastro: open a bug and I'll make sure to check it when I finish writing tests for mysql
[14:11] <jcastro> yeah I am going to check it out
[14:11] <jcastro> but we should test that
[14:11] <jcastro> someone from Maria finally wrote me back!
[14:11]  * marcoceppi nods
[14:20] <arosales> question on juju status in 1.11
[14:20] <arosales> say I didn't know which port mongdb (or any given charm was exposing over)
[14:20] <arosales> juju status in 1.0 > doesn't show the exposed port
[14:20] <arosales> http://paste.ubuntu.com/5755016/
[14:21] <arosales> I am pretty sure the port output was there before, is there a suggested way to find the exposed port?
[14:22] <mgz_> arosales: bug 1173093
[14:22] <_mup_> Bug #1173093: status should report ports <juju-core:Confirmed> <https://launchpad.net/bugs/1173093>
[14:22] <arosales> ah, thank you mgz_
[14:26] <arosales> mgz_, I also added a comment.
[14:26] <arosales> mgz_, any gut feeling on when this bug may get an owner to address?
[14:30] <arosales> I _think_ the open port status is still shown in the juju gui, but I think they are communicating over the web socket.  But the data should be there . .  .
[14:31] <mgz_> arosales: not really, perhaps along with fixing other addressing issues (which will also be a compat change in the json output of some kind)
[14:32] <arosales> mgz_, ok. thanks for the reply on the bug too
[14:39] <jcastro> there's another thing expose needs
[14:39] <jcastro> I put it in a bug
[14:40] <jcastro> it needs to return "service exposed on: http://blah blah" when you first expose it
[14:40] <jcastro> so I don't have to do another status command
[14:41] <mgz_> yup.
[14:48] <marcoceppi> jcastro: that brings some oddities though. What if you expose prior to open-port being called?
[14:50] <jcastro> then wait I think
[14:50] <jcastro> it sucks to expose, then status
[14:50] <marcoceppi> I wouldn't want to block the expose, so many people's scripts will cry
[14:54] <jcastro> evilnickveitch: confused, do I base my new page off my existing branch or do I wait for you to commit to trunk?
[15:00] <evilnickveitch> jcastro, pull the latest version, because I fixed a lot of your bits...
[15:02] <jcastro> evilnickveitch: it's dated from june 6th
[15:02] <evilnickveitch> hmmm
[15:02] <jcastro> lp:juju-core/docs right?
[15:03] <evilnickveitch> that's not right - it is revision 39 now
[15:03] <jcastro> https://code.launchpad.net/juju-core says 31
[15:04] <evilnickveitch> ah... sorry. grab my branch
[15:04] <evilnickveitch> we are changing the juju/core one so it is owned by ~charmers
[15:04] <jcastro> ah ok
[15:04] <evilnickveitch> so this will be a lot easier after tomorrow
[15:05] <evilnickveitch> grab ~evilnick/juju/go-juju-docs if you want to work on anything
[15:05] <jcastro> ack
[15:13] <jcastro> evilnickveitch: hey, do we have like a sidebar class or something for the docs?
[15:13] <jcastro> something for like, a side comment or something I want to tell the audience, but not be in the text block
[15:14] <evilnickveitch> jcastro, you can use an <aside>. i haven't created a style for that yet, but I will need to soon anyhow
[15:14] <jcastro> ah, perfect
[15:14] <evilnickveitch> or you can use the "Note" or "Warning" styles for like footnotes
[15:49] <jcastro> evilnickveitch: ok, best practices done, but when I propose to merge it says "This branch is not mergeable into lp:~evilnick/juju/go-juju-docs."
[15:51] <evilnickveitch> jcastro, it's okay, i don't know why it says that, but i can merge it myself
[15:51] <jcastro> ok
[15:51] <evilnickveitch> where is the branch? same place?
[15:51] <jcastro> branch is pushed to ~jorge/juju-core/best-practice
[15:57] <evilnickveitch> jcastro, yay!
[15:57] <evilnickveitch> okay, i merged that. as you see there isn't a style as such for the aside, but it's cool to have one to work with. I will sort it out
[15:58] <evilnickveitch> AND you didn't mix your spaces and tabs this time :)
[15:58] <jcastro> \o/
[16:16] <jcastro> evilnickveitch: ok, after that I have some updates to both, but that will post meeting and post-lunch
[19:48] <jcastro> m_3: http://codeascraft.com/2013/06/11/introducing-loupe/
[19:51] <m_3> jcastro: sweet