[00:08] <thumper> marcoceppi, lazyPower: the latest merge into python-django charm, is that fully backwardly compatible?
[00:08] <thumper> as in, as a user of the charm, there should be no change>?
[00:08] <lazyPower> thumper: link?
[00:09] <thumper> lazyPower: didn't marcoceppi update it?
[00:09] <thumper> lazyPower: in an email to the juju list today
[00:09] <lazyPower> looking
[00:09] <thumper> https://code.launchpad.net/~charmers/charms/trusty/python-django/trunk
[00:09] <thumper> last commit 19 hours ago
[00:10] <lazyPower> thumper: no serious change to config - you should be fine. I would recommend you simulate a deploy in a staging env before you do this on anything you have in production
[00:11] <lazyPower> it changed some of the defaults, but theory states you already have these values set on your charms in the wild. so again, looks g2g at first glance
[00:11]  * thumper twitches
[00:11]  * thumper grabs the code and proposes a fix
[00:11] <lazyPower> if you're relying on unit-config - it will block you from upgrading.
[00:12] <lazyPower> as that config option was removed, so i stand corrected
[00:13] <thumper> lazyPower: how do I run the tests on this thing?
[00:13] <lazyPower> thumper: make a virtualenv, pip install bundletester into that virtualenv and just run bundletester from the charm root.
[00:13] <lazyPower> ti will execute against your currently active juju env
[00:15] <lazyPower> marcoceppi: added an inline diff comment on that python-django merge that thumper is talking about - this merge violates policy
[00:16] <marcoceppi> lazyPower: it doesn't anymore, juju handles this now as well as removing relations
[00:16] <lazyPower> marcoceppi: our policy docs clearly state that its violated
[00:17] <lazyPower> included for easy ref.
[00:17] <lazyPower> it has to be maintained until the next series release
[00:17] <lazyPower> so if this was going to vivid, sure
[00:17] <lazyPower> but not according to policy today
[00:17] <lazyPower> s/vivid/vivid or utopic/
[00:17] <lazyPower> or even trusty
[00:18] <lazyPower> unless im' mis-reading policy
[00:18] <lazyPower> which is possible
[00:39] <thumper> lazyPower: my first charm patch https://code.launchpad.net/~thumper/charms/precise/python-django/tweaks/+merge/245807
[00:41] <lazyPower> thumper: no tests to validate? :(
[00:41] <thumper> lazyPower: no behaviour has changed
[00:41] <thumper> so all tests should be the same, no?
[00:42] <thumper> I've not added any functionality, just pulled four copies of code into one place
[00:42] <lazyPower> ah i see what you did here
[00:46] <lazyPower> tvansteenburgh: oh man, we got lazr authentication pulled in pip proper now? no more crazyness with --alow-unverified and --allow-unsigned? Very nice!
[00:50] <lazyPower> thumper: something is hozed in my env, waiting on automated tests
[00:50] <thumper> lazyPower: no rush
[01:21] <lazyPower> noodles785: hey this is cool, the /etc/ansible/host_vars/localhost  - i had no idea we were storing all this data - makes it kind of handy to access via current_relation['var']. well played sir.
[01:29] <jose> lazyPower, arosales: I do object to the auto-merging of thos
[01:30] <jose> lazyPower, arosales: after working with Matt with some of them, not all of them are acceptable as-is. Some charms will not be satisfied with an autogen, since they force you to set an specific key, or maybe need an specific setup that's specified in the readme and not the metadata
[01:30] <jose> lazyPower, arosales: so, yes, I would test *all* of them and if tests pass then merge it, as I've been doing lately
[01:31] <lazyPower> jose: seems like something as simple as setting a key could be updated in the test during the merge
[01:31] <lazyPower> are there other scenarios?
[01:32] <arosales> jose defaults for a charm ~should~ work correct?
[01:32] <jose> lazyPower: needing to *create* the key somewhere else, and as I said, specific deployment
[01:32] <jose> arosales: not always
[01:33] <lazyPower> jose: thats policy. sane defaults. the charm should deploy without any user intervention, and if it requires user intervention - it must be clearly outlined in teh readme. which means we can set it.
[01:33] <jose> e.g. the newrelic charm, I had to create an account and add my key to the tests in order for them to pass, otherwise I would get a clear failure
[01:33] <lazyPower> unless its something like pagekite where it requires an account - and thats iffy at best putting test credentials in a charm.
[01:33] <lazyPower> smells of abuse
[01:33] <jose> pagekite is not in the store yet :)
[01:33] <arosales> its a valid point but I think we should take that as the exception and not the rule to the pending MPs
[01:34] <lazyPower> jose: indeed - but it was an example case.
[01:34] <arosales> jose: do you see any of the charms currently in the queue?
[01:34] <jose> if you get them all in and then start to find failures, warned you
[01:35] <jose> arosales: I did, yes. newrelic-php and another couple I saw before the  holiday break
[01:35] <arosales> jose: also one action lazyPower was going to take is to file a bug against the charm that is failing
[01:35] <arosales> jose: if you could add a comment to those MPs that would be greatly appreciated
[01:35] <arosales> I am curently going through them too.
[01:35] <jose> yep, I've been working on newrelic-php and trying to check how can I fix it since it's a bit weird
[01:35] <arosales> ie https://code.launchpad.net/~marcoceppi/charms/precise/seafile/tests/+merge/240964
[01:36] <jose> I was going to propose a fix
[01:36] <jose> seafile... I believe there is an incoming MP to fix the non-deployment?
[01:36] <arosales> even for the point you outlined I think it is good to accept these tests
[01:36] <jose> sure
[01:36] <arosales> it brings up points and possible bugs that would not have been noticed had the autogen charm test not been there
[01:36] <arosales> so I am commenting on the MPs.
[01:37] <arosales> I'll leave it up to the charmers team to make the final decision.
[01:37] <arosales> thus far 4 +1 to accept and your -1 to nack
[01:37] <jose> if they're going to be tested at the end, I'd say run the test and if there's an error *because of the test* then nack
[01:37] <jose> take it as a 0, not as a -1
[01:38] <jose> half/half in with the proposal
[01:39] <arosales> we lose the unit logs with auto charm testing
[01:39] <arosales> for the ones I can tell if the test is failing though we should note that
[01:39] <arosales> very good point jose
[01:39] <jose> arosales: btw, that seafile error, if the queue follows its natural flow the fix should land before the test
[01:39] <arosales> ah very nice
[01:40] <arosales> I am going to get some dinner, but I'll return later tonight and keep commeting on these outstanding test MPs
[01:40] <jose> cool :)
[01:40] <arosales> and looking for the ones that have charm tests that may need updating
[01:40] <jose> also, when I run bundletester over here and something fails, everything is kept as is
[01:40] <arosales> jose: thanks for your reply on the matter
[01:40] <jose> sure.
[01:41] <jose> enjoy your dinner
[01:41] <lazyPower> arosales: i'm getting close to being at a point i can transition to helping with the queue, in a furious debug session with racing config between two hosts
[01:41] <arosales> jose: thanks
[01:41] <lazyPower> but this is looking awesome and should give lamont a good basis to look at for sep. of concerns on a host vs its subordinate
[01:42] <jose> lazyPower: I've gone back to the queue after a 'discussion' with my ISP and my connection being off
[01:42] <lazyPower> jose: are you getting throttled already?
[01:42] <jose> lazyPower: I was. couldn
[01:42] <jose> couldn't stay online for more than 5mins or it'd kick meoff
[01:43] <lazyPower> thats the pitts, i know it bothers me when comcast gets nosey in my bidniss and throttles me during the day because i'm pushing volumes of data related to builds
[01:43] <lazyPower> After 3 months of back and forth i gave up and they won, i get throttled from 10am => 5pm
[01:46] <lazyPower> jose: however - if you get to those MP's before me - just make sure you file bugs against the ones with failing tests you ack - so we have a point of reference when the problem surfaced, and how long we have to make it correct. The mail to the list of status will serve as the first step in its trajectory
[01:46] <jose> not getting this... are you asking me to merge all of them?
[01:48] <lazyPower> jose: there's a 20 minute scrollback worth of conversation about it. if the test fails, and its not an edge case merge that requires crednetials - yes.
[01:48] <lazyPower> *credentials
[01:48] <lazyPower> and filing of a bug against the charm that it has failing tests, tagged audit.
[01:49] <jose> I'll leave that to you.
[02:17] <jose> marcoceppi: ping
[03:32] <lazyPower> hey thumper, you still kickin around?
[03:32] <thumper> yeah, in a call now
[03:34] <lazyPower> thumper: when you get a moment - i'm attempting to send relationship data out of a relationship context - i have a dependent service that needs to update config based on values being passed from a different context, and i have no way of triggering that manually that i'm aware of , but i have this bit of shell in my head that i should be able to do this...
[03:34] <lazyPower> https://gist.github.com/chuckbutler/443777748984e3673925
[03:34] <lazyPower> using relation-set -r docker:8 foo=bar - i thought i could push data out of band and trigger the relationship-changed hook on that relation id, no?
[04:09] <thumper> lazyPower: sorry, not sure
[04:09] <lazyPower> ill sync up with marcoceppi tomorrow - thanks for taking a look thumper
[04:09] <thumper> kk
[04:09] <thumper> nigth
[07:01] <X-Rob> Is there any way to reset the positioning of all the icons in juju-gui? It's totally mental, and getting lots of NaNs
[07:52] <lazyPower> X-Rob: Yeah, i ran into that myself
[07:52] <lazyPower> let me find the snippet for you
[07:53] <lazyPower> X-Rob: are you familiar with the browser console and how to get to it?
[08:21] <X-Rob> lazyPower: extremely
[08:22] <lazyPower> X-Rob: this will reset every last charm you have in your gui (up to 100 services) to teh same X/Y
[08:22] <lazyPower> https://gist.github.com/chuckbutler/edf2efe5a426b62b1e1b
[08:23] <lazyPower> shoudl get rid of those nasty NaN errors as well - this happens during a botched upgrade of juju-gui releases as i understand it. Its really rare though - so if this doesn't persist - reach out to hatch and he can get you locked down. there was some additional steps I had to take in teh end to fully resolve it
[08:24] <lazyPower> but that might fix you up with no additional work required
[09:05] <X-Rob> I actually gave up, lazyPower. 'juju destroy-environment' and I'll just start again
[14:49] <tvansteenburgh> wwitzel3: know how to fix this? http://pastebin.ubuntu.com/9693080/
[14:50] <tvansteenburgh> (or anyone else)
[14:57] <wwitzel3> tvansteenburgh: looking
[15:00] <jamespage> gnuoy, https://code.launchpad.net/~james-page/charm-helpers/kilo-enable/+merge/245870
[15:01] <wwitzel3> tvansteenburgh: can you pastebin the output of: go env
[15:03] <tvansteenburgh> wwitzel3: http://pastebin.ubuntu.com/9693183/
[15:06] <wwitzel3> tvansteenburgh: going in to my standup, I would try deleting that pkg folder and attempting re go get
[15:06] <tvansteenburgh> wwitzel3: k, thanks
[15:15] <tvansteenburgh> marcoceppi: i have a test that i kicked off from RevQ that finished, but RevQ status didn't get updated: http://juju-ci.vapour.ws:8080/job/charm-bundle-test/10878/console
[15:16] <tvansteenburgh> marcoceppi: it's http://review.juju.solutions/review/1893 in the RevQ
[15:23] <marcoceppi> tvansteenburgh: all test results are giving a 404
[15:23] <marcoceppi> Did the URL change?
[15:25] <tvansteenburgh> marcoceppi: example?
[15:25] <marcoceppi> actually, it's not getting the URL back at all
[15:25] <marcoceppi> tvansteenburgh: did the jenkins test change?
[15:26] <tvansteenburgh> curl http://review.juju.solutions/review/1893/ctb_callback/344 --data-urlencode status=PASS --data-urlencode result_url=http://reports.vapour.ws/charm-tests/charm-bundle-test-10878-results
[15:26] <marcoceppi> tvansteenburgh: this is in the database: http://paste.ubuntu.com/9693288/ it's got the callback, but hte url wasn't recorded
[15:27] <marcoceppi> yeah, it's still looking for that. Let me add some debug information in
[15:27] <tvansteenburgh> well that is weird? there were many yesterday that *did* work
[15:28] <marcoceppi> omg
[15:30] <marcoceppi> weird
[15:35] <marcoceppi> tvansteenburgh: this is why
[15:35] <marcoceppi> tvansteenburgh: http://reports.vapour.ws/charm-tests/charm-bundle-test-10878-results/json
[15:35] <marcoceppi> that result url doesn't work
[15:36] <jose> hey marcoceppi, have you seen an error where Amulet tries to relate yet-to-be-deployed services?
[15:37] <marcoceppi> jose: that should never happen unless the d.add for the service is executed after the initial d.setup
[15:37] <marcoceppi> jose: could you be more explicit, like witha test file and the output of the test run?
[15:37] <jose> marcoceppi: sure, I have the test file but not the output (that was yesterday night), I'll run again
[15:37] <jose> sec for link
[15:38] <jose> https://code.launchpad.net/~mbruzek/charms/precise/oops-tools/tests/+merge/240997 to be specific
[15:39] <mbruzek> what did I do?
[15:40] <jose> mbruzek: autogen tests are throwing an unexpected amulet error, sorry for the highlight :)
[15:41] <mbruzek> jose:  that is fine, probably due to bad test author
[15:41] <mbruzek> (me)
[15:41] <jose> well, this time Amulet is to blame :P
[15:41] <jose> but *only for this time*
[15:42] <mbruzek> Have you *met* Marco?  He is never wrong!
[15:42] <jose> I have
[15:43] <jose> I believe that was... 2012
[15:43] <mbruzek> jose marcoceppi the reason that test is failing is because I misspelled postgresql
[15:44] <mbruzek> jose postresql
[15:44] <jose> mbruzek: oooh, good catch!
[15:44] <jose> why did the autogen misspell?
[15:44] <mbruzek> Autogen didn't do that, that was a *human* error
[15:44] <mbruzek> fixing now
[15:45]  * marcoceppi is always right, yet again! ;)
[15:49] <jose> :P
[15:50] <wwitzel3> tvansteenburgh: did that resolve your issue?
[15:53] <tvansteenburgh> wwitzel3: which dir were you suggesting i delete?
[16:07] <wwitzel3> tvansteenburgh: GOPATH/pkg/linux_amd64 folder
[16:07] <wwitzel3> tvansteenburgh: just delete the whole thing and retry
[16:10] <skay> when I try to run tests for a charm I get an import error due to yaml; however, yaml is installed
[16:10] <skay> is hte python path getting munged by bundletester in some way? I haven't used it before now
[16:12] <tvansteenburgh> skay please paste errer
[16:12] <tvansteenburgh> error
[16:12] <tvansteenburgh> wwitzel3: what is your GOROOT?
[16:13] <wwitzel3> tvansteenburgh: mine is /home/wwitzel3/opt/go .. I built go from source
[16:14] <skay> tvansteenburgh: http://paste.ubuntu.com/9693519/
[16:15] <skay> tvansteenburgh: I imported it from a shell for a sanity check http://paste.ubuntu.com/9693523/
[16:17] <tvansteenburgh> skay: are the tests using py3 perhaps?
[16:17] <skay> facepalm
[16:17] <skay> tvansteenburgh: yes, thanks for the tip :)
[16:17] <skay> forgot to check
[16:18] <tvansteenburgh> np :)
[16:19] <skay> tvansteenburgh: what's the common practice -- do people usually have a readme that explains how to run the tests for the charm that is being worked on, and have a testing requirements.txt file for people to use?
[16:19] <skay> that's something I have when I'm creating things, but I'm making a small change for the first time to a charm, and I've never gonet hrough the process before
[16:19] <marcoceppi> skay: usually a Makefile
[16:20] <marcoceppi> with a test target
[16:20] <tvansteenburgh> make test is most common for unit teste
[16:20] <tvansteenburgh> tests
[16:20] <marcoceppi> oh, is that not this?
[16:20] <skay> oh I see. there's a makefile with the test target commented out
[16:20] <tvansteenburgh> no, i'm just slow
[16:21] <skay> I wasn't sure what to do, so I gave up and decided to see what commands jenkins would call so I could mimic it
[16:21] <skay> I saw that it was running a bundletester command and tried to use that
[16:22] <tvansteenburgh> yeah that is what you should do
[16:22] <skay> so, for this charm, the test target is commented out. there is an integration-test target, and there's nothing that creates a virtualenv to install the testing dependencies and such
[16:22] <skay> is it common practice for people to set all that up using some other method?
[16:23] <skay> or should I plan to edit the Makefile to do what I think is probably good practice?
[16:23] <tvansteenburgh> the latter
[16:23] <tvansteenburgh> bundletester will call `make test`
[16:23] <tvansteenburgh> and execute anything in tests/
[16:24] <tvansteenburgh> so just make sure that your test target has a prereq that sets up deps
[16:24] <skay> tvansteenburgh: is there an exemplar project with a makefile and such that follow best practices?
[16:25] <tvansteenburgh> there are several, let me find one...
[16:25] <skay> I'd like not to make newbie mistakes, though I know it is inevitable
[16:27] <skay> I am thinking about a guide: So you want to contribute to an existing charm! here's what you do
[16:28] <skay> and then later: So you want to make a charm that is easy for new contributors to hack on! here's what you do
[16:28] <tvansteenburgh> skay: trusty/haproxy
[16:28] <tvansteenburgh> look at test, .venv, and lint targets
[16:30] <tvansteenburgh> that's standard setup
[16:30] <tvansteenburgh> then put amulet tests in tests/
[16:30] <skay> tvansteenburgh: thanks! checking my assumptions -- bundletester will kick off by creating a container or vm and then run make test for me?
[16:31] <skay> I want to make sure I'm not clobbering my system
[16:31] <tvansteenburgh> bundletester does not create a container yet, although it is planned
[16:32] <tvansteenburgh> hence the .venv target
[16:32] <skay> tvansteenburgh: okay, so I wouldn't want to do .venv that way for my system, since I install virtualenv from pip and not the apt package.
[16:32] <skay> but I would guess standard practice must be to use system dependencies where they exist?
[16:33] <skay> thus I should probably make a container when I do this
[16:34] <skay> tvansteenburgh: thanks for the help. I am grateful for it!
[16:34] <skay> I am also very happy that people have done a lot of work in the review queue
[16:34] <tvansteenburgh> sure thing, any time :)
[16:36] <tvansteenburgh> wwitzel3: http://pastebin.ubuntu.com/9693596/
[16:37] <tvansteenburgh> wwitzel3: should i need sudo for that?
[16:41] <wwitzel3> tvansteenburgh: umm shouldn't since it is in your home, you might if you attempted to sudo go get anything.
[16:42] <wwitzel3> tvansteenburgh: /home/tvansteenburgh/src/go/pkg/linux_amd64/ that is the folder you want to delete
[16:43] <tvansteenburgh> i did, see paste
[16:43] <tvansteenburgh> the place it's installing is not in my home
[16:44] <tvansteenburgh> it's under /usr/lib/go
[16:44] <tvansteenburgh> i tried unsetting GOROOT but it still used that path
[17:03] <ianrossi> jamespage, Ian Rossi here, long time no see. I was wondering if you could help direct me to the right person at Canonical that  can delete an ubuntu pastebin
[17:17] <noise][> can anyone recommend a dirt-simple charm that exposes a website relation? like just a hello-world page… so far i'm just finding things like wordpress that are too complex for my simple bug repro'ing use
[18:10] <jose> hey cory_fu, have a min?
[18:11] <cory_fu> Sure
[18:12] <jose> cory_fu: I see you opened an MP against a branch I already merged, mind opening it against the parent branch?
[18:12] <jose> https://code.launchpad.net/~johnsca/charms/precise/couchbase/fix-install/+merge/243575
[18:14] <cory_fu> jose: I did mention that MP on the original MP.  I had hoped that mbruzek would have a chance to merge my fix into his branch, or that the person merging the original MP upstream would include mine to fix the tests.
[18:15] <jose> cory_fu: that's why I'm asking if I you can open an MP over there, so I can take a look in a while
[18:15] <cory_fu> jose: That said, sure I can resubmit against the parent.  :)
[18:15] <cory_fu> Sure
[18:15] <jose> \o/
[18:16] <jose> thank you!
[18:17] <cory_fu> jose: https://code.launchpad.net/~johnsca/charms/precise/couchbase/fix-install/+merge/245892
[18:17] <cory_fu> Thanks for taking a look at those
[18:17] <jose> yep, got the email
[18:17] <jose> will look after I'm done with a couple more tests
[18:18] <cory_fu> I wish we had a better or more defined procedure for submitting fixes against other people's MPs
[18:18] <cory_fu> jose: I'm open to ideas for the future.  :)
[18:19] <cory_fu> The review process could certainly use some stream-lining
[18:19] <jose> yeah, my fault over there - saw you reported the bug but didn't see the other branch
[18:20] <cory_fu> Meh.  MPs against MPs seem prone to getting missed like that.  I don't think it's a great method, but it was all I could come up with at the time.
[18:21] <jose> if I do an MP against an MP I tend to contact the owner of the branch to see if I can get it merged before it's reviewed
[18:21] <Mmike> Hi guys. When I'm doing amulet tests, how can I print to stdout? Plain print() produces no output.
[18:21] <noise][> take 2: can anyone recommend a dirt-simple charm that exposes a website relation? like just a hello-world page
[18:22] <cory_fu> jose: Yeah, I think I did mention it to mbruzek at the time, but he's a busy guy and he added tests to a lot of charms.  :)
[18:23] <jose> noise][: the pubphoto charm does a good job over there
[18:24] <jose> Mmike: are you running that test individually? if so, a print('Hello!') should write Hello! on the console
[18:24] <cory_fu> Mmike: Well, I would expect that to depend on your test runner, but if you're using print to debug, I would recommend trying out pdb (or ipdb, if you want to be fancy), since it gives you an interactive session that is more flexible than just prints
[18:25] <Mmike> pudb is actually the neatest I found :) it's ncurses based
[18:25] <cory_fu> Interesting.  I'll have to check that out.  :)
[18:25] <Mmike> but, during the test I want to print stuff on stdout like 'creating habooka', 'testing against habooka', and stuff like that
[18:25] <noise][> jose: thx
[18:25] <Mmike> jose, I do: juju test 02_my_habooka_test.py
[18:25] <Mmike> and print('mario is super!') prints me nothing
[18:26] <jose> Mmike: try running ./02_my_habooka_test.py
[18:27] <Mmike> jose, when I do so then jujuj-deployer complains about not being able to find condiguration in /tmp/amulet-blahblah...
[19:13] <lazyPower> Mmike:  if you're using the juju test runner, i believe it traps output unless you pass teh verbose flag
[19:23] <Mmike> lazyPower, tried that , no dice.
[19:24] <Mmike> dunno what's the issue, I see that amulet has raise_status method which uses print too, but using it also produces no output
[19:24] <lazyPower> Mmike: somethings trapping your stdout - if you run the test directly you say juju-deployer raises errors?
[19:26] <Mmike> yup, I'm assuming 'juju test' creates deployer config or something...
[19:26] <lazyPower> its coming from amulet, amulet wraps juju-deployer
[19:26] <lazyPower> what version of amulet are you running?
[19:26] <Mmike> 1.9.0
[19:27] <Mmike> with juju  1.21-beta4
[19:27] <lazyPower> tvansteenburgh: any thoughts on Mmike's issue above? amulet shouldn't be crying wolf about deployer on latest packaging
[19:27] <nicopace> \quit
[19:29] <Mmike> I created a simple test script which just does print('wonka!')
[19:29] <Mmike> and when I juju test it, nothing is printed
[19:30] <lazyPower> Mmike: tvan is the current maintainer of our testing tools - give him a bit to come aroudn and he should be able to get you lined out.
[19:30] <lazyPower> but you're right, the fact you're getting no output and directly running the tests with exceptions bubbling up about juju-deployer smells of a local configuration problem
[19:30] <Mmike> ack, no rush
[19:31] <Mmike> maybe it's because i'm using juju 1.21, But I can't have my lxcs in /var/lib/lxc, and with juju 1.20 I can't use local envs when I tell lxcs NOT to be placed in /var/lib/lxc
[19:31] <noise][> lazyPower: not sure if you saw it but I added easy repro steps for that HAProxy relation bug, still makes no sense though
[19:32] <lazyPower> noise][: i actually haven't been tracking it as closely as i should be - a bit scattered since i got back from break. I can give it a look later today when i context switch to the queue
[19:33] <noise][> lazyPower: cool, no rush since it's easy to avoid, but damn if it isn't a weird one
[19:33] <lazyPower> yeah, enabling debug changes behavior of the charm - i dont like that at all
[19:38] <tvansteenburgh> Mmike: try using bundletester instead; pip install bundletester; then run it in your charm dir
[19:44] <Mmike> tvansteenburgh, is bundletester replacement for amulet?
[19:44] <tvansteenburgh> no, for juju test
[19:45] <tvansteenburgh> amulet is a testing library, bundletester is a test runner
[19:51] <Mmike> oh, I see
[19:51] <Mmike> neat
[19:56] <rick_h_> thumper: oh buddy oh pal
[19:56] <thumper> o/ rick_h_
[19:56] <rick_h_> thumper: frankban asked me to poke you about his branch and some 'naming of things' questions he had when you showed up
[19:56] <rick_h_> so /me pokes you about all that
[19:56] <thumper> kk
[20:18] <jose> marcoceppi: ping
[20:18] <marcoceppi> o/ jose
[20:18] <jose> marcoceppi: hey, I was checking on one of your MPs but turns out it has conflicts
[20:19] <marcoceppi> oh, which?
[20:19] <jose> https://code.launchpad.net/~marcoceppi/charms/precise/thinkup/tests/+merge/240894
[20:19] <jose> ^
[20:19] <marcoceppi> jose: I'll rectify
[20:20] <jose> thank you :)
[20:20] <jose> please let me know once it's done so I can re-verify the merge
[20:41] <jcastro> lazyPower, https://github.com/juju-solutions/juju-solutions.github.io/pull/20
[20:48] <lazyPower> jcastro: missing the directive in _config.yml
[20:48] <lazyPower> jcastro: commented
[21:00] <jcastro> lazyPower, done, I fixed it just forgot to push, thanks
[21:20] <lazyPower> jcastro: just make sure you frontload your page with a permalink to get the proper page location
[21:20] <lazyPower> jcastro: eg: permalink: /containers.html
[21:21] <jcastro> ack
[21:36] <jcastro> lazyPower, is layout: post fine too?
[21:37] <lazyPower> You'll inherit stuff from teh blog post layout. I can build another layout tonight if you need one.
[21:37] <lazyPower> but to get you moving - yeah thats fine
[21:37] <jcastro> nah, I think we're fine for now
[21:37] <jcastro> the idea is for this content to be moved to the real site anyway
[21:37] <jcastro> so we don't need to spend a ton of time making it pretty
[21:39] <lazyPower> Fair enough