Bug 1902075
| Summary: | [OVN][Multicast] Packets flooding when mcast_relay is enabled and there are subscribed clients | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux Fast Datapath | Reporter: | Roman Safronov <rsafrono> | ||||
| Component: | ovn2.13 | Assignee: | Dumitru Ceara <dceara> | ||||
| Status: | NEW --- | QA Contact: | Jianlin Shi <jishi> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | FDP 20.D | CC: | ctrautma, dceara, jishi, lmartins, mmichels, ralongi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1901615 | ||||||
| Attachments: |
|
||||||
|
Description
Roman Safronov
2020-11-26 18:27:43 UTC
Created attachment 1733871 [details]
capture on one of the subscribed clients after single multicast packet sent
Hi Lucas, Would it be an option for OpenStack to restrict the IP Multicast Relay flood tree by setting a new option on the logical router, e.g., mcast-relay-chassis=<chassis-name>? Like this we could try to ensure in OVN that multicast traffic is routed only once, on the chassis matching mcast-relay-chassis. Thanks, Dumitru (In reply to Dumitru Ceara from comment #4) > Hi Lucas, > > Would it be an option for OpenStack to restrict the IP Multicast Relay flood > tree by setting a new option on the logical router, e.g., > mcast-relay-chassis=<chassis-name>? > > Like this we could try to ensure in OVN that multicast traffic is routed > only once, on the chassis matching mcast-relay-chassis. > > Thanks, > Dumitru Hi Dumitru, From the OpenStack perspective it wouldn't be a problem to set that option. The given chassis would be a gateway chassis (one with the "enable-chassis-as-gw" option set to the "ovn-cms-options") ? The only problem I can see with this approach is in terms of HA, what if that chassis goes away ? Usually it's core OVN that is monitoring those things via BFD. Another approach perhaps would be point to a HA Chassis Group so that the Chassis with the highest priority would be the one doing the routing and, if it goes away, the next Chassis with the highest priority would be pick. Something like mcast-relay-chassis-group=<ha_chassis_group name>. What do you think ? (In reply to Lucas Alvares Gomes from comment #5) [...] > > Another approach perhaps would be point to a HA Chassis Group so that the > Chassis with the highest priority would be the one doing the routing and, if > it goes away, the next Chassis with the highest priority would be pick. > Something like mcast-relay-chassis-group=<ha_chassis_group name>. What do > you think ? This is way better indeed. I hadn't thought about HA. I'll go ahead and try to implement this. Thanks, Dumitru Hi Dumitru, according to the latest comment you were going to try to implement the idea proposed by Lucas. Is this something you've already done? Or is this still in progress? (In reply to Mark Michelson from comment #8) > Hi Dumitru, according to the latest comment you were going to try to > implement the idea proposed by Lucas. Is this something you've already done? > Or is this still in progress? Hi Mark, I didn't get a chance to try out the ideas discussed above. Thanks, Dumitru |