16:00:02 #startmeeting Ansible Network Working Group 16:00:02 Meeting started Wed Nov 2 16:00:02 2022 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 https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 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:23 #topic Agenda https://github.com/ansible/community/issues/542 16:00:31 #link https://github.com/ansible/community/labels/network is where you can always find the latest agenda 16:00:34 #topic Core Updates 16:01:10 o/ 16:01:25 #chair thedoubl3j 16:01:25 Current chairs: Qalthos thedoubl3j 16:01:58 Not a lot new to report this week 16:02:17 yeah, I just got down to the agenda, I was just coming in to ask a question and figured I would hang out for the meeting 16:03:21 #info There will be a new feature release for netcommon soon, but not any other collections 16:04:03 The October release was the major releases a few weeks ago, so this is just a little extra 16:04:40 any huge changes? 16:05:41 Nope, just a new cli_parser plugin to enable other collections to do new things 16:06:31 Qalthos: thanks 16:08:52 I don't think there's anything big planned for November's releases either 16:09:35 Although I could be forgetting something 16:09:57 Will the parser be a general parser or a vendor specific like pyats/genie 16:14:50 It's not a vendor-specific plugin, but I am not entirely sure what it is being used for. 16:15:33 https://github.com/ansible-collections/ansible.netcommon/pull/456 is the PR adding the plugin if you want to know more, but it doesn't do much by itself 16:16:03 Anyway, that's the main thing happening this week 16:16:05 #topic Open Floor 16:16:27 thedoubl3j: You had something you wanted to ask about? 16:17:24 Or did you just show up just as the meeting started and came along? 16:18:21 More of a general question and probably the wrong place for it. But is there any news on the libssh implementation? 16:18:57 I did (and yes that haha), and this might just be me not looking in the right place. I was looking for deprecation examples and landed on netcommon. looking through the runtime of that collection, saw that the cli_parse module was being deprecated but couldn't find it in the collection. did it move already somewhere else? 16:20:00 thedoubl3j: Yeah, the module itself got moved and redirected to ansible.utils https://github.com/ansible-collections/ansible.netcommon/blob/main/meta/runtime.yml#L9 16:20:58 ahh perfect. I missed the redirect line 16:21:36 We still have some parser plugins in netcommon, but the general-purpose stuff got moved to utils so people wanting to use it wouldn't have to depend on netcommon and all the stuff that brings 16:22:18 #topic libssh 16:22:41 oliverl-21: Did you have a more specific question about it? 16:23:42 A couple of people reported issues with Performance the last time I checked the repo 16:24:20 Just to check if the plan is still to move to libssh 16:25:31 libssh has been the default ssh transport since the release of netcommon 3.0.0 in April, although you do have to install ansible-pylibssh to take advantage of it. 16:26:55 And if it’s supported for your platform 16:27:13 It does have some performance problems in certain situations, most notably on very large device output, but overall the feedback I have seen has been majority positive compared to paramiko 16:27:45 That is the idea of making it the default, yes 16:27:59 Ok, thanks 16:28:42 It did have the feature preview a little longer than intended, but that was also removed in 3.0.1 16:30:10 Anything else you wanted to know? 16:30:20 Nope thanks 16:30:21 Cool 16:31:04 #topic Open Floor 16:34:43 I'll give it a few more minutes for anyone else to straggle in, and if not I'm going to close the meeting 16:40:01 #endmeeting