[12:20] <jcastro> bloodearnest, hey
[12:21] <jcastro> bloodearnest, noodles775: evan is asking (We're at a sprint) on how we test the ansible bits in a charm?
[12:47] <bloodearnest> jcastro: not easily, other than actually running it, which is a downside to using ansible currently
[12:47] <bloodearnest> jcastro: the 2 things I do do are:
[12:48] <bloodearnest> 1) use ansible-playbook --syntax-check to check for typos
[12:48] <bloodearnest> 2) unit test any templates standalone
[12:48] <jcastro> ack, thanks, exactly what we needed to know, thanks.
[12:49] <bloodearnest> jcastro: we've talked about spending some time seeing if we can write something that mocks out ansible at some level (it's all python, after all)
[12:52] <bloodearnest> jcastro: if it's any help, my lint make target is usually: https://pastebin.canonical.com/115051/
[12:56] <bloodearnest> jcastro: in general, once I have a unit up, I find that edit the playbook on the unit with debug-hooks, then using this plugin to save those changes, works pretty well for fast feedback: https://pastebin.canonical.com/115053/
[14:41] <lazyPower> gnuoy: Are you around/avail?
[16:21] <lazyPower> kentb: Ping
[16:28] <kentb> lazyPower, hey
[16:29] <lazyPower> Hey Kent! I'm reviewing the Dell Open Server Management charm in the queue - there's no way i can stub out the calls and validate without a dell power server is there?
[16:39] <kentb> lazyPower, right. you'll probably only get so far with it.  probably as far as the package installation but the dataeng service most likely won't start without a server
[16:39] <kentb> (a dell server that is)
[16:49] <lazyPower> kentb: I can do a full charm review, but without being able to validate this charm i'm not comfortable promoting it to a recommended charm. It can live in a personal namespace - but i'd need access to the physical hardware to get full validation to recommend this particular charm.
[16:50] <lazyPower> this is sad to me, because it looks like an excellent utility for people running dell power edge servers
[16:56] <kentb> lazyPower, I'll make a note and see if maybe we can loan you one or get you access to one somehow
[16:56] <lazyPower> kentb: that would be excellent. For now i'm going to wrap this review as a CR, outline any concerns about not being able to promote under current conditions - when you've settled a path forward ping me directly here and I'll be more than happy to context switch into testing the charm.
[16:57] <kentb> lazyPower, ok. sounds good
[17:48] <jose> mbruzek: ping
[18:01] <lazyPower> jose: he just bailed for lunch
[18:01] <jose> ah, gotcha
[18:01] <lazyPower> something I can help with?
[18:17] <jose> lazyPower: nope, just wanted to confirm the bug he filed for owncloud, and that an MP is in the queue now
[18:17] <jose> thanks though :)
[18:17] <lazyPower> link?
[18:18] <jose> as it was using the repo by default and it grabs the latest version ever, there was a path change and a sed failed, but MP is there
[18:18] <jose> https://code.launchpad.net/~jose/charms/precise/owncloud/update-to-7.0.1
[18:28] <mbruzek> Hello jose
[18:28] <jose> hey mbruzek!
[18:28] <jose> I found out what caused the problem
[18:29] <mbruzek> yeah?
[18:29] <jose> I was focusing in 7.0.0, and 7.0.1 was released maybe a couple days or hours ago? so basically the Sabre path changed and caused the sed to fail
[18:30] <jose> the config options for 'src' were still pointing to 7.0.0, but as the repo gives you the latest one, it was grabbing 7.0.1, causing that
[18:30] <mbruzek> jose ahh
[18:31] <mbruzek> jose what about comment #3, with the ini error?
[18:31] <jose> I haven't been able to reproduce that one
[18:31] <jose> my config-changed ran successfully
[18:32] <mbruzek> Ok let me give it another go.
[18:32] <mbruzek> Thanks for turning this change around for me.
[18:32] <mbruzek> I appreciate it.
[18:33] <jose> no problem, my pleasure