15:00:11 <sshnaidm> #startmeeting ansible-sig
15:00:12 <openstack> Meeting started Tue Mar 31 15:00:11 2020 UTC and is due to finish in 60 minutes.  The chair is sshnaidm. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:15 <openstack> The meeting name has been set to 'ansible_sig'
15:00:25 <sshnaidm> hi all, who is available today?
15:01:03 * cyberpear eavesdrops
15:01:10 * mordred waves
15:01:20 <dtantsur> o/
15:02:12 <sshnaidm> ok, let's move on
15:02:34 <sshnaidm> no specific agenda for today, I'd like to give some updates from Ansible
15:02:57 <sshnaidm> I've been on Sunday Ansible contributors virtual mtg, we talked about collections
15:03:33 <sshnaidm> so all community modules should be part of ACD (Ansible community distribution), which will be released much more frequently than half-year release of Ansible
15:03:50 <sshnaidm> how it will sync with all releases of various modules is not clear yet
15:04:06 <dtantsur> an openstack-style coordinated release?
15:04:32 <mordred> dtantsur: it seems the process is that they pull in the collections when they build ACD tarball
15:04:34 <sshnaidm> dtantsur, that's unclear currently what will be a cadence
15:04:46 <sshnaidm> yeah, kind of
15:05:02 <sshnaidm> I'll post lately some links with WIP ideas from Ansible folks
15:05:02 * mordred has a crazy thought related to releases for us to come back to in a bit
15:05:05 <mordred> ++
15:05:34 <mordred> once the actual ACD build process is nailed down - I'd like to run at least some part of the ACD build in our jobs so we can test that we're still working with what they're expecting
15:06:23 <sshnaidm> mordred, yeah, it seems reasonable
15:06:41 <sshnaidm> I hope other modules won't break ours and this is independent system
15:07:19 <sshnaidm> but building ACD with our latest code seems a good test for me
15:07:50 <sshnaidm> just need to understand how things are taken into ACD
15:08:16 <mordred> yup
15:08:26 <mordred> which I think means it needs to be defined first - since that's still WIP for them ;)
15:08:28 <sshnaidm> and I must to admit openstack ansible modules are in good shape unlike many other modules..
15:08:38 <sshnaidm> mordred, yep
15:09:05 <sshnaidm> at least from CI and tests perspective
15:09:22 <sshnaidm> which takes I to next point
15:09:36 <sshnaidm> I think we're all covered in all branches except of rocky
15:09:56 <dtantsur> Rocky is EM, right?
15:10:08 <sshnaidm> EM..?
15:10:12 <mordred> extended maint
15:10:14 <dtantsur> extended maintenance
15:10:19 <dtantsur> alive-but-not-really
15:10:27 <mordred> and yeah - I don't really think people shold be doing much with rocky openstacksdk
15:10:39 <mordred> (I don't really think they should be doing much with train openstacksdk - but I know I'm going to lose that battle)
15:10:49 <dtantsur> :D
15:11:01 <cyberpear> I'm using it because Queens is too old.
15:11:04 <dtantsur> true vikings consume only master
15:11:28 <mordred> well - just as a quick reminder for everyone who might not know - latest sdk should ALWAYS work with *all* older versions of openstack
15:11:34 <cyberpear> and RH doesn't ship any newer SDK than Rocky for RHEL7
15:11:40 <mordred> it is not necessary to install an sdk matching your version of cloud
15:11:51 <mordred> cyberpear: yeah - that I can't help with - and is a fair reason to use it ;)
15:12:04 <sshnaidm> while rocky is blocked for incoming patches including breaking patches, I'm fine :)
15:12:14 <sshnaidm> but better to settle it
15:12:26 <sshnaidm> it's some python deps hell there
15:12:33 <sshnaidm> nothing serious
15:12:54 <mordred> yeah- I am not opposed to fixing those
15:13:10 <mordred> having CI jobs able to work is not a bad thing, even if it's in EM
15:14:06 <dtantsur> "not a bad thing" :)
15:14:45 <sshnaidm> and for testing new features of SDK with current modules I pass openstacksdk version to test roles: https://review.opendev.org/#/c/715620/
15:15:04 <sshnaidm> please use it for now, until we come with a better solution
15:15:07 <mordred> ++
15:15:47 <sshnaidm> mordred, can we have something pushed to galaxy already? like 0.x version
15:16:13 <sshnaidm> I'm starting to look at building/pushing jobs
15:16:39 <sshnaidm> so maybe we can set up releasing procedure in the near future
15:17:17 <sshnaidm> but I think it's fine to push it manually for now
15:17:33 <mordred> we do
15:17:40 <mordred> already there
15:17:46 <sshnaidm> oh, great
15:18:06 <mordred> https://galaxy.ansible.com/openstack/cloud
15:18:38 <sshnaidm> which version is it?
15:18:43 <mordred> it's been a bit shaky - there's been issues with the tarball built being inconsistent - so we should make sure we're producing consistent tarballs before we tag anything 1.0
15:18:49 <mordred> 0.0.1-dev83
15:19:56 <sshnaidm> ok, so we need to add "--pre" like: ansible-galaxy collection install openstack.cloud --pre
15:20:13 <sshnaidm> until it has release 1.*
15:21:17 <sshnaidm> so that's it for me for now
15:21:32 <sshnaidm> any topics to talk, folks?
15:22:20 * dtantsur cannot think of anything
15:22:49 * mordred had one - but just spoke with sivel and turns out it may not be a thing
15:23:02 <sshnaidm> mordred, what was it?
15:23:04 <dtantsur> stop intriguing us :)
15:23:11 <mordred> but the tl;dr is that it's possible to install an ansible_collection as part of the install of a python library
15:23:17 <mordred> ansible scans sys.path
15:23:21 <dtantsur> via pip install?
15:23:28 <mordred> so I was pondering the idea of bundling the collection with sdk
15:23:30 <mordred> BUT
15:23:43 <mordred> it's a purposefully undocumented feature and is intended to only be there to support ACD
15:23:53 <mordred> so I think it's best to stay away from that for now
15:24:05 <dtantsur> good, undocumented features are never abused by curious people
15:24:17 * dtantsur may be overly sarcastic today
15:24:21 <mordred> :)
15:24:26 <gtema> oh yes, you are
15:24:57 <dtantsur> nice! I was afraid for a second that I'm always overly sarcastic.
15:25:02 <sshnaidm> btw, if you want to install it from git, it's like: git clone https://github.com/namespace/collection ~/.ansible/collections/ansible_collections/namespace/collection
15:25:31 <sshnaidm> and it should work if you have plain structure in your repo
15:26:02 <mordred> yeah
15:26:38 * dtantsur wonders why collections/ansible_collections, are there any other sort of collections in ansible?
15:27:02 <cyberpear> nope, it's a known issue
15:27:10 * cyberpear also annoyed by it
15:27:26 <sshnaidm> seems more like philosophical question
15:28:07 <sshnaidm> ok, so if no more questions, I think we can end the meeting
15:28:15 <mordred> woot
15:28:16 <sshnaidm> #endofmeeting
15:28:23 <sshnaidm> #endmeeting