16:14:08 <pabelanger> #startmeeting Ansible Network Working Group
16:14:08 <zodbot> Meeting started Wed May  8 16:14:08 2019 UTC.
16:14:08 <zodbot> This meeting is logged and archived in a public location.
16:14:08 <zodbot> The chair is pabelanger. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:14:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:14:08 <zodbot> The meeting name has been set to 'ansible_network_working_group'
16:14:38 <pabelanger> #chair ganeshrn Qalthos trishnag
16:14:38 <zodbot> Current chairs: Qalthos ganeshrn pabelanger trishnag
16:14:46 <pabelanger> #topic Core Updates
16:15:08 <pabelanger> Sorry for late start today, we are head down working on ansible 2.8 release
16:15:46 <pabelanger> we noticed last week a issue with our testing platform (DCI), once we figured it out, we noticed some testing on devel / stable-2.8 was failing.
16:16:09 <pabelanger> We don't see any major issue, but working our way throught the tests to enable them again
16:16:28 <pabelanger> we've also start the migration away from DCI for network integration testing
16:17:21 <pabelanger> this will now be handeled by zuul.ansible.com moving forward. Today we have 2 appliances running, vyos / eos, they are also running integration testing against ansible/ansible
16:17:47 <pabelanger> I expect another few weeks until we get the rest of the images migrated, but we are well on our way
16:18:32 <pabelanger> We are about 2 weeks out from ansible 2.8 GA, last I heard things are looking good
16:18:58 <pabelanger> Also redhat summit is this week, I know a bit of the ansible network folks are attending too
16:19:09 <pabelanger> #link https://github.com/ansible/community/labels/network is where the agenda for this meeting can always be found
16:19:16 <pabelanger> so, lets get started
16:20:04 <pabelanger> #topic Update cnos_vrf.py to to fix coverity bug
16:20:12 <pabelanger> #link https://github.com/ansible/ansible/pull/56014
16:20:33 <pabelanger> so, right now stable-2.8 is frozen until the GA of ansible-2.8
16:20:52 <pabelanger> so, I don't believe we'll see this bug fix before 2.8.1
16:21:14 <pabelanger> I also know this week, we haven't had a chance to do bug triage, due to redhat summit as I mentioned
16:21:38 <Anil_Lenovo> ok. Got it. So I may have to revert on this PR post GA ?
16:22:25 <Anil_Lenovo> Or should I raise a fresh backporting PR later ?
16:23:21 <pabelanger> Anil_Lenovo: yah, right now we have to raise an backport exception with release mgmt for ansible core. And give then last RC is scheduled for tomorrow, I don't think there is enough time to go though all the checks
16:23:34 <pabelanger> Once we cut the 2.8.0 release, stable-2.8 will open for backports
16:23:43 <pabelanger> which _should_ be next week I believe
16:23:53 <pabelanger> so I suspect we'll be okay to land it then
16:24:03 <Anil_Lenovo> ok. Great. No issues..
16:24:19 <pabelanger> thanks
16:24:36 <pabelanger> #topic Open discussion
16:24:51 <pabelanger> there was nothing else on the agenda today
16:24:57 <pabelanger> if anybody else has something to raise
16:25:07 <chaitanyaavi> Just a reminder for https://github.com/ansible/ansible/pull/54894
16:26:11 <chaitanyaavi> I understand the team is busy in 2.8.0 release but can we get any ETA as our next enhancements are depending on this one.
16:27:13 <pabelanger> chaitanyaavi: Next week we should be back into bug triage with team, so I imagine we'll discuss this then and add somebody to review
16:27:29 <pabelanger> But right now, I cannot remember if we have discussed this already or not
16:27:36 <bcoca> also ... pycon + rh summit
16:27:39 <pabelanger> given there is no comments from team, I would say no
16:28:08 <pabelanger> #action pabelanger raise https://github.com/ansible/ansible/pull/54894 at bug triage meeting
16:28:26 <chaitanyaavi> ok thanks
16:28:41 <pabelanger> thanks for bring it up
16:34:39 <pabelanger> okay, thanks all. Again, sorry for the delay in starting this week
16:34:41 <pabelanger> #endmeeting