ansible_network_working_group
LOGS
16:00:21 <Qalthos> #startmeeting Ansible Network Working Group
16:00:21 <zodbot> Meeting started Wed Apr 17 16:00:21 2019 UTC.
16:00:21 <zodbot> This meeting is logged and archived in a public location.
16:00:21 <zodbot> The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:21 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:21 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:00:43 <Qalthos> #chair ganeshrn privateip trishnag pabelanger
16:00:43 <zodbot> Current chairs: Qalthos ganeshrn pabelanger privateip trishnag
16:00:52 <Qalthos> #topic Core Updates
16:01:47 <Qalthos> #info 2.8 is well on its way now, 2.8.0b1 was released on Monday
16:02:51 <Qalthos> Go check it out and report bugs if you find any
16:03:54 <Qalthos> Not a whole lot else to talk about yet, fixing bugs and preparing for 2.9
16:04:26 <Qalthos> #link https://github.com/ansible/community/labels/network is where the agenda for this meeting can always be found
16:04:44 <Qalthos> So let's get in to it
16:05:24 <Qalthos> #topic "ncclient is not installed"
16:05:49 <Qalthos> The issue was raised with respect to NX-OS, but others may run into it
16:06:19 <Qalthos> #link https://github.com/ansible/ansible/pull/55384 should fix the issue
16:06:47 <Qalthos> Will be merging and backporting to 2.8 and 2.7 shortly.
16:08:00 <Qalthos> #topic Avi Modules mass update
16:09:28 <Qalthos> chaitanyaavi: Anything new to add about this, or just a reminder?
16:10:03 <chaitanyaavi> Just a reminder as 2.8 is released can you please review it?
16:11:09 <Qalthos> Someone should get to it soon, though we are still prioritizing bugfixes for 2.8 ahead of its release
16:12:02 <chaitanyaavi> Sure no hurry this is not a blocker.
16:14:27 <Qalthos> chaitanyaavi: Understood
16:15:07 <Qalthos> #topic New module exos_vlan
16:17:26 <Qalthos> ujwalkomarla: I'm looking through the diff you attached now
16:18:42 <Qalthos> You're still using `ansible_network_os: exos` and not `ansible_network_os: restconf` here, yes?
16:18:47 <ujwalkomarla> Yes.
16:19:00 * Qalthos takes another reminder to fix that variable name
16:21:52 <ujwalkomarla> The diff was just a quick hack.. to see what we could do with restconf's module_utils..
16:22:11 <ujwalkomarla> Not processing the 'accept' and 'content_type' yet...
16:24:16 <Qalthos> I don't especially care if you use the module_utils or not, particularly if it doesn't net you any benefit over what you are doing. What I would rather see is using the restconf httpapi plugin instead of your own
16:25:29 <Qalthos> That said, you've mentioned that exos doesn't support the entire RESTCONF RFC, nor does it support it for all configuration, so there are some issues with that option
16:27:24 <Qalthos> If `network_os: restconf` won't work even for your most straightforward module here, then we can probably move forward with the hybrid approach you've outlined previously
16:27:46 <ujwalkomarla> Yes. I agree. Utilizing restconf httpapi plugin alone isn't an option.
16:30:01 <Qalthos> Alright then, I'll take another pass over your module, and see if it can get merged soon.
16:30:35 <ujwalkomarla> Awesome. Thanks! :)
16:31:47 <Qalthos> #topic Open Floor
16:32:00 <Qalthos> Anyone else have anything they want to discuss here?
16:34:00 <ujwalkomarla> Is there a way to use one ansible module from another? Say, exos_lldp is completely supported by RESTCONF RFC. Is there a way to call restconf_get and restconf_config from exos_lldp?
16:35:28 <ujwalkomarla> Essentially, build an exos_* module over restconf_* modules..
16:37:04 <Qalthos> ujwalkomarla: I'm not entirely sure why you would want to, vs just calling the functions in module_utils.network.restconf.restconf... that is what they are there for
16:39:12 <Qalthos> If you want something that operates on manipulating the existing modules, it sounds like what you want is a role, not a module
16:40:18 <ujwalkomarla> Ah... I see.
16:40:22 <ujwalkomarla> Let me look into that.
16:46:08 <Qalthos> Unless anyone else has anything quick, I'll close this meeting
16:46:51 <Qalthos> Thanks everyone for coming
16:47:04 <Qalthos> #endmeeting