Tuesday, 2024-10-15

opendevreviewRodolfo Alonso proposed openstack/neutron master: AddressGroup API collection should be the resource name in plural  https://review.opendev.org/c/openstack/neutron/+/93238007:09
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Support address group for ovn driver  https://review.opendev.org/c/openstack/neutron/+/85150907:14
gsamfiracardoe: We're setting up an OpenStack cloud with a few hundred Ironic nodes, right now. We went with using networking-generic-switch (https://github.com/openstack/networking-generic-switch) to manage attaching the baremetal nodes to VLAN networks. 10:48
gsamfirawe set up a few physical networks with a few VLAN pools made available on them10:48
gsamfiratenants can create internal VLAN tenant networks which can then be used to boot their ironic nodes10:49
gsamfirayou can use availability zones if you have multiple physical networks10:50
gsamfiraif you need to target one particular physical network, neutron will use the AZ hints to create the ports10:51
gsamfiraalternatively (but this increases the failure domain), you can use BGP EVPN to transport the VLANs across multiple leaf pairs in a leaf-spine topology10:51
gsamfiradefining VLAN ranges on a physical network, will allow tenants to create a VLAN network without caring about the underlying physnet. They can just: openstack network create --provider-network-type vlan test-net10:54
gsamfiraopenstack will create an internal network and pick one free VLAN id from the pool10:54
opendevreviewMerged openstack/neutron master: Replace ``greenthread.sleep`` with ``time.sleep``  https://review.opendev.org/c/openstack/neutron/+/93125111:12
opendevreviewLiushy proposed openstack/neutron master: Only consider one IPv4 subnet when creating a FIP  https://review.opendev.org/c/openstack/neutron/+/93240512:18
opendevreviewLiushy proposed openstack/neutron master: Only consider one IPv4 subnet when creating a FIP  https://review.opendev.org/c/openstack/neutron/+/93240512:20
cardoegsamfira: So similar but each physical network currently its own region. So was just wondering how I could have multiple physicals on one neutron. So I guess I'm at a loss how that openstack network create takes the AZ hints to land in the right place. Or are you just saying VLAN 1000 is used by that tenant's network on ALL physical networks?13:21
opendevreviewLajos Katona proposed openstack/neutron-vpnaas stable/2023.2: Stable Only: change tempest to use correct job definition  https://review.opendev.org/c/openstack/neutron-vpnaas/+/92961813:36
gsamfiracardoe: for configuring AZs in OVN, see: https://docs.openstack.org/neutron/latest/admin/ovn/availability_zones.html13:50
gsamfiraas for the physical networks, we created one LACP (2x25Gbps) bond on compute/GW nodes, enabled trunk on the bond and allowed a range of VLANs on that port. We created a br-data port in OVS and mapped physnet-data to br-data. The we set a pool of vlan ranges in ml2_conf.ini on that physnet.13:54
gsamfirato clarify: we created a br-data bridge in OVS, added the data0 bond to it and mapped physnet-data to br-data.13:59
gsamfirawe can now use physnet-data to create tenant VLAN networks13:59
gsamfirawhich in our care are used by Ironic14:00
gsamfiraeverything else uses Geneve14:00
haleyb#startmeeting networking14:00
opendevmeetMeeting started Tue Oct 15 14:00:30 2024 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'networking'14:00
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh14:00
lajoskatonao/14:00
mlavalle\o14:00
gsamfirao/14:00
kgube_o/14:00
opendevreviewLiushy proposed openstack/neutron master: Only consider the IPv4 subnets when creating a FIP  https://review.opendev.org/c/openstack/neutron/+/93240514:01
jlibosvao/14:02
elvirao/14:02
slaweqo/14:02
haleybok, we can get started seem to have a mass of people14:02
haleyb#topic announcements14:02
haleybEpoxy cycle PTG sessions (October 21-25)14:02
ralonsohhello14:02
haleyb#link https://etherpad.opendev.org/p/oct2024-ptg-neutron14:02
haleybthanks to those who have added topics, please continue to add14:03
bcafarellate o/14:03
cbuggyo/14:03
haleybi need to add some myself, will create agendas for next week this weekend14:03
haleybHave Tue/Wed/Thu/Fri (if needed) timeslots14:04
ralonsohjust a heads-up14:04
haleybTC meetings monday, and there is an eventlet meeting during the week as well14:04
ralonsohif we have xmeetings with Nova and the eventlet on wednesday 14:04
ralonsohwe should reserve these slots14:05
haleybralonsoh: i will reach out to nova today, saw a ping from ironic late friday but i was offline for a long weekend14:05
ralonsohcool14:05
haleyb#link https://ptg.opendev.org/ptg.html has the calendar with rooms and times14:06
haleybeventlet-removal is Wednesday at 13:00 and 14:0014:07
lajoskatonafor Ironic I suppose one of the topics will be this thread: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/QS73CVSVRU66MN2MBGZ76WKJFVFM7LPC/ 14:07
cardoehaleyb: I did want to get some time to have neutron/ironic as well.14:07
cardoeSorry I'm late to the meeting.14:08
cardoethe ironic core's asked me to schedule something with you guys on behalf of ironic14:08
haleybcardoe: yes, thanks for attending, can talk right after to pick a time. i've been offline14:08
ralonsohfirst should be to add a topic in the Neutron etherpad, I think, to have some context14:09
haleybralonsoh: it has been a known topic of mine (another dhcp backend), i'm just slow at adding things14:10
ralonsohno problem, just asking to know the calendar and the topics14:10
haleybReminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers14:11
haleybif no topics will just cancel, and we will not have one PTG week, we can discuss anything during a timeslot14:12
cardoeralonsoh: I added one a few weeks ago. It's not very speced out.14:13
haleyband just to pre-announce, the week after the PTG I am out (company event). will be looking for someone to lead this meeting October 29th14:14
haleybcardoe: i see one item in the agenda, i will add a little to that14:14
cardoeI need to engage with you guys better and that's on me. Apologies.14:14
ralonsohhaleyb, I can do it14:14
ralonsohOct 29th, added to my calendar14:14
haleyb^^ that week i will be in europe timezone, so around, but just busy14:15
haleybralonsoh: thanks!14:15
haleybif anyone is near the Hague i'm happy to meet up, but it's far from most i think14:15
haleyblast announcement is about antelope14:17
haleybElod sent an email to the list about Antelop transitioning to unmaintained14:17
haleyb#link https://etherpad.opendev.org/p/2023.1-antelope-final-release-before-eom14:18
haleybso we should merge any changes in flight before too long14:18
haleyb#link https://etherpad.opendev.org/p/neutron-stable-2023.1-eom14:19
haleybthat was all the announcments i had, antyhing else?14:20
haleyb#topic bugs14:21
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/F2RKF3GW52WWZY2CKKO5QXZISRRVVZG4/14:21
haleyblajoskatona was the deputy last week, and there was just a single bug (?!)14:21
lajoskatonaexactly:-)14:21
bcafarellucky you :)14:21
haleyband it has a patch14:21
lajoskatonayes, so it is in good hands14:22
lajoskatonahttps://review.opendev.org/c/openstack/neutron/+/93163214:22
haleybdid anyone have other bugs to talk about? anything that needs attention?14:23
haleybok14:24
gsamfiraI would have one. Not sure if this is the right time or place. The bug is reported here: https://bugs.launchpad.net/neutron/+bug/208453614:24
gsamfiraand is related to https://bugs.launchpad.net/neutron/+bug/199507814:24
gsamfirait has to do with using internal VLAN networks, connected to virtual routers in conjunction with Ironic baremetal (external) ports14:24
gsamfiraI am willing to work on it if you folks think this can be added to neutron14:25
ralonsohgsamfira, we talked before about this bug. https://review.opendev.org/c/openstack/neutron/+/931892 is not the way to support this feature14:26
ralonsohyou need a new L3 scheduler14:26
ralonsohsomething like this: https://review.opendev.org/c/openstack/neutron/+/87203314:26
gsamfirayes. The patch is a PoC, not intended to be merged as is14:26
ralonsohcould be a POC but the approach is incorrect14:27
gsamfirabut we still need to bind internal router ports to the same HA chassis group as the network it belongs to14:27
gsamfiraralonsoh: yes. I am aware. 14:27
ralonsohbut why the internal interfaces?14:27
haleybralonsoh: would you consider this an RFE? or just a bug?14:28
ralonsohyou need the external GW of the router to be scheduled in the same GW chassis as the external ports14:28
gsamfirabecause we want to be able to connect VLAN networks to geneve networks without going through a provider network14:28
gsamfiraand we may have several VLAN networks connected to the same vrouter and several geneve networks14:28
ralonsohok, we can have this conversation offline, not during this meeting14:28
gsamfirawith security groups enforced14:29
gsamfirasure14:29
gsamfirathanks!14:29
* cardoe wants to join that too.14:29
haleybok, moving on14:30
haleybykarel is the bug deputy this week, although i know he is out a couple of days14:30
haleybor did someone swap?14:30
ralonsohI did14:31
elviraDid we not change it in the end? I can swap 14:31
elviraOh cool, we should reflect it on the table then 14:31
ralonsohno problem, I'll talk to yatin next week14:32
haleybralonsoh: i think you just did it, but you can do it again, will have to figure out a week to swap yatin back in14:32
ralonsohsure, next time I'll ask him14:32
haleybmtomaska is in the schedule for next week14:32
mtomaskaACK14:33
haleybthanks!14:33
haleyband the bug count stayed stable this week at 73014:33
haleyb#topic community-goals14:33
haleybeventlet deprecation is clearly top of mind, and we will discuss next week at PTG14:34
ralonsohnice! I hope you have time to read the document and add any comment14:34
haleybralonsoh: are there any patches ready for merge since last week?14:34
haleyboh, did you send it to the ML?14:34
ralonsohyes and are approved14:35
ralonsohin any case, the big chunk of work must be defined next week14:35
ralonsohwe'll have time to create tasks and assign them14:35
haleybah, it was in the "#eventlet-removal - Progress & Update" thread14:36
ralonsohyes14:36
lajoskatonaI added some lines to the etherpad about stadiums, not much new information just to have all in one place14:36
lajoskatonahttps://etherpad.opendev.org/p/neutron-eventlet-deprecation14:36
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YAX2X7C6FCDDNN4SBFN7BNSUA44Z6VXA/14:37
haleybthat's the ML thread if you can't find it14:37
haleyblajoskatona: right, and the etherpad, thanks14:37
lajoskatonaralonsoh: really good summary of the eventlet things in Neutron, thanks for it14:39
ralonsohyw14:39
haleyblajoskatona: is there an update on horizon work? no pressure, just asking since i have not looked at patches14:40
lajoskatonanothing this week14:40
haleyback14:40
haleyb#topic on-demand14:41
opendevreviewMerged openstack/neutron stable/2024.2: Optimize the SG rule retrieval  https://review.opendev.org/c/openstack/neutron/+/93233014:41
opendevreviewMerged openstack/neutron stable/2024.1: Optimize the SG rule retrieval  https://review.opendev.org/c/openstack/neutron/+/93233214:41
ralonsohnothing from me, thanks14:41
haleybi did see a topic from kgube_ 14:41
kgube_Yes14:41
kgube_so, AWS and google are both providing link-local NTP servers to instances, similar to the EC2 metadata IP14:41
haleybi see AWS uses the "common" .123 address14:42
kgube_this seems nicer than providing local NTP servers via provider network, as is currebntly required in openstack14:42
kgube_the Sovereign Cloud Stack project is currently considering contributing a feature like that, if there is interest14:43
haleybkgube_: i don't know antying about Sovereign, i'm assuming it's openstack-based?14:44
kgube_but we are not sure if this is even a neutron topic, or if it could be instead part of the nova metadata service14:44
kgube_Yes, it's basically an effort to create a standardized Openstack Setup, that allows easier migration between compliant providers14:45
ralonsohqq: do you propose that openstack provides this NTP service or just be a proxy?14:45
ralonsoh(same as metadata in Neutron)14:45
kgube_I think a proxy would be more realistic14:46
ralonsohright14:46
ralonsohso I would start creating a LP bug for this RFE14:46
cardoeSo maybe the ability to define link-local proxies for different services would be the RFC?14:46
cardoeAnd the metadata service could then be a consumer of that just like NTP?14:46
ralonsohwe do (neutron) much more than being a proxy for metadata14:47
ralonsohso I would avoid touching the metadata feature14:47
haleybi would agree with ralonsoh regarding an RFE. I could see a provider maybe wanting this, but how it's implemented (metadata entries, dhcp options, etc changes?) and/or config options14:47
ralonsohexactly, and if you do this during this week, we can discuss it during the PTG14:48
ralonsohif the PTL agrees on this14:48
haleybyes, it would be a good topic if we have an RFE14:48
kgube_would this be a topic for a cross session with nova?14:49
ralonsohI don't see the link with Nova in this RFE14:49
kgube_alright14:49
haleybkgube_: i would only see a link if there is some new metadata value required, but i'm guessing it's more something in the dhcp response pointing at this proxy14:50
haleybbut that's what the RFE is for :)14:51
kgube_yeah, I think NTP is well supported by DHCP14:51
gsamfirayup. It's option 004 IIRC14:51
kgube_and there is currently no metadata key for it14:52
gsamfiraahh. It's 042 https://www.greyware.com/software/domaintime/v5/installation/dhcp.asp14:53
haleybtrying to be somewhat similar to gcp/aws might be good, i just don't know what they are doing under the hood14:53
triddeOption 042 actually. 004 is deprecated.14:53
gsamfirayup14:53
triddeYeah.14:53
gsamfirafeeling old14:53
cardoeThe reason I suggest making it generic is that technically AWS and GCP provide more than just NTP. I believe they also do DNS.14:53
cardoeSo allow it to be extensible to add DNS in the future potentially.14:54
haleybwe have to start with an RFE, then we can discuss it further14:55
haleybare there any other topics?14:55
haleybok, thanks for attending everyone, next week is in person at the PTG14:56
haleyb#endmeeting14:56
opendevmeetMeeting ended Tue Oct 15 14:56:22 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2024/networking.2024-10-15-14.00.html14:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2024/networking.2024-10-15-14.00.txt14:56
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2024/networking.2024-10-15-14.00.log.html14:56
ralonsohbye14:56
slaweqsee you14:56
kgube_bye!14:56
ralonsohgsamfira, I have 5 minutes now only14:56
gsamfirabye folks!14:56
ralonsohwhat is your timezone?14:56
cbuggyo/14:56
gsamfiraGMT+214:56
ralonsohsame as mine14:56
gsamfira\o/14:57
gsamfiraif you want we can have a chat now, or some other day14:57
ralonsohI'll be online tomorrow at 5:30UTC (7:30 local time)14:57
cardoeI was curious about gsamfira's questions on VLAN so I'd be interested in joining that.14:57
ralonsohand I won't have meetings during the morning14:57
gsamfiracool. 14:57
ralonsohso ping me at any time14:57
ralonsohcardoe, for sure, tomorrow morning14:57
gsamfira7:30 AM?14:57
ralonsohI start at this time, could be later14:58
ralonsohat any time during the morning14:58
gsamfiraeither way is fine with me. Fatherhood made sleep a pipe dream anyway14:58
cardoeI'm GMT-5 but maybe skrobul can join for me.14:58
triddeslaweq: Sorry, was a bit late for the meeting, would there be any chance you would have the oportunity to take a look at https://bugs.launchpad.net/neutron/+bug/1649909 som time? It would be a nice feature and the last comment is a suggestion that you might have some input on it.14:59
cardoeWe've got multiple physical networks with Ironic and rather than doing a neutron per wanted to understand how to best have neutron be physical network aware.14:59
gsamfiraralonsoh cardoe I am free tomorrow at any time. If you folks want to agree on a time that is ok for you both, let me know. If not, 7:30-08:00 AM is fine with me14:59
slaweqtridde hi, sure, I will take a look14:59
ralonsohok, I need to leave now15:00
gsamfiratake care!15:00
triddeslaweq: Thanks! 15:00
cardoeThat's fine. I'll poke skrobul to join for me. He's GMT I think.15:00
gsamfirasounds good15:01
skrobulgsamfira ralonsoh : I should be around from 8am/GMT onwards, preferably 9am - lmk if any of that works for you15:14
gsamfiraany time works for me15:17
opendevreviewMerged openstack/neutron stable/2023.1: Always get local vlan from port other_config  https://review.opendev.org/c/openstack/neutron/+/92695516:35
opendevreviewTakashi Kajinami proposed openstack/os-vif master: Clean up Windows support  https://review.opendev.org/c/openstack/os-vif/+/93243617:23
opendevreviewTakashi Kajinami proposed openstack/ovsdbapp master: Remove Windows support  https://review.opendev.org/c/openstack/ovsdbapp/+/93244017:36
*** elodilles is now known as elodilles_pto19:41
cardoebah. Forgot to follow up with haleyb to get an ironic + neutron session scheduled.22:42

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!