16:59:03 <chouseknecht> #startmeeting ansible-container
16:59:03 <zodbot> Meeting started Mon Feb 19 16:59:03 2018 UTC.  The chair is chouseknecht. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:59:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:59:03 <zodbot> The meeting name has been set to 'ansible-container'
16:59:22 <j00bar> House had his coffee this morning 👍
16:59:34 <chouseknecht> j00bar: i did!
17:00:22 <chouseknecht> fabianvf: where did we leave off last week with 0.4.x of the OpenShift client?
17:00:48 <chouseknecht> wanting to get that wrapped up today or tomorrow, and pushed into Ansible 2.5
17:01:32 <fabianvf> chouseknecht: 0.4.3 with all the changes from friday is live on pypi
17:01:45 <chouseknecht> fabianvf: sweet!
17:02:11 <chouseknecht> i'll poke at it from the Ansible side, and see if everything is good to go
17:02:24 <fabianvf> chouseknecht: I think there may still be a few bugs to fix, but a lot of them are actually from the kubernetes 4.0 due to some validation changes with swagger generation
17:03:10 <chouseknecht> fabianvf: i think we can let the community find and report those. i'm more concerned that the basics functionality all works.
17:03:30 <fabianvf> chouseknecht: ack, I'm pretty confident about base functionality
17:03:38 <j00bar> We upped the dependency in Ansible Container too (thanks @ehelms )
17:04:23 <fabianvf> chouseknecht: haven't found much time to work on the dynamic client unfortunately, I'm leaning towards pushing the friday WG back a week atm
17:04:52 <fabianvf> cycles are hard to come by with the 3.9 release
17:05:17 <chouseknecht> fabianvf: we can totally push that meeting. i don't think there is an emergency.
17:06:05 <ehelms> j00bar: woot, thanks for taking a look at that
17:08:18 <chouseknecht> j00bar: anything to discuss?
17:09:48 <j00bar> I'm going to cram in a-c work this week.
17:10:02 <j00bar> I'm transitioning back over to the Ansible side of things for the fiscal year turnover.
17:10:11 <j00bar> Expect a release before month's end.
17:10:40 <chouseknecht> j00bar: wha? that's cool.
17:10:53 <chouseknecht> hope that's a good thing.
17:10:57 <j00bar> Yeah. Expect news on that front.
17:12:14 <chouseknecht> ttomecek: you out there?
17:14:31 <chouseknecht> anyone have anything?
17:14:48 <chouseknecht> if not, I move we adjourn the meeting
17:14:50 <ehelms> I have a question I guess.
17:15:28 <j00bar> Fire away
17:15:37 <ehelms> If an issue is a better place to discuss, I've been thinking about how it'd be nicer if the deployment role was more generic and didn't force me to push to the registry to generate it.
17:16:00 <ehelms> This might fall a bit in line with the depoyment artifacts change proposal
17:16:03 <j00bar> There's a way....
17:16:07 <j00bar> But I think the option should be renamed.
17:16:20 <j00bar> If you do `ansible-container deploy --local-images` it doesn't do a push
17:16:28 <j00bar> I think it should be `--no-push`
17:16:49 <j00bar> Oh, but it changes the image references too, I think, right House?
17:17:28 <chouseknecht> j00bar: yep
17:17:37 <ehelms> does it also variablize the registry/openshift instance in the deployment role?
17:18:16 <chouseknecht> it does not 'variablize' the registry reference
17:18:32 <ehelms> in my workflow I tend to think, an openshift is an openshift, if I could generate the role (maybe keep it in source control) and then just point it wherever I want or spin up up cluster after the fact that'd be a nice freedom to have
17:18:58 <j00bar> That would make a good issue.
17:19:03 <ehelms> do you feel this would be an OK direction to go? I started looking into the code but realized I was... deep
17:19:31 <j00bar> Ever since ryansb got sucked back into Ansible Core work, deploy has not had much love.
17:19:46 <j00bar> I think more knobs-dials makes sense.
17:20:04 <chouseknecht> `deploy` needs a refactor for sure
17:20:09 <ehelms> i'll fire up an issue to capture my thinking
17:21:13 <j00bar> Thank you - sincerely.
17:22:51 <Pilou> I have a question too: why '--vault-password-file' switch isn't available with 'build' command ?
17:23:58 <chouseknecht> pilou: vault was added as a way to support instantiating secrets during deployment
17:24:19 <chouseknecht> that's not to say that it couldn't or shouldn't be available during build
17:25:27 <Pilou> ok. thank you for the answer :)
17:26:13 <chouseknecht> you can pass arguments to `ansible-playbook` during build, so you should be able to pass `--vault-passwod-file`
17:26:39 <j00bar> It would be worth reconsidering the use cases for that feature so we're covering our bases.
17:26:49 <j00bar> Pilou - would you mind opening an issue with the use-case you envision?
17:27:15 <Pilou> yep, i will create an issue
17:27:42 <j00bar> Much obliged.
17:30:03 <chouseknecht> anything else, or shall we adjourn?
17:30:24 <ehelms> I have nothing else.
17:32:29 <chouseknecht> going once...
17:32:47 <chouseknecht> twice...
17:33:00 <chouseknecht> #endmeeting