17:02:41 <chouseknecht> #startmeeting ansible-container
17:02:41 <zodbot> Meeting started Mon Feb  5 17:02:41 2018 UTC.  The chair is chouseknecht. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:41 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:02:41 <zodbot> The meeting name has been set to 'ansible-container'
17:02:45 <fabianvf> chouseknecht: I think with time I can learn to forgive you
17:03:02 <chouseknecht> LOL
17:03:51 <chouseknecht> ttomecek: j00bar:
17:03:55 <chouseknecht> anyone around?
17:04:07 <ttomecek> o/
17:04:29 <chouseknecht> fabianvf: how goes it with the dynamic client spec document you started? has anyone else contributed?
17:05:11 <fabianvf> chouseknecht: haven't gotten any feedback on it as of my last check, unfortunately. I've been reading the go client dynamic stuff, and have a pretty good replica of the discovery logic in python I think
17:05:29 <chouseknecht> fabianvf: nice
17:05:30 <fabianvf> chouseknecht: I was going to put my discovery logic pseudocode into the document along with a few questions
17:05:44 <chouseknecht> fabianvf: that makes sense
17:06:13 <fabianvf> chouseknecht: unfortunately a lot of my time is being eaten up by the 3.9 release, I don't think I'm going to be able to answer all the questions I posed in the initial document by Friday
17:06:19 <j00bar> Present and accounted for.
17:06:27 <fabianvf> chouseknecht: but I think we can have a productive conversation about the discovery process at least
17:07:35 <chouseknecht> fabianvf: adam miller and/or james cammarata will be at the next meeting. i think it's Friday. they'll be helping from the Ansible side.
17:07:40 <fabianvf> chouseknecht: I also have a list of all the actions that kubernetes defines, and I'm not totally sure what all of them mean, so I'm bringing that up on Friday as well. Once we have discovery, and the proper way to handle each action, implementation of the full client should be easy
17:08:01 <fabianvf> chouseknecht: I'm reusing all of the generated rest/api client stuff as well, it's all just working out of the box
17:08:19 <chouseknecht> j00bar: ttomecek: any takeaways or plans / roadmap items from this morning's buildah meeting?
17:08:47 <j00bar> TL;DR they're not all-in on Ansible Container but they'll provide technical advice and a marketing platform should we suceed.
17:08:50 <j00bar> * succeed
17:08:57 <j00bar> But chicken/egg problem for audience.
17:10:12 <ttomecek> during devconf, I got feedback from some other people that they would help
17:10:32 <j00bar> That would be cool - I still owe you a pretty comprehensive review, ttomecek
17:10:56 <chouseknecht> i'm not sure they (OpenShift, and whichever product group Ben Breard represents) are convinced that Ansible is a worthwhile way to build images.
17:10:58 <ttomecek> it's up to us now; I really hope I'll find time to finish the PR so that it can be reviewed and tried locally (it's really far from being on par with docker backend)
17:11:36 <ttomecek> the other thing is that we might need a buildah ansible module if we want to do the chroot thing -- the conn plugin can't do that now
17:11:44 <j00bar> My plan for the week includes a few bug fixes and then the 0.9.3 release
17:11:45 <chouseknecht> sounds like they're currently attempting to hook buildah into OpenShift as a build strategy
17:11:49 <ehelms> I'm here of sorts, I really gotta learn to get food before noon on Mondays
17:12:01 <j00bar> I'm on PTO starting Thursday, which means if I do any work I DO WHAT I WANT YOU'RE NOT THE BOSS OF ME
17:12:14 <ehelms> chouseknecht: I'm curious then, what they believe is the language of building images? all bash all the time?
17:12:15 <ttomecek> j00bar, nothing to be reviewed yet :/
17:12:33 <j00bar> ttomecek: We should talk about the approach you're using.
17:13:00 <j00bar> ehelms: They're split. On one hand, some don't see what's wrong with the Dockerfile. On the other hand, some people want to use anything but Dockerfile.
17:13:54 <chouseknecht> ben breard's team is working on using Dockerfile to drive buildah. Dan Walsh, on the hand, wants to remove all mention of 'docker' from everything, including builds.
17:14:52 <ehelms> for simple containers, I kinda get it, when I look at large, multi-service projects, I shudder at the thought of not having something that cna coordinate it all
17:15:11 <j00bar> ehelms: that was the essence of the argument i gave them
17:16:50 <ttomecek> and we probably should shout more
17:17:01 <ttomecek> that
17:17:27 <ehelms> j00bar: +1, I'd be curious to see how they would handle one, so many talks and examples are ... simple
17:18:06 <j00bar> Well, this is a good opportunity to bring an interesting story.
17:18:30 <j00bar> I'm still a little concerned that buildah has zero intentions to have native win/mac support.
17:19:51 <ttomecek> that's probably the difference b/w both departments: everyone has different goals
17:20:16 <j00bar> Definitely true.
17:20:31 <j00bar> Anyway, algo mas?
17:22:10 <ttomecek> Za mna nič :P
17:23:32 <j00bar> Pro mě, traktor, řepka, hýždě.
17:23:54 <j00bar> Whoa.
17:24:39 <j00bar> Google Translate is weird.
17:24:42 <j00bar> Anyway, adjourn?
17:24:46 <ttomecek> that's a tough one :D
17:24:53 <ttomecek> thanks for a nice chat!
17:25:00 <j00bar> Tractor! Turnip! Buttocks!
17:25:06 <chouseknecht> thanks, everyone!
17:25:12 <chouseknecht> #endmeeting