| laerling | Good morning. Is there no meeting today? | 16:36 |
|---|---|---|
| johnsom | laerling Hi, we had our PTG session this morning, so no IRC meeting today | 16:41 |
| laerling | Sorry, PTG? Not sure right now what that means, sorry :) | 16:47 |
| johnsom | laerling The Project Teams Gathering (PTG) is a once every six months video conference for the OpenStack project teams. https://openinfra.org/ptg/ | 16:50 |
| johnsom | Octavia had a two hour block this morning to discuss topics | 16:50 |
| johnsom | This page is also helpful for seeing the schedule and etherpads: https://ptg.opendev.org/ | 16:51 |
| laerling | Oh got it, thanks! | 16:51 |
| johnsom | laerling Is there a topic you want to chat about or did you just want to observe the weekly meeting? | 16:52 |
| laerling | I was asking since last week's meeting had already been cancelled, but I'm waiting for the opportunity to ask about an RFE of mine that I created ~one month ago, which hasn't received any interaction yet :) | 16:53 |
| laerling | This one, to be precise. https://bugs.launchpad.net/octavia/+bug/2125786 | 16:53 |
| opendevreview | Takashi Kajinami proposed openstack/octavia master: devstack: Remove remaining logic for linuxbridge-agent https://review.opendev.org/c/openstack/octavia/+/965258 | 16:53 |
| laerling | We at SAP need it upstream and are happy to implement it. And I think it is a technically reasonable request. I just would like to have an indication how you maintainers feel about it. | 16:54 |
| johnsom | laerling Thank you for this RFE. We did not discuss this at the PTG unfortunately. | 16:55 |
| johnsom | It seems similar to the batch members update API idea. https://docs.openstack.org/api-ref/load-balancer/v2/index.html#batch-update-members | 16:56 |
| laerling | That's okay, I don't want to come across like I'm trying to put pressure on you :) | 16:57 |
| laerling | It is semantically similar to batch member update, but technically more similar to the fully-populated LB creation. | 16:57 |
| johnsom | Oh no, we all have many responsibilities, so it is good to raise awareness. We do not mind | 16:57 |
| gthiemon1e | (this feature would solve a lot of potential issues with octavia-dashboard ;-) ) | 16:57 |
| johnsom | laerling I would recommend moving forward with a specification file that describes the API changes in detail. | 17:00 |
| johnsom | Similar to these: https://docs.openstack.org/octavia/latest/contributor/index.html#design-documentation | 17:00 |
| johnsom | https://github.com/openstack/octavia/tree/master/specs | 17:00 |
| johnsom | There is a template in that directory | 17:00 |
| laerling | Ah, okay. So I would write such a spec file and submit a change with a PR? And when that gets approved we can start with the implementation? | 17:03 |
| johnsom | Correct, for RFEs that make API changes, that is the normal process. | 17:03 |
| laerling | Thanks for the explanation. Then I will do that and come back to you with a change :) | 17:04 |
| johnsom | Sounds great! | 17:04 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!