[07:02] <zchander> Goodmorning to all. Can someone explain to me how the version number of the charm is calculated? When I do a bzr checkout for a charm I get (e.g.) a revision file with a number 7, but the charm shows ‘<charm>-13’
[07:47] <lazyPower> zchander: while not a full explanation to your question, sinzui did a writeup over this http://curtis.hovey.name/2013/06/26/managing-juju-charm-versions/
[07:48] <lazyPower> So, effectively there are different revisions depending on context. A revision that you see in teh charm store, is how many releases have been pushed to the store. Each time I merge a charm proposal, it increments the rev no in the store by 1
[07:48] <lazyPower> every time you deploy a charm locally, it increments in your environment by 1 for each deployment
[07:49] <lazyPower> so if i deployed elasticsearch-1, and tweaked something thend eployed again, it would be elasticsearch-2
[09:25] <zchander> lazyPower: Thanks for the info.
[09:26] <lazyPower> np. it can be confusing at first - but it's pretty straight forward once you get there's 3 possible revisions to reference.
[09:28] <zchander> lazyPower: I am busy with ownCloud again (got my MaaS up and running again..)
[09:28] <zchander> Is it possible to clean the juju charm cache?
[09:37] <lazyPower> not that i'm aware of. I believe you'll want to upgrade the charm.
[09:37] <lazyPower> i mean, its possible, but not in a sane and clean manner.
[09:45] <zchander> I am trying to deploy my (updated) test version of ownCloud, but it won’t pick up the change(s) I made, e.g. in my config.yaml
[09:46] <zchander> lazyPower: What happens if I rm-ed /var/lib/juju/charmcache/cs_<charmname> from my juju node?
[09:47] <lazyPower> you'll kill kittens
[09:47] <zchander> Oops….
[09:47] <lazyPower> did you try juju upgrade-charm <charmname>?
[09:47] <lazyPower> that should be all you need to do to have it increment revision to whats deployed +1
[09:56] <zchander> In my initial config.yaml I made an error for the source, e.g. cloud:precise-updates:havana. But this should be cloud:precise-updates/havana (obvious, huh ;) )
[09:56] <zchander> But my current devel version I changed this, but it isn’t picked up
[09:59] <lazyPower> is a hook in an error state?
[09:59] <lazyPower> or with an active debug-hooks session open?
[10:00] <lazyPower> those two instances will prevent an upgrade from landing, as its waiting in line to execute.
[10:00] <lazyPower> hook execution in juju is serial. You can queue many operations that will stack and resolve in FIFO fashion.
[10:01] <zchander> I just did a juju upgrade-charm but my new config.yaml isn’t picked up
[10:05] <lazyPower> did you deploy from local or from teh charm store?
[10:06] <zchander> lazyPower: Local
[10:06] <lazyPower> strange
[10:11] <lazyPower> zchander: i dont know :( that should work. Aside from tearing down i'm out of ideas this early in the morning.
[10:12] <zchander> lazyPower: np. I’ll continue my quest :D In the worst case, I’ll tear down my juju and rebuild it
[10:25] <zchander> lazyPower: Is there documentation for charm-helpers? Seems I cannot find any (or my Google skills are getting worse)
[10:26] <lazyPower> just a few charm schools - there are no official documents to speak of
[10:26] <lazyPower> its on the todo list to get them documented, but it hasn't happened yet.
[10:26] <lazyPower> most of the code in charm helpers is pretty straight forward though, well enough to gleen what its doing.
[10:31] <zchander> lazyPower: I am trying to add a new source (like cs:precise-updates/havana) to my charm, but it seems the ordinairy add-apt-repository doesn’t understand this kind of URL. It seems the charm-helpers does have it, but I need/search the correct syntax
[10:32] <lazyPower> cs:precise isn't a valid ppa url.
[10:32] <lazyPower> ppa:precise-updates/havana?
[10:33] <lazyPower> zchander: here's how dosaboy did it in the MySQL charm w/ charm helpers fetch: https://code.launchpad.net/~hopem/charms/precise/mysql/lp1281752/+merge/209312
[10:37] <zchander> lazyPower: I know it isn’t a valid ppd url, but I want(ed) to keep it a bit like e.g. the Ceph charm does it
[10:37] <zchander> I’ll have a look at the MySQL charm
[10:37] <lazyPower> it's using a helper from charm_helpers in the fetch module.
[13:09] <didrocks> jcastro: hey man! not sure you noticed another small fix: https://github.com/juju/docs/pull/98
[14:00] <marcoceppi> didrocks: thanks for the fix!
[15:00] <didrocks> marcoceppi: yw!
[15:00] <didrocks> thanks for looking at it :)
[15:25] <roadmr> hello, I tried to juju deploy wordpress using default-series: trusty and I get "ERROR charm not found: cs:trusty/wordpress". Is there really no charm for wordpress on trusty, or do I need to update something for this to work?
[15:25] <roadmr> btw I'm just curious, I don't need this for production or anything, just thought it was odd and worth pointing out
[15:38] <lazyPower> roadmr: it has not been pushed to trusty yet
[15:39] <roadmr> lazyPower: thanks! well that takes care of my question :)
[15:39] <lazyPower> roadmr: http://manage.jujucharms.com/charms/trusty - are all our current trusty charms. There's an audit effort going on to ensure were promoting charms of good quality to the trusty series. We appreciate your patience while we continue the effort.
[15:40] <roadmr> lazyPower: sure thing, no rush from me, and thanks for your work on this
[15:45] <jcastro> hey sinzui
[15:45] <jcastro> cjohnston and I are seeing https://bugs.launchpad.net/juju-core/+bug/1306537 still
[15:45] <_mup_> Bug #1306537: LXC local provider fails to provision precise instances from a trusty host <deploy> <local-provider> <lxc> <juju-core:Fix Released by wallyworld> <juju-core 1.18:Fix Released by wallyworld> <juju-quickstart:Fix Released by frankban> <juju-quickstart (Ubuntu):New> <juju-quickstart (Ubuntu Trusty):New> <https://launchpad.net/bugs/1306537>
[15:45] <jcastro> what's the procedure for reopening, I just didn't want to toggle it without talking to you first
[15:50] <sinzui> jcastro, Lets open a new bug citing the old bug targeted to 1.18.4. The issue may not be the same since it was tested to be fixed
[17:07] <lazyPower> jcastro: whats your output from dmesg?
[17:08] <lazyPower> i want to validate i'm not nuts if at all possible.
[17:22] <jose> negronjl: https://code.launchpad.net/~jose/charms/precise/seafile/add-set--eux/+merge/219736 for you to check
[17:33] <cjohnston> jcastro: did you open a new bug by chance?
[17:33] <jcastro> no
[17:37] <cjohnston> jcastro: bug #1319947 if you want to confirm it please :-)
[17:38] <_mup_> Bug #1319947: LXC local provider fails to provision precise instances from a trusty host - take 2 <juju-core:New> <https://launchpad.net/bugs/1319947>
[19:00] <l1l> Can anyone help with this error. I get it during the bootstrap: DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh -o "StrictHostKeyChecking no" -o "PasswordAuthentication no" -i
[19:05] <sinzui> charmers https://code.launchpad.net/~juju-qa/charms/precise/jenkins-slave/trunk/+merge/219749
[19:07] <marcoceppi> sinzui: will take a peek in a min
[19:24] <negronjl> jose: https://code.launchpad.net/~jose/charms/precise/seafile/add-set--eux/+merge/219736 ... Approved and Merged.  Thank you sir :)
[19:24] <jose> negronjl: thanks to you :)
[19:24] <jose> another MP coming soon to fix a little bug
[23:11] <jcastro> http://askubuntu.com/questions/465508/juju-bootstrap-debug-failed-to-connect-https-streams-canonical-com
[23:11] <jcastro> any ideas here?
[23:13] <jose> jcastro: sometimes it happens with the archives that I hit in a second when they're down or something, but if it's an SSL error contact IS?