[01:40] <marcoceppi> JoseeAntonioR: I am now
[01:41] <JoseeAntonioR> marcoceppi: hey, wanted to know if you can give me a hand with a couple things on my postfix charm
[02:30] <marcoceppi> JoseeAntonioR: Yeah. I'm about to head off to bed, but tomorrow I'll be around to help out
[02:30] <JoseeAntonioR> sure, thanks!
[12:21] <jcastro> hey evilnickveitch
[12:53] <evilnickveitch> jcastro, hey
[12:56] <jcastro> heya
[12:56] <jcastro> check out the juju list, apparently large swaths of the writecharms stuff is missing
[12:58] <evilnickveitch> jcastro, yeah, I saw that, I am working on a fix. thanks!
[13:00] <jcastro> <3
[13:02] <evilnickveitch> jcastro - the issue was, the "writing a charm" was covered in 2 different places in the old docs, and I only converted one (because it was on my list once, not twice), but it is a reasonably straightforward fix. I will have it done today, and can make it beautiful later
[13:03] <jcastro> nod
[16:33] <arosales> For folks looking on the Juju list they may have noticed we have launched a Charm Championship competition
[16:33] <arosales> https://github.com/juju/charm-championship/
[17:02] <henninge> Hi!
[17:02] <henninge> How can I work around the missing debug-hooks command?
[17:04] <henninge> I ssh into the unit and add '/var/lib/juju/tools/1.11.2-precise-amd64' to PATH, so I can run relation-get but it complains about JUJU_CONTEXT_ID missing.
[17:04] <henninge> What environment do I need to build to be able to run relation-get?
[17:44] <arosales> henninge, hello :-)
[17:44] <arosales> marcoceppi, any suggestions on debug hooks
[17:44] <arosales> henninge, are you using juju 1.11.1?
[17:44] <arosales> henninge, sorry I see the version in your path now
[17:44] <henninge> arosales: 1.11.2, actually
[17:45] <henninge> arosales:  and Hi ;-)
[17:47] <marcoceppi> henninge: I've not tried to mock debug-hooks yet in 1.11.2, typically when I'm writing charms and a hook errors out, I'll just ssh in to the machine, add a few juju-log lines to spit out the relation-get data then run juju resolved --retry on the unit/relation
[17:47] <marcoceppi> henninge: Give me a second to spin up an evironment and check what envs you need
[17:48] <henninge> marcoceppi: Thanks
[17:48] <henninge> yeah true, --retry is an option.
[17:49] <marcoceppi> henninge: I used to know back in pyjuju, but I'm sure there are extra environment variables now. As such I typically patch something live then run --retry until I get it working. After that I just pop the fixes in the local charm and plug away
[17:52] <henninge> marcoceppi: Ok, I'll go with that then. Thanks! ;-)
[17:53] <marcoceppi> henninge: IIRC they're adding debug-hooks or something similar in to core sooner or later, so that's merely a stop gap until then
[17:53] <henninge> Cool. I was hoping for that ...
[18:04] <henninge> Thanks again guys, gotta go.
[18:18] <wedgwood> jcastro: sorry if this is covered elsewhere, but in the contest rules I see "All deployment bundles and charms must be the participant’s original work"
[18:19] <wedgwood> does that mean that a participant would have to write their own postgres charm, for example?
[18:21] <marcoceppi> wedgwood: The wording might be misleading as the contest strongly encourages using charms from the current ecosystem
[18:22] <wedgwood> misleading and possibly confusing/frustrating.
[18:24] <marcoceppi> wedgwood: jcastro is out for the rest of the day, you might want to mail the list for a clarification/to get it fixed
[18:25] <wedgwood> marcoceppi: will do thanks
[18:28] <arosales> wedgwood, I can also follow up on the wording
[18:28] <wedgwood> arosales: ok. I'm emailing the list now too, for good measure.
[18:28] <arosales> wedgwood, ok thanks
[18:29] <arosales> wedgwood, thanks for brining it up
[19:21] <Jarco> Hello, Where can I find info on Juju pricing?
[19:23] <sarnold> Jarco: juju itself is free. hosting on AWS or HP Cloud or Rackspace or whatever will not be free, of course. If you're using your own OpenStack environment or MAAS bare-metal "clouds", juju is free.
[19:23] <Jarco> I will need to look into openstack then
[19:24] <Jarco> Or perhaps aws. Seems to be very good and not to expencive
[19:33] <marcoceppi> Jarco: if you've got hardware already, OpenStack and MAAS are good options, if you don't own hardware and can accept cloud prices HP Cloud is built on OpenStack or you can use AWS. The provider boils down to preference as the provider is interchangeable in Juju. So you can use the same charm and deploy a service on to AWS as you do OpenStack, MAAS, etc
[21:23] <thumper> jcastro, m_3, marcoceppi: I'm looking for some juju presentations that I can pilliage for a talk this afternoon, got any handy?
[21:48] <m_3> thumper: one sec... looking for link
[21:52] <thumper> m_3: ta
[21:53] <thumper> dropbox?
[21:53] <m_3> thumper: invited you... it's a bit frail as it's a dropbox share of a U1 share... etc etc
[21:53] <thumper> m_3: what happened to U1?
[21:53] <thumper> m_3: can't the u1 share just work?
[21:53] <m_3> don't have the U1 link on this laptop
[21:53] <m_3> jcastro might though
[21:54] <m_3> negronjl oe ^
[21:54] <m_3> or negronjl ^^
[21:54] <negronjl> thumper: u1 link for what ?
[21:54] <thumper> m_3: you can share from the web ui
[21:55] <thumper> m_3: the share seems to work ok though :)
[21:58] <m_3> thumper: it's not shared with me over U1 anymore
[21:59] <thumper> m_3: the cloudcamp one is quite good
[21:59] <thumper> needs a little tweaking under the hood
[22:00] <thumper> but the background is almost perfect for my audience
[22:01] <m_3> thumper: great
[22:01] <m_3> have a good talk!  break a leg and such
[22:02] <thumper> thanks