16:00:20 <Qalthos> #startmeeting Ansible Network Working Group
16:00:20 <zodbot> Meeting started Wed Jun 30 16:00:20 2021 UTC.
16:00:20 <zodbot> This meeting is logged and archived in a public location.
16:00:20 <zodbot> The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:20 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:00:53 <Qalthos> #topic Agenda https://github.com/ansible/community/issues/542
16:01:12 <Qalthos> #info The current agenda can always be found at https://github.com/ansible/community/labels/network
16:01:23 <Qalthos> #topic Core Updates
16:02:26 <Qalthos> #info I still haven't seen videos from the Contributor Summit earlier this month, I will pass them along when I do
16:02:30 <Qalthos> #chair GomathiselviS
16:02:30 <zodbot> Current chairs: GomathiselviS Qalthos
16:03:26 <Qalthos> #info The next Contributor Summit will be happening around AnsibleFest 2021 time, which is September 29-30
16:04:48 <Qalthos> #link https://www.ansible.com/ansiblefest for more details on AnsibleFest itself
16:05:36 <Qalthos> GomathiselviS: anything you want to add this week?
16:08:03 <GomathiselviS> I donot have anything from my side.
16:08:08 <Qalthos> Alright, then
16:08:17 <Qalthos> #topic Open Floor
16:08:37 <Qalthos> If anyone has anything they want to discuss this week, let me know
16:10:18 <sc68cal> I saw https://github.com/ansible-collections/arista.eos/issues/133 yesterday, and was interested to see what else in the arista.eos collection is impacted by the CLI changes that Arista is doing in the new releases
16:10:44 <sc68cal> I haven't been able to get the notes from Arista for what they changed yet, but I assume a lot of the eos collection is impacted
16:11:06 <sc68cal> so it'd be great to maybe put together a list of impacted parts of the code, so that others could jump in and make the fixes
16:11:09 <GomathiselviS> sc68cal: The details of the changes are available in https://www.arista.com/en/support/advisories-notices/fieldnotices/7097-field-notice-39.
16:11:27 <sc68cal> right but that requires logging into arista's site, have to re-activate my account
16:11:39 <Qalthos> #topic EOS syntax changes
16:12:27 <GomathiselviS> This PR : https://github.com/ansible-collections/arista.eos/pull/134 provides support for a couple of changed cli commands.
16:13:35 <GomathiselviS> For the rest, I am planning to work on them, mostly in August.
16:14:05 <sc68cal> right, I appreciate that you re-opened the bug, but I think maybe we need to create a table or some sort of documentation in the bug, based on that field notice
16:14:07 <GomathiselviS> I have the doc downloaded. I can mail it to you
16:14:32 <sc68cal> like for example - I see "neighbor peer-group" -> "neighbor peer group"
16:14:32 <GomathiselviS> sure, that sounds reasonable. I shall do that.
16:14:58 <GomathiselviS> I shall update the issue, with the details.
16:15:20 <sc68cal> yeah. I think maybe three columns, the old syntax, new syntax, and a general guess as to which role is where it needs to change
16:15:37 <Qalthos> #action GomathiselviS update issue to list eos syntax changes and track progress on adding them
16:15:49 <sc68cal> so for that example of peer group, those two lines, and then..... eos.eos_bgp_address_family_module ?
16:16:02 <GomathiselviS> got it !
16:16:26 <sc68cal> I can assist in some modules that I am consuming, but mainly we just need to organize the work so we don't duplicate effort
16:17:39 <GomathiselviS> Right. I would like to have the modules to provide backward compatibility. Your views on that?
16:17:42 <sc68cal> I also have a VM with Arista EOS 4.24.1.F available, if we have some sort of test suite that I can run against it and just gather up all the syntax errors
16:18:28 <sc68cal> I think versions before 4.24 (where they did the syntax changes) support the new syntax
16:18:46 <sc68cal> I just think it's the 4.24 version where they dropped support for the old syntax and it now errors
16:19:04 <GomathiselviS> We can run the eos integration test suite against 4.24
16:19:42 <sc68cal> I'll check, but I _think_ basically older versions of EOS supported the new syntax really early, so if we update to use the new syntax, it _should_ work even on older versions of EOS, but I will check
16:19:59 <Qalthos> sc68cal: https://docs.ansible.com/ansible/latest/network/dev_guide/developing_resource_modules_network.html#running-network-integration-tests shows how to run our integration tests, feel free to bother someone if you can't figure something out
16:20:13 <sc68cal> ah here we go, from the field note:
16:20:15 <sc68cal> "4.21.4F and later releases up to 4.22.x contains support for the complete set of new syntax command changes, deprecated commands are also supported."
16:20:39 <sc68cal> so do we currently support anything older than 4.21.4F ?
16:21:41 <sc68cal> "Nothing changes, other than the addition of new commands described below, in future releases of the 4.19 train, the 4.20 train, the 4.21 train, or even the 4.22 train coming out in Q2 2019."
16:22:05 <sc68cal> so it sounds like even super old releases in the 4.19 version will have the new commands available
16:22:49 <sc68cal> everything before 4.20 is currently end of life and has no support by Arista - per https://www.arista.com/en/support/product-documentation/eos-life-cycle-policy
16:22:56 <GomathiselviS> Our modules are tested against 4.20.x in the CI. Locally I test the new resource modules against 4.21 and 4.23
16:23:45 <sc68cal> ok, so we should be able to switch to the new command syntax and not require a backwards compatability shim of some sort
16:26:09 <sc68cal> as a customer, I have also discussed this issue with Arista
16:26:32 <sc68cal> my hope is that they contribute fixes
16:27:33 <GomathiselviS> That would be great.
16:28:04 <sc68cal> I have also tried to discuss with them about the.... overlap between the Ansible.AVD collection and Arista.EOS collection
16:28:34 <sc68cal> and that as a consumer I don't like having two collections that do the same thing. I would prefer just having one.
16:29:47 <sc68cal> I understand that their objectives with the Ansible.AVD collection are much more comprehensive compared to Arista.EOS but most of the documentation points to Arista.EOS and that's how people interact with EOS with ansible for the most part
16:30:45 <sc68cal> so, I am hoping to see more collaboration from Arista in the Arista.EOS collection
16:31:05 <sc68cal> okay, that's all i've got, i'll be quiet now
16:31:29 <Qalthos> Thanks for bringing it up
16:31:38 <Qalthos> #topic Open Floor
16:31:56 <Qalthos> Anyone else have anything they want to talk about this week?
16:32:26 <Qalthos> If not, I think we can end the meeting here
16:32:27 <GomathiselviS> sc68cal: Thanks for your input. We will take this up in our team meeting .
16:32:55 <sc68cal> GomathiselviS: no problem. I plan on being in this IRC room going forward
16:33:30 <sc68cal> i'll try running the tests for arista.eos against 4.24.1.F and see what explodes
16:34:36 <Qalthos> sc68cal: Thanks for showing up and letting us know what you want to see
16:35:01 <Qalthos> #endmeeting