16:00:08 <Qalthos> #startmeeting Ansible Network Working Group
16:00:09 <zodbot> Meeting started Wed May  3 16:00:08 2023 UTC.
16:00:09 <zodbot> This meeting is logged and archived in a public location.
16:00:09 <zodbot> The chair is Qalthos. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:09 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:00:16 <Qalthos> #topic Agenda https://github.com/ansible/community/issues/542
16:00:33 <Qalthos> #link https://github.com/ansible/community/labels/network is where you can always find the latest agenda
16:00:36 <Qalthos> #topic Core Updates
16:01:44 <Qalthos> #info After the discussion last week, this meeting will be moving to every other week on Thursdays at 1300 UTC
16:02:40 <Qalthos> #info This will start with the next meeting
16:03:02 <Qalthos> #link https://github.com/ansible/community/pull/694 is the PR making the change to the calendar
16:03:10 <Qalthos> (and some other assorted cleanup)
16:03:43 <Qalthos> We might tweak this further down the line, but that's the plan for now
16:14:46 <Qalthos> #topic Open Floor
16:14:55 <Qalthos> Anyone else want to talk about anything?
16:26:09 <jahknem[m]> I've got a question about show commands on network devices. Would I implement these as lookups in a collection? Say the currently used bandwidth on a port or the Mac table on a switch
16:29:37 <Qalthos> I guess you could do it that way, but I'm not aware of anyone doing that currently
16:34:19 <jahknem[m]> What would be the best practice way of doing it?
16:34:32 <jahknem[m]> Or is that usually not done?
16:38:17 <Qalthos> I'm not sure there is an established procedure for providing something like that by the collection, when there's usually a general-purpose module like cli_command available to get whatever specific detail you want without the collection author having thought about it
16:40:15 <Landrash[m]> Nothing to addd Qalthos (open floor)
16:45:08 <jahknem[m]> Sure, but cli_command forces users to write a template/parser
16:46:54 <jahknem[m]> If there is no established procedure I'll just go ahead and do it the way I think makes the most sense :)
16:54:35 <Qalthos> #endmeeting