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