16:00:06 #startmeeting Octavia 16:00:06 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:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:06 The meeting name has been set to 'octavia' 16:00:14 o/ 16:00:22 Hi everyone 16:00:42 #topic Announcements 16:01:05 I don't think I have any announcements this week. 16:01:09 Anyone else? 16:01:15 gthiemonge: ah okay, i will read that. Missed it last week because of familiy issues... 16:01:20 johnsom: nop 16:01:37 #topic Brief progress reports / bugs needing review 16:02:06 As you have probably noticed, I have been focused on fixing our gates. 16:02:21 I was also on holiday this week. 16:02:52 same for me, holidays (+ downstream tasks) 16:02:59 Our gates are suffering from changes in setuptools, oslo.context, neutron, etc. 16:03:33 I hope I am getting close to having things functioning again. Sorry it's been slow going but fun issues keep coming up. 16:04:36 Oh and taskflow also broke us this week. 16:05:01 :/ 16:05:06 So, that has been really all I have been able to focus on. 16:06:06 Ok, sounds like that is it. Moving on 16:06:19 #topic Open Discussion 16:06:24 Other topics this week? 16:06:34 nothing from me 16:08:11 Yeah, maybe the anti-affinity topic :-) 16:08:12 scoopex Did you want to discuss your topic more this week or wait until next week? 16:08:19 Yes :-) 16:08:43 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:09:18 This filter can then react to the set value in nova. 16:09:43 A filter can then react to the set value in nova. 16:10:04 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:21 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:11:30 We have to add a possibility to specify a rule name, which then is used as an name for the hostgroup. 16:13:44 So one new setting or two? I'm slightly confused on that. 16:15:09 Exacly one setting, we create the possibility to define a "rule name". (see https://docs.openstack.org/api-ref/compute/#create-server-group) 16:16:39 Yeah, ok, so we are thinking the same thing. I said "filter", but it's actual "rules". 16:17:06 The configure value can then be cosumed by a enabled custom filter (which filters out all unwanted hosts). 16:17:19 I don't think this would be a problem for Octavia. It should be fairly straight forward to implement. 16:18:05 I understand "filter" as the filter implementation in nova. https://docs.openstack.org/nova/latest/admin/scheduling.html#aggregateinstanceextraspecsfilter 16:19:40 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:56 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:20:37 Yeah, so I don't see a problem with this idea. 16:20:53 Testing it may be a bit tricky though 16:21:46 I have no concerns with moving forward with a proposed patch. 16:21:57 gthiemonge Any thoughts on the topic? 16:22:29 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:47 nop, that looks interesting, maybe we could have a spec that describes the changes in the octavia API 16:23:26 The testing complexity is on the nova side. Multi-node gate jobs have been tricky to get right. 16:23:55 It might be a more flexible alternative to: 16:23:58 #link https://review.opendev.org/c/openstack/octavia/+/923939 16:24:41 gthiemonge Do you think we need a spec or is this small enough we iterate on proposed patches? 16:26:13 I'm fine if we iterate on patches 16:28:21 I agree, it's small so changing it should not be a major undertaking 16:29:01 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:30:40 Using a metadata on the image? (that's pretty much the only way it would know it's an amphora I think) 16:32:01 Probably. I might also possible to get the id of the flavor as an cirteria. 16:33:06 Sorry for the many spelling mistakes :-) Too many parallel topics today.... 16:33:25 lol, same here, no worries 16:36:03 scoopex Do you have what you need from us on this? 16:36:24 Yes! Thanks! 16:36:34 Great! 16:36:40 Any other topics today? 16:36:44 nop 16:37:17 Alright, thank you everyone! 16:37:21 #endmeeting