| opendevreview | Tom Weininger proposed openstack/octavia master: Add support for HTTP Strict Transport Security https://review.opendev.org/c/openstack/octavia/+/880806 | 06:11 |
|---|---|---|
| gthiemonge | #startmeeting Octavia | 16:00 |
| opendevmeet | Meeting started Wed May 31 16:00:24 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 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'octavia' | 16:00 |
| johnsom | o/ | 16:00 |
| matfechner | o/ | 16:00 |
| gthiemonge | hello | 16:00 |
| oschwart | o/ | 16:00 |
| gthiemonge | #topic Announcements | 16:01 |
| gthiemonge | no announcement this week | 16:01 |
| gthiemonge | does someone have one? | 16:01 |
| johnsom | I will be hosting a forum session for Octavia at the Vancouver Summit | 16:02 |
| johnsom | It is on Wednesday morning at 9AM. | 16:02 |
| johnsom | Is anyone planning to attend the summit? | 16:02 |
| gthiemonge | \o/ | 16:02 |
| johnsom | Ok, it might be a quiet forum session. lol | 16:03 |
| johnsom | If anyone is attending I will be there in person and happy to meet with people. | 16:04 |
| gthiemonge | thanks johnsom! | 16:04 |
| gthiemonge | #topic CI Status | 16:05 |
| gthiemonge | good news | 16:06 |
| gthiemonge | the CI is in a better shape this week | 16:06 |
| gthiemonge | _this week_ | 16:06 |
| gthiemonge | We should not see any timeouts on 2023.1 and master | 16:06 |
| gthiemonge | don't hesitate to ping me in case of issues | 16:06 |
| gthiemonge | The FIPS issue in devstack was fixed but our jobs are still failing (timeout when connecting to the Cirros VM) | 16:07 |
| gthiemonge | https://zuul.openstack.org/builds?job_name=octavia-v2-dsvm-tls-barbican-fips&skip=0 | 16:07 |
| gthiemonge | I will open a new launchpad issue for this new error | 16:07 |
| johnsom | Thanks, maybe I can take a look and see if something jumps out at me. It's a busy day | 16:08 |
| johnsom | ping me if you don't see a comment | 16:09 |
| gthiemonge | it's not urgent (it's not blocking us) | 16:09 |
| gthiemonge | #topic Brief progress reports / bugs needing review | 16:10 |
| gthiemonge | just a kind reminder that we have a lot of open patches on stable branches: | 16:10 |
| gthiemonge | #link https://review.opendev.org/q/project:openstack/octavia+status:open+branch:%255Estable/.* | 16:10 |
| gthiemonge | (a reminder to me as well ;-) | 16:10 |
| gthiemonge | #topic Open Discussion | 16:16 |
| johnsom | I have done some reviews, also making some progress in understanding the SRIOV process | 16:16 |
| gthiemonge | I have one topic: | 16:16 |
| gthiemonge | I'm working on the implementation of the Active-Active L3 Distributor spec | 16:16 |
| gthiemonge | #link https://docs.openstack.org/octavia/latest/contributor/specs/version1.1/active-active-l3-distributor.html | 16:16 |
| gthiemonge | so first, I'm not planning to use their DB schema, I will change some details | 16:17 |
| johnsom | Boy I have not read that in a while. This was the Walmart plan right? | 16:17 |
| gthiemonge | Question #1: do you think it requires an update of this spec? | 16:17 |
| gthiemonge | hmmm, I don't remember, it's the BGP spec | 16:17 |
| johnsom | Yeah, it was. | 16:18 |
| gthiemonge | or should I create an new updated spec? | 16:18 |
| johnsom | Umm, you could always copy it into a new version directory and make the required changes. Marking the old one and new as such | 16:18 |
| gthiemonge | ack | 16:19 |
| gthiemonge | I tihnk I will have more updates yeah | 16:19 |
| johnsom | The old one had some patches, but didn't make it far. | 16:19 |
| johnsom | I think a fresh review on a spec would be good too. | 16:19 |
| gthiemonge | +1 | 16:19 |
| gthiemonge | this spec doesn't detail the new proposed API (only internals and DB changes) | 16:20 |
| johnsom | I am excited that we have some good stuff moving forward, BGP, SRIOV, DPDK. | 16:20 |
| johnsom | Yeah, that is not good | 16:20 |
| gthiemonge | IMO we need to provide API calls for managing 2 new resources for BGP | 16:21 |
| gthiemonge | - BGP peers (an external BGP daemon) | 16:21 |
| gthiemonge | - BGP speakers (which is in the amphora in this implementation) | 16:21 |
| gthiemonge | Question #2 | 16:21 |
| gthiemonge | do you think we can manipulate BGP objects with the Octavia API (a new endpoint like /lbaas/distributor/bgp/peer) | 16:22 |
| gthiemonge | or do we need to have more "Generic" objects | 16:22 |
| johnsom | Maybe a pass phrase field too? | 16:22 |
| gthiemonge | ex: a new endpoint /lbaas/distributor which gets a {"type": "bgp-{peer,speaker}"} parameters | 16:22 |
| gthiemonge | a passphrase field? | 16:22 |
| johnsom | Don't you need to provide a pass phrase to some peers? | 16:23 |
| gthiemonge | yeah there's an "auth_pass" parameter | 16:23 |
| johnsom | Back to the API question #2, in REST you typically are talking about objects, so I would expect something more like /lbaas/distributor/<distributor ID>/bgp/peer/<peer ID> if you go down that path. | 16:25 |
| gthiemonge | yeah, to me, it looks like a good way to do that | 16:26 |
| johnsom | In those documents "distributor" is a concept and does not always have to be implemented as an actual process. One proposal had an implementation, the other did not need one. | 16:26 |
| gthiemonge | in my mind the distributor will be an object that links the LB (and the amps), speakers in the amps and a remote peer | 16:27 |
| johnsom | Cool, so yeah, a proposal for that approach would be cool | 16:27 |
| johnsom | Yep | 16:28 |
| gthiemonge | cool, I will propose a new spec! | 16:28 |
| gthiemonge | BTW I'm not targeting Bobcat | 16:28 |
| johnsom | Maybe just keep in mind, there might be some reason to have an LVS distributor or an OVN distributor. | 16:28 |
| johnsom | That should help guide the API to be flexible for future implementations using "shiny new ball technology" | 16:29 |
| gthiemonge | I thought the LVS distributor spec was an old spec that was propsoed before the BGP spec | 16:30 |
| gthiemonge | ah ok | 16:30 |
| gthiemonge | I see | 16:30 |
| johnsom | It was, the LVS approach was intended to be a gate testable approach as BGP peers in the testing environment was not a thing | 16:31 |
| johnsom | But yeah, the odds of someone implementing that are fairly low now. | 16:31 |
| johnsom | I would just use it as an idea to guide the API design to be flexible | 16:32 |
| gthiemonge | ack | 16:33 |
| gthiemonge | johnsom: thanks for your feedback! | 16:33 |
| johnsom | Sure, NP | 16:34 |
| gthiemonge | any other topics folks? | 16:35 |
| johnsom | I don't have anything else | 16:35 |
| gthiemonge | ok! | 16:36 |
| gthiemonge | thank you guys! | 16:36 |
| gthiemonge | #endmeeting | 16:36 |
| opendevmeet | Meeting ended Wed May 31 16:36:35 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:36 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/octavia/2023/octavia.2023-05-31-16.00.html | 16:36 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/octavia/2023/octavia.2023-05-31-16.00.txt | 16:36 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/octavia/2023/octavia.2023-05-31-16.00.log.html | 16:36 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!