16:03:49 #startmeeting Ansible Network Working Group 16:03:49 Meeting started Wed Feb 26 16:03:49 2020 UTC. 16:03:49 This meeting is logged and archived in a public location. 16:03:49 The chair is pabelanger. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:03:49 The meeting name has been set to 'ansible_network_working_group' 16:04:00 #chair Qalthos 16:04:00 Current chairs: Qalthos pabelanger 16:04:08 #topic Core Updates 16:04:47 Rather then copypaste the bits from last week, I'll link to the previous meeting 16:04:52 #link https://meetbot.fedoraproject.org/ansible-network/2020-02-19/ansible_network_working_group.2020-02-19-16.00.html 16:05:23 the collection migration is soon to be upon us, please follow the upcoming dates 16:05:37 #topic Open Floor 16:05:56 There is no items on the agenda this will, so if people have items now, we can discuss 16:06:04 otherwise, we'll close out here in a few minutes 16:09:57 Anything new on the networking core front? 16:10:29 still getting feet wet with collections and it looks like Palo Alto has been busy on their code 16:11:18 the network team has been working on new resource modules for things like firewall / acls 16:11:39 as well as migrating all content from ansible/ansible into each platform collection 16:11:47 And has anyone been able to set up a backup proxy for ssh for remote routers/switches/firewalls behind bastion hosts? 16:13:26 we have 2 per site and it would be nice if I did not have to manually switch them on failure. If this is not an appropriate question for this group, please let me know. There was no one doing this in #ansible. 16:13:57 Keeping an eye out for new resource modules. We are migrating over as fast as we can. 16:15:47 I am not sure, we do not test it today. But likely can try to understand what is happening 16:17:18 okay, lets wrap up this meeting for today 16:17:20 thanks everybody 16:17:22 #endmeeting