15:02:59 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:02:59 <opendevmeet> Meeting started Tue Sep  7 15:02:59 2021 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:00 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:03:04 <noonedeadpunk> #topic rollcall
15:03:07 <noonedeadpunk> \o/
15:04:05 <mgariepy> hello ! \o/
15:06:07 <noonedeadpunk> #topic office hours
15:06:10 <noonedeadpunk> So
15:06:18 <noonedeadpunk> Eventually I have a thing to discuss
15:06:48 <noonedeadpunk> I made a patch to the config_template to make it installabe as a collection https://review.opendev.org/c/openstack/ansible-config_template/+/807581
15:07:14 <noonedeadpunk> The question here is how we want to name it and under what namespace to put
15:08:10 <noonedeadpunk> I talked to sshnaidm yestarday and eventually we have 2 options: we can go under `openstack` namespace or we can register our own one in the galaxy
15:08:57 <noonedeadpunk> While I'd say it would be logical to go with openstack, tricky thing is that access to that namespace is not owned by governance but it's more like personal account with single admin in it
15:09:33 <noonedeadpunk> The pros though that there's already a releasing process we could apply
15:10:22 <noonedeadpunk> Eventually, I thin kwe have more modules to make installabe as a collections - potentially whole https://opendev.org/openstack/openstack-ansible-plugins and our parallel git clone thing
15:11:46 <noonedeadpunk> Or, we can register some new namespace in galaxy and manage it, and see where this will go
15:13:42 <mgariepy> not sure what is the best namespace but i guess that this kind of module could be helpful for more than just openstack
15:16:12 <noonedeadpunk> Eventually namespace is kind of name of the account in galaxy as far as I got
15:16:37 <noonedeadpunk> but it's totally more then just osa...
15:17:41 <noonedeadpunk> well, even if it's `openstack` namespace - the only thing namespace reflects is `fqdn` path to the collection that you would need to provide when calling for a module
15:17:55 <noonedeadpunk> ie `openstack.config_template.config_template`
15:18:13 <noonedeadpunk> or `openstack_ansible.config_template.config_template`
15:18:21 <noonedeadpunk> jrosser: any thoughts?
15:18:32 <mgariepy> if it's not under the openstack ns it might be easier for other ppl to find/discover it ?
15:21:47 <sshnaidm|off> is there non-openstack usage of it?
15:24:16 <mgariepy> there are a lot of services that use either json,yaml,ini file as config
15:28:34 <sshnaidm|off> then probably worth to have a separate namespace
15:29:15 <noonedeadpunk> What I have concerns about, is that if we want to create and manage multiple namespaces...
15:29:54 <noonedeadpunk> well, the best place for it might be smth like `community` but I really doubt we have chances to push it there
15:37:41 <mgariepy> hmm indeed i guess it cloud be hard to push there.
15:44:41 <noonedeadpunk> Might be worth asking TC opinion as well then...
15:45:02 <noonedeadpunk> Because in our case comparing to openstack ansible modules, we're not tighten with license
16:00:29 <noonedeadpunk> #endmeeting