ansible_network_working_group
LOGS
16:00:12 <pabelanger> #startmeeting Ansible Network Working Group
16:00:12 <zodbot> Meeting started Wed Dec 18 16:00:12 2019 UTC.
16:00:12 <zodbot> This meeting is logged and archived in a public location.
16:00:12 <zodbot> The chair is pabelanger. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:12 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:00:34 <pabelanger> #chair Qalthos
16:00:34 <zodbot> Current chairs: Qalthos pabelanger
16:00:47 <pabelanger> #topic Core Updates
16:01:21 <pabelanger> we are well into the 2.10 development cycle, major changes this time around is collection content
16:01:38 <pabelanger> So, if you are keeping up with commits into ansible/ansible, you'll likely see a lot of stuff related to that
16:02:02 <pabelanger> the big thing, is content is moving out of ansible/ansible into its own collection repo
16:02:20 <pabelanger> the date of the move is still a while out, but we are actively testing new collections via a migration script
16:02:39 <pabelanger> #link https://github.com/ansible-community/collection_migration/
16:03:19 <pabelanger> also, as a reminder, holiday shutdown in the US is next week, so we don't expect to have a meeting until Jan 2020
16:03:48 <pabelanger> #link https://github.com/ansible/community/labels/network is where you can find the agenda as always
16:04:12 <pabelanger> #topic deprecation of local connection
16:04:27 <pabelanger> going out of order today
16:05:05 <pabelanger> with the move to collections, one of the things we've finally started to discuss is the deprecation of local connection for network modules
16:05:15 <pabelanger> this is partly due to how internals of collections work
16:05:27 <pabelanger> and because we have a good number of modules now using network_cli
16:05:41 <pabelanger> #link https://github.com/ansible/ansible/pull/65876
16:06:07 <pabelanger> That means, in ansible 2.14 we plan on removing it
16:06:19 <pabelanger> so, you have a bit of time but is something that will change
16:06:43 <pabelanger> moving on
16:06:59 <pabelanger> #topic meraki PRs
16:07:08 <pabelanger> #link https://github.com/ansible/ansible/pull/59395
16:07:13 <pabelanger> mrproper: this one is from you
16:08:39 <pabelanger> PR looks to be good
16:08:56 <pabelanger> unless Qalthos sees and issue, we likely can merge
16:09:14 <Qalthos> +1
16:09:25 <pabelanger> lets keep moving on
16:09:31 <pabelanger> #topic onyx PRs
16:09:39 <pabelanger> #link https://github.com/ansible/ansible/pull/64359
16:09:45 <pabelanger> #link https://github.com/ansible/ansible/pull/64434
16:09:53 <pabelanger> #link https://github.com/ansible/ansible/pull/64509
16:10:00 <pabelanger> #link https://github.com/ansible/ansible/pull/63983
16:10:16 <pabelanger> I am not sure if OP is here
16:11:19 <pabelanger> the good news, it there does seems to be unit tests
16:11:22 <pabelanger> so, that is helpful
16:11:40 <pabelanger> so, i think it is just a matter of reviewing these and seeing if any issues found
16:13:49 <pabelanger> I'll send some time on reviews there
16:13:55 <pabelanger> #topic Open discussion
16:14:08 <pabelanger> If you have anything else you'd like to bring up, now is the time
16:14:18 <pabelanger> I imagine a lot of folks are preparing for holidays
16:16:49 <Qalthos> #info This is the last IRC meeting of the yeay
16:16:59 <Qalthos> By which I mean year
16:17:02 <pabelanger> ++
16:17:24 <Qalthos> #info Next meeting is on 2020-01-08
16:21:58 <pabelanger> and that is a wrap on the year!
16:22:12 <pabelanger> Thanks again to everything who helped make ansible better this year
16:22:18 <pabelanger> #endmeeting