[13:05] <aaaaaaaaa> hi
[13:05] <aaaaaaaaa> How all ?
[15:00] <lazyPower> Good Morning Juju Community!
[15:00] <lazyPower> We'll be kicking off in a moment
[15:01] <lazyPower> http://summit.ubuntu.com/uos-1411/meeting/22389/juju-charm-school/ - if you need the link to follow along at home
[15:01] <lazyPower> If you'd like to join the hangout and talk on air with us, https://plus.google.com/hangouts/_/hoaevent/AP36tYc0Jup3WIfx2y7xjN_n5r_CqEIPHfQALDK4M8cYEvra-yB17Q?authuser=0&hl=en
[15:05] <lazyPower> uh oh, i see our summit page is missing the link
[15:05] <lazyPower> http://youtu.be/BQ_blv9JhCs - THis will get you started while we figure out what we did with the video link on summit
[15:07] <cory_fu> Do you need a PPA to install juju?
[15:09] <rbasak-uos> sudo add-apt-repository ppa:juju/stable
[15:09] <rbasak-uos> (IIRC)
[15:09] <lazyPower> that is correct!
[15:09] <lazyPower> to the new joiners - it appears we didnt put the correct link int eh summit page - you can follow along here: http://youtu.be/BQ_blv9JhCs
[15:09] <lazyPower> many apologies for the inconvenience
[15:13] <kwmonroe> \join #ubuntu-uds-devops-1
[15:15] <kwmonroe> 1/join #ubuntu-uds-devops-1nnnnnnnnnnnnnnmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm.mmmmmmmmmmjkllko-],m
[15:15] <lazyPower> kwmonroe: awesome cat typing
[15:19] <kwmonroe> doh!
[15:22] <larrymi2> QUESTION what's the local entry in your environments file look like?
[15:22] <kwmonroe> thanks mbruzek1!  we'll get that 1st 5 minute walkthrough doc live asap.
[15:25] <larrymi2> great thank you
[15:25] <mbruzek1> You are welcome
[15:26] <mbruzek1> Thanks for the question
[15:31] <mbruzek1> Please let us know if you have questions!
[15:42] <cory_fu> lazyPower: The syntax for relation_set is actually: hookenv.relation_set(hookenv.relation_id(), {'public-address': hookenv.unit_get('public-address')})
[15:49] <noise][> thanks for the juju intro, I got behind a bit but very helpful!
[15:52] <lazyPower> noise][: we're available in #juju here on freenode to answer any questions you may have.
[15:53] <noise][> awesome, I'm going to finish working through the python example shortly
[15:53] <lazyPower> http://pythonhosted.org/charmhelpers/
[15:53] <cory_fu> Also: https://juju.ubuntu.com/docs/
[15:56] <larrymi2> thank you!
[15:56] <lazyPower> it was our pleasure larrymi2
[17:57] <mbruzek1> If you want to join the Juju Testing conversation please go here https://plus.google.com/hangouts/_/hoaevent/AP36tYekk8djMgop1pzFddjyTDy7plhXOwcKYregkciGjHoVC0aAXQ?authuser=0&hl=en
[17:58] <mbruzek1> Our next UOS session starts soon
[18:02] <mbruzek1> https://juju.ubuntu.com/docs/authors-charm-policy.html
[18:02] <mbruzek1> We are talking about Charm Store Policy right now
[18:03] <mbruzek1> Amulet:  https://juju.ubuntu.com/docs/tools-amulet.html
[18:04] <mbruzek1> Bundletester:  https://github.com/juju-solutions/bundletester
[18:06] <sparkiegeek> lazyPower: can't see your screen, Tim has "focus"
[18:06] <mbruzek1> bundletester repository
[18:06] <mbruzek1> https://github.com/juju-solutions/bundletester
[18:08] <dpb1> mbruzek1: can you change the focus over to lazypower?
[18:08] <jamestunnicliffe> ^^
[18:08] <sparkiegeek> +1
[18:08] <mbruzek1> Thank you
[18:08] <mbruzek1> Sorry about that
[18:09] <mbruzek1> apt-get install python-pip juju charm-tools python-devel
[18:10] <sparkiegeek> why not juju deploy bundletester ?
[18:10] <tvansteenburgh> it's not a charm
[18:10] <mbruzek1> It is not a charm, it is a testing framework
[18:11] <mbruzek1> Good question sparkiegeek, we hope to have it bundled with juju as Josh S. mentioned
[18:11] <mbruzek1> in the near future.
[18:11] <sparkiegeek> mbruzek1: sounds good
[18:14] <sparkiegeek> it's impossible to see what lazyPower is typing because the heads cover up the bottom of the terminal screen
[18:15] <sparkiegeek> that's better, thanks!
[18:15] <cory_fu> Not just the top, also the bottom, which is an issue when issuing commands on the command-line
[18:15] <dpb1> mbruzek1: also the pictures of who is in the hangout cover up the command line
[18:16] <mbruzek1> dpb1: OK I will try to address that
[18:16] <dpb1> mbruzek1: thx.  understand it's hard to adjust things.
[18:16] <sparkiegeek> perhaps larger font size would help
[18:19] <dpb1> oh, cool. thanks for doing that tvansteenburgh
[18:19] <tvansteenburgh> \o/
[18:23] <dpb1> can bundletester work on an already bootstrapped environment?
[18:23] <mbruzek1> yes absoltely
[18:23] <mbruzek1> It runs faster
[18:23] <dpb1> does each test tear down and build back up the environment like on juju-test, or is that pretty much obsolete now?
[18:24] <sparkiegeek> what are the guidelines about when you put tests into a separate tests/XX-my-test file vs. many in one ?
[18:24] <tvansteenburgh> it resets the env between each test
[18:24] <tvansteenburgh> much faster than destroy/rebootstrap between each test
[18:26] <dpb1> Q: Is the name 'bundletester' is a bit misleading?  Is it for testing individual charms, as well as bundles?
[18:27] <sparkiegeek> thank you
[18:28]  * sparkiegeek guesses mojo
[18:28] <dpb1> tvansteenburgh: I think it's fine, just threw me a bit.  thanks
[18:28] <dpb1> since bundle is like a superset I can see where you are going
[18:29] <tvansteenburgh> http://reports.vapour.ws/charm-tests-by-charm
[18:29] <dpb1> mbruzek1: actually, if charles would just do export PS1='$ ' and could live without the fancy prompt, it would be better.
[18:30] <sparkiegeek> dpb1: +1
[18:30] <tvansteenburgh> https://github.com/juju-solutions/charmguardian
[18:31] <dpb1> mind blown. j/k
[18:31] <sparkiegeek> dpb1: your MP is quoted in the README.md of that project :)
[18:31] <tvansteenburgh> haha
[18:32] <dpb1> sparkiegeek: :)
[18:32] <dpb1> tvansteenburgh: this is quite nice, thanks for doing all this
[18:32] <sparkiegeek> the #! has to be at the top
[18:32] <sparkiegeek> (looks like you fixed it)
[18:33] <dpb1> Q: can the results of those bundle tests be appended to the MP, right now are they just emailed?
[18:33] <tvansteenburgh> dpb1: thanks, it's been fun. still lots to do too!
[18:33] <tvansteenburgh> dpb1: doesn't it post a link to the results on the MP?
[18:33] <JoshStrobl> I didn't realize test creation is so easy. Makes me ashamed that I haven't done it for my charms yet.
[18:34] <tvansteenburgh> a recent blog post on Juju testing: http://blog.juju.solutions/cloud/juju/2014/10/02/charm-testing.html
[18:34] <dpb1> tvansteenburgh: I'm checking that
[18:35] <dpb1> tvansteenburgh: for instance: https://code.launchpad.net/~brad-marshall/charms/trusty/nrpe-external-master/fix-rsyncd-conf/+merge/241482
[18:38] <tvansteenburgh> dpb1: in the review queue/auto-testing integration still needs work
[18:38] <tvansteenburgh> s/in//
[18:38] <sparkiegeek> tvansteenburgh: awesome! So the unit name that appears to relations is "normal"?
[18:38] <tvansteenburgh> yes
[18:38] <dpb1> tvansteenburgh: that is fine, looking forward to more in that area.  thanks.
[18:38] <tvansteenburgh> no more cruft
[18:38] <sparkiegeek> tvansteenburgh: tried using amulet before to test a charm that related to PostgreSQL and it was impossible
[18:40] <dpb1> yes, creating the shim was always a problem for me to, big +1 on that change (as I said before).
[18:40] <sparkiegeek> http://upload.wikimedia.org/wikipedia/commons/0/04/Potato_salad_with_egg_and_mayonnaise.jpg
[18:40] <sparkiegeek> ^^ potato salad for lazyPower
[18:42]  * dpb1 is strangely hungry
[18:42] <sparkiegeek> well you'll now get a test error instead of a test failure
[18:42] <sparkiegeek> I assume bundletester distinguishes between them?
[18:46] <tvansteenburgh> not really, exit code 0 = pass, other = fail
[18:48] <sparkiegeek> ack
[18:49] <dpb1> tvansteenburgh: does it also run unit tests?
[18:49] <dpb1> tvansteenburgh: or is that a totally separate topic
[18:49] <tvansteenburgh> yep, just put them behind a `make test` target
[18:49] <dpb1> ok
[18:49] <dpb1> great, thought it did
[18:50] <sparkiegeek> can you go over again what the technique is for getting *this* charm in amulet and not the one that's in the store?
[18:50]  * dpb1 would like to see that too
[18:50] <sparkiegeek> is it just cs:XYZ for store ones? and XYZ for local?
[18:51] <JoshStrobl> sparkiegeek, yes
[18:51] <JoshStrobl> that is my understanding as well
[18:51] <sparkiegeek> hmmm
[18:52] <sparkiegeek> so if I have a bzr branch of XYZ called "XYZ-fix-bug-123" then all my tests will break?
[18:52] <sparkiegeek> (as in my directory name isn't the same as the charm name)
[18:52] <tvansteenburgh> sparkiegeek: correct
[18:52] <dpb1> I thought it redirected to the locally checked out branch
[18:52] <dpb1> wherever you are running things from
[18:52] <sparkiegeek> tvansteenburgh: ok, cheers
[18:53] <tvansteenburgh> it would be better to check out the branch into a dir with a name that matches the charm
[18:53] <dpb1> ok
[18:53] <sparkiegeek> juju sure loves its directory names
[18:53] <tvansteenburgh> heh,  yeah :?
[18:54] <sparkiegeek> if only there was a metadata file with the name in it, oh wait :)
[18:54]  * sparkiegeek files bug
[18:54] <dpb1> link and I'll +1
[18:54] <tvansteenburgh> sparkiegeek: really good point there
[18:54] <mbruzek1> https://juju.ubuntu.com/docs/tools-amulet.html
[18:54] <tvansteenburgh> sparkiegeek: you file it, i'll fix it
[18:55] <dpb1> tvansteenburgh: nice attitude. :)
[18:57] <sparkiegeek> dpb1: tvansteenburgh: https://github.com/marcoceppi/amulet/issues/50
[18:57] <tvansteenburgh> sparkiegeek: thank you!
[18:58] <dpb1> thx sparkiegeek, nice catch
[18:58]  * JoshStrobl goes and makes dinner
[19:00] <sparkiegeek> tvansteenburgh: FWIW looks like i could run the tests with JUJU_TEST_CHARM environment variable set and that'd do similar thing
[19:00] <tvansteenburgh> sparkiegeek: yep, forgot about that :)
[19:03] <mbruzek1> http://pythonhosted.org/charmhelpers/
[19:03] <mbruzek1> https://juju.ubuntu.com/docs/tools-charm-helpers.html
[19:04] <lazyPower> http://pythonhosted.org/charmhelpers/
[19:04] <lazyPower> just to re-iterate :)
[19:14] <avoine> QUESTION: why  charmhelper is not a debian package?
[19:15] <whit> avoine, it's in flux and when it settles down, we will likely make it a deb
[19:16] <whit> right now, most f us typically use pip to pull it in
[19:17]  * whit notes that releasing to a ppa would be sensible for ch
[19:18] <avoine> ok
[19:21] <whit> avoine, right now charm helpers encompasses a broad number of concerns which need to eventually be broken into their packages
[19:22] <whit> ^ own
[19:28] <avoine> ok, the main reason I asked is because updating charmhelper makes charm MP really big and make it a package would make merge lighter
[19:28] <tvansteenburgh> avoine: totally agree
[19:29] <whit> yup
[19:29] <cory_fu> Completely agree.  As whit mentioned, `pip install charmhelpers` is currently my preferred way around that
[19:29] <whit> remember also you can peg ch to a revision or pull it from bzr with pip