16:00:01 <gthiemonge> #startmeeting Octavia
16:00:01 <opendevmeet> Meeting started Wed Jul 26 16:00:01 2023 UTC and is due to finish in 60 minutes.  The chair is gthiemonge. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:01 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:01 <opendevmeet> The meeting name has been set to 'octavia'
16:00:06 <johnsom> o/
16:00:08 <gthiemonge> right on time!
16:00:09 <gthiemonge> hi
16:00:37 <tweining> o/
16:01:37 <gthiemonge> #topic Announcements
16:01:46 <gthiemonge> * Review policy on backports
16:02:08 <gthiemonge> Since I've been working on Octavia, we have always approved (W+1) backports after 2 CR+2s
16:02:21 <gthiemonge> In the Stable Branches guidelines (https://docs.openstack.org/project-team-guide/stable-branches.html), there's the following paragraph:
16:02:28 <gthiemonge> | Each backported commit proposed to Gerrit should be reviewed and +2ed by two
16:02:31 <gthiemonge> | project-specific stable maintenance team members before it is approved. Where
16:02:34 <gthiemonge> | a team member has backported a fix, a single other +2 is sufficient for
16:02:37 <gthiemonge> | approval.
16:03:04 <gthiemonge> As we are a small team with a small number of core-reviewers (and they are the most active contributors), I suggest that we follow those recommendations (one +2 needed if a member of the core team has backported the fix)
16:03:08 <gthiemonge> what do you think?
16:03:29 <tweining> makes sense. +1
16:03:34 <johnsom> The stable maintenance team never supported Octavia either. It has always been a subset of the core team
16:03:58 <gthiemonge> right
16:04:29 <gthiemonge> if we do it, it means that we will have to be really careful with the content of the backports (API/DB changes, etc...)
16:04:30 <johnsom> Yeah, I think this is ok. We just need to be sure to take the time to review the patches for changes that could cause breakage on stable branches or upgrades.
16:04:43 <gthiemonge> we need to enforce the use of the Backport-Candidate flag in gerrit
16:04:46 <johnsom> Right, internal APIs and RPC as well
16:04:52 <gthiemonge> (at least for non trivial things)
16:05:25 <gthiemonge> yeah the list of forbidden changes is https://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines
16:06:57 <johnsom> BTW, for announcements, the virtual PTG in October is open for registrations and they sent out the email for teams to sign up.
16:07:00 <johnsom> #link https://openinfra.dev/ptg/
16:07:26 <gthiemonge> yeah I will register the octavia project
16:07:35 <johnsom> +2+w
16:07:39 <johnsom> grin
16:08:02 <gthiemonge> ok, so on this backport policy, let's try to do it. But I think the core team should keep an eye on the approved backport, to ensure that we are doing it correctly
16:09:19 <tweining> yeah, I will try to look for api changes etc. before approving backports.
16:09:45 <tweining> but even if mistakes happen that shouldn't be the end of the world. we can always revert patches
16:10:04 <tweining> if we catch it later on
16:10:41 <johnsom> It is really hard to pull releases
16:11:22 <gthiemonge> we need 2 bad core team members to merge a patch
16:11:25 <gthiemonge> :D
16:11:30 <johnsom> lol
16:12:56 <gthiemonge> next big announcement:
16:13:00 <gthiemonge> * PTL on PTO
16:13:06 <gthiemonge> I'm on vacation for the next 2 weeks
16:13:14 <gthiemonge> I'm proposing that we cancel our weekly meetings until I'm back
16:13:20 <tweining> well deserved. enjoy!
16:13:31 <johnsom> Yeah, I hope you do something fun
16:13:51 <johnsom> I think that is fine, it's been pretty quiet this summer meeting wise
16:14:27 <gthiemonge> ok then the next meeting will be on August 16
16:17:04 <gthiemonge> #topic CI Status
16:17:15 <gthiemonge> FYI We fixed a few issues on stable branches, the lower-constraints jobs were still enabled on wallaby xena yoga
16:17:39 <gthiemonge> We updated octavia and octavia-dashboard, I will check if python-octaviaclient is impacted too
16:18:08 <gthiemonge> #topic Brief progress reports / bugs needing review
16:19:08 <gthiemonge> I've been working on a neutron bug that impacts the failover of IPv6 loadbalancers
16:19:11 <tweining> a heads up about my hsts patches: today the openstacksdk patch got its first +2.
16:19:14 <tweining> https://review.opendev.org/c/openstack/openstacksdk/+/881553
16:19:16 <johnsom> I have done a bunch of reviews and I'm poking at the SRIOV feature. I hope I can start a spec soon
16:19:57 <tweining> once the patch is merged we must deliver the feature in octavia too ;)
16:19:59 <johnsom> I will review and merge that today if I don't see anythng
16:20:51 <gthiemonge> about this ipv6 issue, I opened a launchpad
16:20:58 <gthiemonge> https://bugs.launchpad.net/octavia/+bug/2028524
16:21:03 <gthiemonge> and for neutron
16:21:07 <gthiemonge> https://bugs.launchpad.net/neutron/+bug/2028651
16:21:27 <johnsom> Hmm, guess I can't merge it
16:21:51 <gthiemonge> I'm trying to write a reproducer with openstacksdk
16:21:54 <gthiemonge> I'm using the same API calls (to neutron and nova) but that doesn't work
16:22:55 <gthiemonge> I'll keep you updated before my vacation
16:25:28 <tweining> yeah, that looks to be a tricky bug
16:26:19 <gthiemonge> #topic Open Discussion
16:27:21 <gthiemonge> anything else guys?
16:27:32 <johnsom> I don't have anything
16:27:59 <tweining> I've got nothing I think. I am testing octavia with DPDK, but it's more a deployment config type of thing
16:28:05 <tweining> (at least for now)
16:29:00 <gthiemonge> cool
16:29:05 <gthiemonge> ok folks
16:29:08 <gthiemonge> thank you!
16:29:15 <gthiemonge> #endmeeting