| opendevreview | Merged openstack/ironic master: Filter out NoMatch actions in _vif_attach_tbn https://review.opendev.org/c/openstack/ironic/+/974569 | 00:05 |
|---|---|---|
| opendevreview | Merged openstack/ironic master: Update TBN config file to improve trait structure https://review.opendev.org/c/openstack/ironic/+/974776 | 00:05 |
| TheJulia | jrosser: oh, I guess if we had a clean path for some details to map in an ml2 plugin, might be easier to discuss in high bandwidth at some point as opposed to asynchronous on irc. | 00:43 |
| *** gmaan_afk is now known as gmaan | 02:01 | |
| opendevreview | Takashi Kajinami proposed openstack/ironic-ui master: Remove MANIFEST.in https://review.opendev.org/c/openstack/ironic-ui/+/975982 | 07:44 |
| opendevreview | Takashi Kajinami proposed openstack/networking-baremetal master: Remove MANIFEST.in https://review.opendev.org/c/openstack/networking-baremetal/+/975983 | 07:45 |
| opendevreview | Takashi Kajinami proposed openstack/ironic-tempest-plugin master: Remove MANIFEST.in https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/975990 | 07:48 |
| TheJulia | jrosser: I’m going to be in Ireland next week, but you’ve got me interested. What tuning are you curious to help enable do your deployed baremetal? | 14:48 |
| jrosser | TheJulia: wont mac/l2vni stuff be in the bgp/evpn routes? | 14:59 |
| TheJulia | Yes, they would be. | 15:00 |
| jrosser | yeah, so if you have a workload that is multicast heavy (like many 10's Gbps) then ingress replication will be a problem | 15:01 |
| TheJulia | How so? I mean at that point you likely don’t want to dumping that through a neutron router. | 15:01 |
| jrosser | as you will saturate the uplink from a leaf with N times the traffic that the mcast source generates, once for each destination vtep | 15:01 |
| jrosser | i don't forsee there being a neutron router in the data path | 15:02 |
| jrosser | for a baremetal <> baremetal node flow of data | 15:02 |
| TheJulia | Hmm, true, so what would you envision? | 15:03 |
| TheJulia | For what it is worth, the metal tube’s boarding door has closed, I need to move to airplane mode soon. | 15:03 |
| TheJulia | Would you have a limited number of VMs on that segment? | 15:04 |
| jrosser | perhaps i'm just raising the issue that ingress replication is not univerally suitable | 15:04 |
| jrosser | and a particular environment might very deliberately want to choose native multicast in the underlay instead (leveraging the switch ASIC hardware) to handle BUM traffic with "normal" protocols for that like PIM | 15:05 |
| TheJulia | I think we’re aware of that, but for general cases it should be relatively suitable for most deployments with generalized workloads. | 15:06 |
| TheJulia | But with vxlan as well? | 15:06 |
| TheJulia | I wonder if that is a possibility, or not, and ultimately what is the ASIC’s preference. | 15:09 |
| jrosser | today i have a manually configured switch setup that is very much like the one in that set of patches ends up with | 15:09 |
| TheJulia | hjensas: ^^^ may be an interesting topic for us to discuss. | 15:09 |
| TheJulia | Interesting! | 15:10 |
| jrosser | so a backend of vxlan/evpn and a resulting set of vlans which are presented as neutron provider networks | 15:10 |
| jrosser | precisely because functionality like the new proposed stuff is missing | 15:10 |
| TheJulia | Heh, okay! | 15:10 |
| jrosser | and that must use native multicast in the underlay rather than ingress replication because the workload requires it | 15:10 |
| jrosser | (think imaging sensor data at many gbps just sprayed out as rtp multicast) | 15:11 |
| jrosser | and we fully leverage the switch asic (arista/broadcom in this case) to make that efficient | 15:12 |
| jrosser | whilst knowing we make a compromise with the potentially limited multicast routing table scalability | 15:12 |
| jrosser | so really i just wanted to raise that as an operator, it would be great in the future if there was a dial to enable things other than ingress replication and it doesnt get somehow fundamnetally written into the model across ironic/neutron | 15:13 |
| TheJulia | That makes sense. That is a key detail because it is a conscious and informed decision at that point, the challenge with all of this is general applicability. Definitely baked in hard to force only ingress replication. There is a neutron native bgp even model under development which will basically force it, but we’ve got a streamlined direct attach model. If you get time, checkout the later NGS patches | 15:15 |
| TheJulia | You’ll see some other options there, just for Cisco specially we’re leaning hard towards ingress replication in large part due to the differing model. The big issue is we’re trying to keep things as scalable as possible | 15:16 |
| jrosser | it may all turn out to be trivial in n-g-s (like a couple of extra config lines perhaps) | 15:19 |
| jrosser | nut more complicated to figure how where the multicast groups etc come from via neutron | 15:19 |
| jrosser | *but | 15:19 |
| TheJulia | Or, just not. | 15:20 |
| TheJulia | A variation and challenge is numbering, since we can’t use the segmentation id as a root for things like intermediate interface numbering. | 15:21 |
| TheJulia | So, original variations had mcast groups as well. Just perceptions were that was also dated. Maybe… not. | 15:26 |
| jrosser | i think i would perhaps look at it depending on which industry you are in, rather than being dated or not (see introduction here https://www.arista.com/assets/data/pdf/Whitepapers/EVPN-Data-Center-Multi-Tenant-Multicast-Services-WP.pdf) | 16:28 |
| TheJulia | See https://review.opendev.org/c/openstack/networking-generic-switch/+/972763/5/networking_generic_switch/devices/netmiko_devices/arista.py :). Granted, we dialed it back but it could make sense. | 17:13 |
| jrosser | ahhh that’s cool. - I’ve barely had enough brain cycles to lurk and watch the conversation about this :) | 19:01 |
| jrosser | next week I can check that config against something running | 20:19 |
| TheJulia | Happy to peel back to that version if it would help you or extract the specific groupings for it | 21:26 |
| TheJulia | anyway, I should go find power plugs | 21:27 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!