16:00:24 <Qalthos> #startmeeting Ansible Network Working Group
16:00:24 <zodbot> Meeting started Wed Jun  5 16:00:24 2019 UTC.
16:00:24 <zodbot> This meeting is logged and archived in a public location.
16:00:24 <zodbot> The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:24 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:00:49 <Qalthos> #chair ganeshrn ikhan pabelanger privateip trishnag
16:00:49 <zodbot> Current chairs: Qalthos ganeshrn ikhan pabelanger privateip trishnag
16:01:21 <Qalthos> #link https://github.com/ansible/community/labels/network is where you can always find the meeting agenda
16:03:13 <Qalthos> #topic Core Updates
16:03:59 <Qalthos> 2.9 roadmap, for those interested in that sort of thing, should be getting generated soon
16:05:03 <Qalthos> I don't have any particular idea when it will be made available, but most of the post-release rush has died down by now
16:06:13 <Qalthos> On that note, 2.8.1 should be coming soon
16:06:21 <mikewiebe> Qalthos: Is it too late to get fixes cherry-picked into stable-2.8 for 2.8.1?
16:06:42 <Qalthos> mikewiebe: there's still time, but sooner is always better
16:07:18 <mikewiebe> Qalthos: Understood... Everything we need in 2.8.1 is currently either merged or open PR
16:08:20 <Qalthos> And on that note, my regular reminder that the only person who can merge your backport is the release manager, so bringing them up here does not do anything to speed that process up
16:09:23 <Qalthos> Generally, the backports are gone through in batches, and everything that's open will be looked at before a release is made
16:10:10 <Qalthos> Just be responsive if they ask you to make a change, and you should have no problem getting it into the next point release
16:10:33 <mikewiebe> Sure thing
16:11:31 <Qalthos> mrproper: I'm going to skip you, unless you think I missed something
16:13:10 <mrproper> Nope, you've got everything.
16:13:37 <Qalthos> Cool, moving on
16:15:55 <ikhan> mikewiebe: we are recommending any major things that you have planned for 2.9 should be merged early in release cycle, so we can avoid last minute rush.
16:16:47 <Qalthos> #topic NX-OS PRs
16:17:13 <Qalthos> On that note, I've reviewed a majority of the PRs in the agenda
16:17:15 <ikhan> mikewiebe: also since AnsibleFest is in Sept.  A lot of people will be busy with the conference, so leaving things at the last moment is probably not a good idea
16:17:38 <mikewiebe> ikhan: What would you consider early.  Is there a target date?
16:18:12 <mikewiebe> ikhan: We have quite a few PRs for 2.9 open right now
16:19:22 <ikhan> mikewiebe: There are discussions happening around 2.9 schedule.  I am not sure if we have final dates yet, but I am sure they will go out to community soon
16:19:53 <mikewiebe> ikhan: Sounds good.
16:21:24 <Qalthos> I'm going to let trishnag have merge those modules at her discretion, but I did want to ask some questions about the 'bfd' param across different modules
16:22:48 <mikewiebe> Qalthos: What questions?
16:23:43 <Qalthos> First the default value when the type is bool... I noted places where the default was not documented, but then ran across one where the argspec did not specify a default
16:24:01 <Qalthos> Is there meant to be a consistent expectation of this param across modules where it is implemented?
16:24:33 <mikewiebe> Qalthos: Yes, we will add the doc updates
16:24:34 <Qalthos> (ignoring the `type: string` ones for the moment)
16:25:24 <Qalthos> Okay, so for `type: bool`, the default should always be `False`?
16:25:46 <mikewiebe> Qalthos: It depends on how the bfd option is configured for a particular feature (bgp vs. pim) for instance.
16:26:12 <mikewiebe> Qalthos: The default is the platform default.
16:27:00 <mikewiebe> bool could be True if the feature owner defaults that option to True, but generally speaking it's more then likely False
16:30:26 <mikewiebe> Qalthos: I just looked at your comment for nxos_ospf_vrf and I understand what you are asking.  Let me circle back with the Chris on that and we will update the PR
16:32:04 <mikewiebe> Qalthos: In terms of priority, we need ansible/ansible#56317 merged asap.
16:33:07 <Qalthos> mikewiebe: I will make sure trishnag sees that as soon as she is back, then.
16:33:37 <mikewiebe> Qalthos: Thanks!
16:34:15 <mikewiebe> Qalthos: Any other questions about the BFD updates?
16:35:52 <Qalthos> No, as long as you go back and make sure they are being used consistently when appropriate, that's all I wanted to make sure
16:37:13 <mikewiebe> Qalthos: Sounds good
16:37:20 <Qalthos> The other PRs look fine, but again, I'll let trishnag give the final say
16:39:24 <Qalthos> #topic Open Floor
16:40:23 <Qalthos> Anyone else have anything to bring up?
16:40:27 <xuxiaowei0512> I see that there are 3Prs merged
16:41:08 <xuxiaowei0512> how about others
16:42:01 <Qalthos> xuxiaowei0512: As I mentioned at the beginning of this meeting, there is nothing I can do for backports, just be patient and you should get a response
16:42:34 <xuxiaowei0512> I got it
16:42:43 <xuxiaowei0512> vxlan?
16:43:04 <xuxiaowei0512> 57264?
16:43:52 <Qalthos> Specifically for that, I am presently somewhat limited in what I am able to help you with at the moment
16:44:55 <Qalthos> If you would like to know more, feel free to talk to gregdek or jtanner, both of whom are in #ansible-devel
16:45:18 <xuxiaowei0512> ok
16:45:28 <xuxiaowei0512> thank you
16:46:11 <Qalthos> Anyone else?
16:49:37 <Qalthos> Well, then, have a good week everyone.
16:49:40 <Qalthos> #endmeeting