16:00:02 #startmeeting Ansible Network Working Group 16:00:02 Meeting started Wed Jan 22 16:00:02 2020 UTC. 16:00:02 This meeting is logged and archived in a public location. 16:00:02 The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:02 The meeting name has been set to 'ansible_network_working_group' 16:00:10 #topic Core Updates 16:00:39 #chair ganeshrn pabelanger ikhan dmellado justjais 16:00:39 Current chairs: Qalthos dmellado ganeshrn ikhan justjais pabelanger 16:02:20 o/ 16:02:39 #info Work on ACL resource modules is continuing 16:03:14 #link https://github.com/ansible/community/wiki/Network%3A-2.10-Roadmap for more details on that and what else is planned 16:04:27 #info Collections for core-supported platforms are nearing their final shape 16:04:46 pabelanger can talk more eloquently about that if he wants to 16:05:31 Yup! Things are looking real good now 16:05:39 we have 7 collections, working on final this week 16:06:01 I'm happy to say all (but 1 test) is passing for both ansible/ansible devel and new collections 16:06:16 so, we have a high level of confidence when people get to use them, they will just work 16:06:43 #link https://github.com/ansible/community/labels/network is where the agenda for this meeting can always be found 16:08:13 There's a few items this week, but I think the first one is handled 16:08:58 #topic citrix_adc_cs_action module 16:09:09 Hi 16:09:23 georgen: Are you the PR author? 16:09:23 About the PR I would like to ask 2 things 16:09:45 Yes I am the author of the PR 16:10:18 So from what I understand going forward ansible-galaxy is the preferred distribution method 16:10:39 Q1: We need to deprecate the netscaler_* modules in favor of citrix_adc* ones 16:10:53 How do we forward to the ansible-galaxy collection? 16:11:17 Q2: How do we get the Citrix namespace under galaxy. Do we have to be an Ansible partner? 16:12:26 open ticket in galaxy on github 16:14:08 ticket about the forwarding? 16:14:13 To the first question, I'm not sure if there is a suggested form to use, but a PR with just the deprecation and a reference to the new collection in the `alternative` field of the module should be sufficient, I think 16:14:30 georgen: I'm assuming bcoca is talking about securing the namespace 16:15:30 Ok thanks 16:15:41 I will open a ticket about the namespace 16:16:15 ^ what he said, for namespaces you just request in a ticket 16:16:28 you also have #ansbile-galaxy channel 16:16:52 georgen: Once that's all set up, you can submit a new PR for the deprecation 16:17:19 Yes I will do that. Thank you. 16:19:00 #topic exos_guest_virtual_machines module 16:19:11 #link https://github.com/ansible/ansible/pull/66248 16:22:38 Hi @Qalthos.. Andrius commented that he wishes it to be seen as a collection.. 16:23:18 ujwalkomarla: Yes. Do you still want to talk about this PR? 16:24:02 What is the review process, if there will be one, when we move to collections? 16:24:03 Theoretically, we can still go over and merge it... this isn't creating a new category 16:24:21 But it will have to get moved to a collection at some point anyway 16:24:35 I would be happy if this can be merged! 16:25:33 I will certainly take a look into creating a collection.. though at first I need to figure out being added as an owner to the galaxy namespace. 16:26:06 As my colleague had an issue of adding me as the owner to the namespace. 16:27:24 My main point is none of this is going to stay in ansible even if we merge it 16:28:58 You are probably better served getting a collection running, as any code that gets merged will have to be moved into the collection anyway 16:29:41 I see. Okay, then, let me look into creating and migrating to collections. 16:30:27 What are your thoughts on review process for contents in collections? 16:32:54 I mean, it's your repository. That's sort of the point, that you're no longer blocked on our reviews 16:33:36 Gotcha! 16:33:37 Thanks! 16:34:00 ujwalkomarla: Any other concerns about this PR? 16:34:10 Nope. That was it. 16:35:03 #topic Open Floor 16:35:26 Anyone have any topics they'd like to bring up that aren't on the agenda? 16:37:39 If nothing comes up, I'll end this early at :45 16:51:21 #endmeeting