14:00:47 #startmeeting tripleo 14:00:48 Meeting started Wed Sep 25 14:00:47 2019 UTC and is due to finish in 60 minutes. The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:51 The meeting name has been set to 'tripleo' 14:01:06 welcome to another tripleo-transformation meeting 14:01:27 #topic rollcall 14:01:30 o/ 14:01:35 o/ 14:01:37 hows not here today? :) 14:01:43 **who's 14:02:23 I'm here today :-) 14:03:35 I might be here :) 14:04:31 Hey 14:04:38 * d0ugal is mostly here 14:04:40 o/ 14:05:09 well hopefully a couple more folks join in as we go. 14:05:19 #topic recap 14:05:20 Etherpad 14:05:20 #link https://etherpad.openstack.org/p/tripleo-ansible-agenda 14:05:20 Work-board 14:05:20 #link https://storyboard.openstack.org/#!/board/174 14:05:21 Project 14:05:22 #link https://storyboard.openstack.org/#!/project/openstack/tripleo-ansible 14:05:23 Open Reviews in need 14:05:24 #link https://review.opendev.org/#/q/project:%255Eopenstack/tripleo-ansible+status:open+label:verified%253D%252B1%252Cuser%253Dzuul 14:05:25 THT2TA work in need of reviews 14:05:26 https://review.opendev.org/#/q/topic:THT2TA+(status:open) 14:05:40 as a reminder, these are some of our useful links 14:06:01 much of the work-board is on hold until we get train out the door. 14:07:06 lots of stabilizing changes have gone into tripleo-ansible, which has been great. there are some open reviews, if folks have time to do some reviews it'd be greatly appreciated. 14:08:41 cross project collaboration with the ansible-sig has started (-cc mnaser) and while early, looks very promising. 14:09:24 #topic meeting schedule 14:09:54 with the cycle well underway, and as we approach the end of the year, I wanted to know if folks think we should still be having this meeting weekly ? 14:10:19 or if we should just roll up into the larger tripleo meeting, like the other squads ? 14:10:39 +1 for meeting conslidation 14:10:42 o/ 14:11:17 early on there was a bit more participation as we were defining things, I think we're hitting a stride, so IDK if this meeting still makes sense ? 14:11:47 sshnaidm d0ugal EmilienM Tengu owalsh? 14:12:11 i havent been around cause i've been busy with things but i've been watching from the sidelines :< 14:12:12 maybe separate part of tripleo meeting after it, because mixing all together could be confusing 14:12:21 I've a ton of PTO next month so +1 14:12:22 cloudnull: I have not been good enough at attending to judge - was making a active attempt at improving that :) 14:12:34 cloudnull: but if it fits into the tripleo meeting that would work for me 14:13:20 sshnaidm there's a squad update part in the larger tripleo meeting, maybe we could just slot in there? 14:13:35 +0 (not a fan of meetings in general, i like async work) 14:14:00 I know there's a lot of meetings to attend, so maybe one less to keep track of is a good thing. 14:14:03 what EmilienM said :) 14:14:11 +1 14:14:23 I like frequent updates on ML though 14:14:26 cloudnull, I think it's just posting links to etherpads :) 14:14:35 like a journal and people can comment if needed 14:15:24 +1 14:15:25 cloudnull, like we have "open discussion" in tripleo mtg we can have "ansible squad discussion" maybe 14:15:40 +1 14:16:09 I'll take an action item to write a weekly squad update and post it to the ML 14:16:27 and I think we can halt this meeting for the time being. 14:16:42 +1 for what EmilienM said in fact 14:16:56 Merged openstack/tripleo-common stable/stein: Add profile_tasks to ansible runs https://review.opendev.org/684305 14:16:58 if we get to a place where we think it makes sense to start having them again, I'd be happy to facilitate that 14:17:21 +42 14:17:22 cloudnull: thanks 14:17:33 #action the tripleo-ansible squad will post weekly updates to the ML to keep folks in the loop 14:17:34 or maybe we can revive the TripleO Owl :D 14:17:43 EmilienM, yay! :) 14:17:54 (i stopped writing it) 14:17:54 EmilienM: do you have new owl facts? :] 14:18:02 Tengu: i always find new facts 14:18:07 :D 14:18:11 #topic open discussion 14:18:20 owls are fact-inating 14:18:29 ... 14:18:36 maybe a bad pun? ok. 14:18:37 ;) 14:19:00 I submitted a patch with podman_container module: https://review.opendev.org/#/c/682458/ 14:19:08 but not sure what to do with it.. 14:19:16 * cloudnull looking 14:19:31 it was merged in ansible and reverted later, because no idempotency for running containers 14:19:39 sshnaidm: great start. We'll need it I think if we build a plan around replacing paunch 14:19:45 sshnaidm nice! 14:20:03 good update to that old podman module. 14:20:06 so I'll continue to work on it to have idepmpotency in running podman containers 14:20:31 and in ideal case to have it in ansible in some point.. 14:20:43 we also have podman_image and podman_image_facts in there 14:21:04 cloudnull, actually facts and image are parts of ansible now, so we can drop them I think 14:21:16 cloudnull, at least from 2.8 14:21:18 ++ to remove them then 14:21:26 to the best of my knowledge IDK if we use any of those modules in TripleO? 14:21:31 sshnaidm +1 14:21:38 cloudnull, I don't think we use them anywhere 14:21:46 we don't. 14:22:27 also I started a podman_pod module for ansible and maybe it can be helpful even more with paunch 14:22:56 it allows to operate podman containers in pods, seems like nice thing to have 14:22:58 Kevin Carter (cloudnull) proposed openstack/tripleo-ansible master: Remove modules that have been up-streamed https://review.opendev.org/684758 14:23:06 ^ 14:23:31 yeah for now I would not spend time on pods but rather on how we can replace paunch by calling this new module 14:23:42 +1 14:23:44 sshnaidm: let's work on it together, i want to help on that front 14:23:48 that sounds like a great idea 14:23:52 EmilienM, sure 14:24:07 and after pods it's just little move to kubernetes.. 14:24:09 that said, I think the paunch module is a good intermediate step 14:24:10 * sshnaidm hides 14:24:15 what I mean to say is: spend time in pods if you want the community to use the new module but in tripleoitself, it's not critical now 14:24:28 cloudnull: right 14:24:34 EmilienM, yeah, agree 14:24:43 sshnaidm: you said the forbidden word 14:24:53 :8 14:25:12 pods? :D 14:25:20 if we run a little kubernetes on it, everything will be perfect 14:25:35 :D 14:25:56 50 pullups for K-word 14:26:01 hahahaha 14:26:16 I think that's a burpees offence 14:26:28 it was big discussion about collections in ansible fest 14:26:43 ++ 14:26:45 seems like this is future "packages" of roles/libs/.. 14:27:15 maybe point to think if we can use this in tripleo-ansible 14:27:25 tripleo-ansiible, while not setup in an "ansible-collection" currently, its not a large leap. 14:28:38 Could be a good goal for the U release to get that reorganized. 14:28:43 I think once they iron out the spec it might be worth our while 14:28:51 Michele Baldessari proposed openstack/puppet-pacemaker master: WIP be able to change pcmk resource op defaults https://review.opendev.org/664606 14:29:01 yeah, it's still under heave discussion about best practices 14:29:07 as I understood 14:29:32 https://galaxy.ansible.com/docs/contributing/creating_collections.html -- doesn't look like its up-to-date 14:30:52 I read here: https://docs.ansible.com/ansible/devel/user_guide/collections_using.html 14:30:53 ie still references mazer, which is deprecated in 2.9 - https://github.com/ansible/mazer 14:31:25 oh I guess thats more up-to-date 14:32:08 Michele Baldessari proposed openstack/puppet-tripleo master: WIP pcs resource op defaults https://review.opendev.org/664612 14:34:24 either way I think we wait for folks to work out a little more of the details before we move to collections 14:34:30 sshnaidm you at ansible fest? 14:34:39 cloudnull, virtually :) 14:35:08 ah, me too :) 14:37:45 btw, ara was built as rpm today, so maybe we'll have it soon in rdo repos, and then can think about using it in product 14:38:00 kudos to dmsimard ^^ 14:38:07 that's awesome! 14:39:38 it's only in rawhide right now, should be in f31 and f30 in the near future -- haven't looked at epel8 or rdo yet 14:39:46 but yes, it's been a long journey of chasing packaging rabbitholes 14:42:41 dmsimard++ 14:43:32 anything else folks want to talk about. otherwise I think we can wrap this meeting up 14:47:52 thanks everyone, have a great rest of your day. 14:47:55 #endmeeting