15:02:26 <sshnaidm> #startmeeting ansible-sig
15:02:27 <openstack> Meeting started Tue May 26 15:02:26 2020 UTC and is due to finish in 60 minutes.  The chair is sshnaidm. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:30 <openstack> The meeting name has been set to 'ansible_sig'
15:02:34 <sshnaidm> ok, we have a quorum
15:03:15 <sshnaidm> first and main point - PLEASE add topics for PTG discussion: https://etherpad.opendev.org/p/openstack-ansible-modules-ptg
15:03:44 <sshnaidm> we have hardly for one hour, while I scheduled for 3
15:04:17 <sshnaidm> can be just a brainstorm, don't hesitate
15:04:43 <sshnaidm> OK, second topic - packaging for module
15:05:00 <sshnaidm> I've started to work on RDO RPM for openstack modules
15:05:32 <sshnaidm> mordred, wrt https://review.opendev.org/#/c/730400/ - what is abadger job which you mentioned there?
15:05:44 <sshnaidm> this is about modules install with pip ^
15:05:48 * jrosser also lurks
15:07:27 <sshnaidm> ok, tell me if you have any objections for PIP install of modules
15:08:26 <sshnaidm> and last, but not least - started the work on Ansible collections roles for install, publish, etc in zuul-jobs: https://review.opendev.org/#/c/730360/
15:09:08 <sshnaidm> jrosser, mnaser noonedeadpunk not sure if you have those, maybe will be useful for you as well ^
15:09:54 <noonedeadpunk> oh, so we can pull collections with them without reaching gaqlaxy?
15:10:17 <noonedeadpunk> ah, it's for zuul-jobs
15:10:27 <sshnaidm> noonedeadpunk, it should support both galaxy and pulling from another role that built it
15:11:04 <noonedeadpunk> yeah, I see now
15:11:24 <sshnaidm> noonedeadpunk, or to build from "required-project" if it was cloned by zuul
15:11:41 <sshnaidm> unfortunately ansible-galaxy doesn't support install from a directory yet
15:11:54 <noonedeadpunk> yeah ,that may reduce time for coolections isntallation
15:11:58 <mordred> sshnaidm: he's working on the ACD stuff and one of his ideas is making collections naturally installable via pip
15:12:41 <sshnaidm> mordred, I see.. can it contradict with having setup.py for standalone install?
15:12:50 <mordred> sshnaidm: there are apparently some other people who aren't crazy about that idea - so it's still a questionable thing
15:13:32 <mordred> sshnaidm: well - mostly I was thinking if his thing lands, then we can just do it that way (it would also be via setup.py but into a different location) and if it doesn't I think your way is a great idea
15:14:19 <mordred> I think they need to make a decision rather soon anyway, since they need some answers for how ansible 2.10 is going to work
15:14:46 <sshnaidm> mordred, ok, let's wait then, do you have this the link to their way..?
15:15:07 <mordred> no - I don't think it's all the way public yet (this is from me having some chats with people)
15:15:15 <sshnaidm> mordred, ack
15:15:29 <mordred> but I'll see what I can find out and hopefully have something to link for people by next time
15:15:43 <sshnaidm> yeah, will be great
15:16:08 <sshnaidm> I hope all people here will join PTG session, right? Now it's much easier :)
15:17:15 <sshnaidm> ok, so I'm finished the agenda, does anyone have topics to discuss?
15:18:27 <mordred> oh - well - just to announce - we released 1.0.0 (and 1.0.1)
15:18:44 <sshnaidm> yeah \o/
15:18:53 <gtema> cool
15:18:58 <dtantsur> \o/
15:19:04 <sshnaidm> mordred, btw, do we need to do a release procedure?
15:19:22 <dtantsur> re PTG, I have a partial conflict, but should be there at least for the 2nd part
15:19:33 <sshnaidm> dtantsur, cool
15:19:48 <sshnaidm> I wonder if I need to something like: https://releases.openstack.org/reference/using.html#using-new-release-command
15:19:51 <mordred> sshnaidm: yes!  but I see you have a PTG bullet for that
15:20:34 <mordred> sshnaidm: I think we already have that mostly covered tooling-wise
15:21:10 <sshnaidm> well, I can try to release according to this doc, if I got messed up we'll discuss it
15:21:13 <mordred> we need to make a zuul job to do the release when we tag - but the process I used was basically "git tag -s 1.0.0 ; tox -ebuild ; ansible-galaxy collection upload build/*"
15:21:36 <mordred> sshnaidm: we aren't released via openstack/releases - so we don't need to quite do that stuff
15:22:00 <sshnaidm> mordred, oh, that's because we're not official openstack project?
15:22:08 <mordred> (we aren't an openstack deliverable, just an openstack SIG - so we're not eligible for openstack/releases)
15:22:10 <mordred> yeah
15:22:18 <sshnaidm> I see
15:22:33 <sshnaidm> ok, one thing off the list :)
15:22:39 <mordred> so instead we just want a job in the release pipeline - which is jobs that respond to signed tags
15:22:53 <sshnaidm> mordred, ack, working on that in zuul-jobs
15:22:56 <mordred> ++
15:23:41 <sshnaidm> https://review.opendev.org/#/c/730360/ - still in WIP, but you can poke around
15:24:31 <sshnaidm> and please review 3 patches that we have in pipeline: https://review.opendev.org/#/q/project:openstack/ansible-collections-openstack+status:open
15:25:22 <sshnaidm> ok, so if no any other topics, thanks all for participation!
15:25:28 <sshnaidm> #endmeeting