| opendevreview | Michael Johnson proposed openstack/octavia master: Fix grenade job wsgi module tranition https://review.opendev.org/c/openstack/octavia/+/951043 | 15:51 |
|---|---|---|
| scoopex | I am new to this group. I have an idea for a relatively slim and flexible anti-affinity for the Amporae described here. I am interested in whether this is a sensible or practicable approach to achieve the described: https://input.scs.community/JgMcHJ8oQTKk0cC9UzgUjw# | 15:57 |
| opendevreview | Michael Johnson proposed openstack/octavia master: Fix grenade job wsgi module tranition https://review.opendev.org/c/openstack/octavia/+/951043 | 15:58 |
| scoopex | Is the octavia meeting happening only here or do you use a conferencing room? | 15:58 |
| johnsom | Only here | 15:59 |
| gthiemonge | scoopex: the meeting is here, we discussed the topic last week: https://meetings.opendev.org/meetings/octavia/2025/octavia.2025-05-21-16.01.log.html#l-60 | 16:00 |
| johnsom | #startmeeting Octavia | 16:00 |
| opendevmeet | Meeting started Wed May 28 16:00:06 2025 UTC and is due to finish in 60 minutes. The chair is johnsom. 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 |
| gthiemonge | o/ | 16:00 |
| johnsom | Hi everyone | 16:00 |
| johnsom | #topic Announcements | 16:00 |
| johnsom | I don't think I have any announcements this week. | 16:01 |
| johnsom | Anyone else? | 16:01 |
| scoopex | gthiemonge: ah okay, i will read that. Missed it last week because of familiy issues... | 16:01 |
| gthiemonge | johnsom: nop | 16:01 |
| johnsom | #topic Brief progress reports / bugs needing review | 16:01 |
| johnsom | As you have probably noticed, I have been focused on fixing our gates. | 16:02 |
| johnsom | I was also on holiday this week. | 16:02 |
| gthiemonge | same for me, holidays (+ downstream tasks) | 16:02 |
| johnsom | Our gates are suffering from changes in setuptools, oslo.context, neutron, etc. | 16:02 |
| johnsom | I hope I am getting close to having things functioning again. Sorry it's been slow going but fun issues keep coming up. | 16:03 |
| johnsom | Oh and taskflow also broke us this week. | 16:04 |
| gthiemonge | :/ | 16:05 |
| johnsom | So, that has been really all I have been able to focus on. | 16:05 |
| johnsom | Ok, sounds like that is it. Moving on | 16:06 |
| johnsom | #topic Open Discussion | 16:06 |
| johnsom | Other topics this week? | 16:06 |
| gthiemonge | nothing from me | 16:06 |
| scoopex | Yeah, maybe the anti-affinity topic :-) | 16:08 |
| johnsom | scoopex Did you want to discuss your topic more this week or wait until next week? | 16:08 |
| scoopex | Yes :-) | 16:08 |
| scoopex | https://input.scs.community/JgMcHJ8oQTKk0cC9UzgUjw# - My suggestion is based on the fact that we can simply pass a rule (possibly with a configuration value) into the created ServerGroup in Octavia. More should not be necessary in the Octavia code. | 16:08 |
| scoopex | This filter can then react to the set value in nova. | 16:09 |
| scoopex | A filter can then react to the set value in nova. | 16:09 |
| scoopex | This can be a custom filter or a new Nova default filter that can be activated and used in Nova for antiaffinity, e.g. at AZ level or HostAggregate level. | 16:10 |
| johnsom | So essentially we would add one new configuration setting in Octavia (default config and flavor likely) that would specify the anti-affinity filter to use in nova? Do I have this right? | 16:10 |
| scoopex | We have to add a possibility to specify a rule name, which then is used as an name for the hostgroup. | 16:11 |
| johnsom | So one new setting or two? I'm slightly confused on that. | 16:13 |
| scoopex | Exacly one setting, we create the possibility to define a "rule name". (see https://docs.openstack.org/api-ref/compute/#create-server-group) | 16:15 |
| johnsom | Yeah, ok, so we are thinking the same thing. I said "filter", but it's actual "rules". | 16:16 |
| scoopex | The configure value can then be cosumed by a enabled custom filter (which filters out all unwanted hosts). | 16:17 |
| johnsom | I don't think this would be a problem for Octavia. It should be fairly straight forward to implement. | 16:17 |
| scoopex | I understand "filter" as the filter implementation in nova. https://docs.openstack.org/nova/latest/admin/scheduling.html#aggregateinstanceextraspecsfilter | 16:18 |
| johnsom | Yeah, the rule would have to be implemented on the nova side somehow, to create the anti-affinity style you want (host, rack, room, az, etc.) | 16:19 |
| scoopex | johnsom: the codechange in the octavia codebase should be small. I also liked the idea that scheduling things are handled in the nova scheduling context. | 16:19 |
| johnsom | Yeah, so I don't see a problem with this idea. | 16:20 |
| johnsom | Testing it may be a bit tricky though | 16:20 |
| johnsom | I have no concerns with moving forward with a proposed patch. | 16:21 |
| johnsom | gthiemonge Any thoughts on the topic? | 16:21 |
| scoopex | Why is testing complex from for octavia? From the perspective of octavia it is only neccessary to test that a rule can be set. | 16:22 |
| gthiemonge | nop, that looks interesting, maybe we could have a spec that describes the changes in the octavia API | 16:22 |
| johnsom | The testing complexity is on the nova side. Multi-node gate jobs have been tricky to get right. | 16:23 |
| johnsom | It might be a more flexible alternative to: | 16:23 |
| johnsom | #link https://review.opendev.org/c/openstack/octavia/+/923939 | 16:23 |
| johnsom | gthiemonge Do you think we need a spec or is this small enough we iterate on proposed patches? | 16:24 |
| gthiemonge | I'm fine if we iterate on patches | 16:26 |
| johnsom | I agree, it's small so changing it should not be a major undertaking | 16:28 |
| scoopex | As described, nova also provides the pssibility to write and activate your own filters. So one idea might be to implement temporary filter which only acts when a server was created from the ampora flavor. With that the idea might be testable without changes to the nova and octavia codebase. | 16:29 |
| johnsom | Using a metadata on the image? (that's pretty much the only way it would know it's an amphora I think) | 16:30 |
| scoopex | Probably. I might also possible to get the id of the flavor as an cirteria. | 16:32 |
| scoopex | Sorry for the many spelling mistakes :-) Too many parallel topics today.... | 16:33 |
| johnsom | lol, same here, no worries | 16:33 |
| johnsom | scoopex Do you have what you need from us on this? | 16:36 |
| scoopex | Yes! Thanks! | 16:36 |
| johnsom | Great! | 16:36 |
| johnsom | Any other topics today? | 16:36 |
| gthiemonge | nop | 16:36 |
| johnsom | Alright, thank you everyone! | 16:37 |
| johnsom | #endmeeting | 16:37 |
| opendevmeet | Meeting ended Wed May 28 16:37:21 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:37 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/octavia/2025/octavia.2025-05-28-16.00.html | 16:37 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/octavia/2025/octavia.2025-05-28-16.00.txt | 16:37 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/octavia/2025/octavia.2025-05-28-16.00.log.html | 16:37 |
| gthiemonge | thanks! | 16:37 |
| opendevreview | Michael Johnson proposed openstack/python-octaviaclient stable/2025.1: osc: Use FormattableColumn for formatter https://review.opendev.org/c/openstack/python-octaviaclient/+/951179 | 16:48 |
| opendevreview | Michael Johnson proposed openstack/python-octaviaclient stable/2024.2: osc: Use FormattableColumn for formatter https://review.opendev.org/c/openstack/python-octaviaclient/+/951180 | 16:49 |
| opendevreview | Michael Johnson proposed openstack/python-octaviaclient stable/2024.1: osc: Use FormattableColumn for formatter https://review.opendev.org/c/openstack/python-octaviaclient/+/951181 | 16:57 |
| opendevreview | Merged openstack/python-octaviaclient stable/2025.1: osc: Use FormattableColumn for formatter https://review.opendev.org/c/openstack/python-octaviaclient/+/951179 | 20:31 |
| opendevreview | Merged openstack/python-octaviaclient stable/2024.2: osc: Use FormattableColumn for formatter https://review.opendev.org/c/openstack/python-octaviaclient/+/951180 | 20:48 |
| opendevreview | Merged openstack/python-octaviaclient stable/2024.1: osc: Use FormattableColumn for formatter https://review.opendev.org/c/openstack/python-octaviaclient/+/951181 | 21:13 |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org is temporarily unreachable due to an ongoing issue in the hosting provider where it resides | 22:07 | |
| *** Aslan is now known as aslan | 23:53 | |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!