Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bpf iface auto detection #8803

Merged
merged 1 commit into from
May 30, 2024

Conversation

sridhartigera
Copy link
Member

@sridhartigera sridhartigera commented May 9, 2024

Description

This PR adds the following

  1. bond* added to the default value of dataIfacePattern Regex.
  2. Handle dynamic addition of interfaces to the bond.
  3. IFstate map changes to add more info about the type of each interface.

This PR does not handle attaching xdp programs to the bond slaves. Will be done subsequently.

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

ebpf:  If a bond master device is part of the bpfDataIfacePattern regexp, calico attaches to it and not to the slaves

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

@marvin-tigera marvin-tigera added this to the Calico v3.29.0 milestone May 9, 2024
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels May 9, 2024
@sridhartigera sridhartigera marked this pull request as ready for review May 14, 2024 01:08
@sridhartigera sridhartigera requested a review from a team as a code owner May 14, 2024 01:08
@sridhartigera sridhartigera changed the title Bpf iface detect Bpf iface auto detection May 14, 2024
Copy link
Contributor

@tomastigera tomastigera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed offline, it would be good/possible not to introduce the new option, deprecate the l3 regexp and just see of ia device is l3 or l2 and or slave/master in a bond. That would let us exclude device using the pattern that we do not care and we woul dnot need to include bondX inthe patter to include bonds.

@@ -204,6 +204,7 @@ type Config struct {
BPFForceTrackPacketsFromIfaces []string `config:"iface-filter-slice;docker+"`
BPFDisableGROForIfaces *regexp.Regexp `config:"regexp;"`
BPFExcludeCIDRsFromNAT []string `config:"cidr-list;;"`
BPFInterfaceAutoDetection string `config:"oneof(TCP,Enabled,Disabled);Enabled;non-zero"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
BPFInterfaceAutoDetection string `config:"oneof(TCP,Enabled,Disabled);Enabled;non-zero"`
BPFInterfaceAutoDetection string `config:"oneof(Enabled,Disabled);Enabled;non-zero"`

Comment on lines 133 to 134
tc.Felixes[0].Exec("ip", "link", "add", "dummy0", "type", "dummy")
tc.Felixes[0].Exec("ip", "link", "add", "dummy1", "type", "dummy")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if you named these devices eth3 and eth4 or somethign else that could interfere with the regexp?

Comment on lines 4067 to 4068
// Check if the interface is bond. If so, update the interface type for
// slaves, master.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this comment relates to?


func (m *bpfEndpointManager) autoDetectInterfaceType(intf *net.Interface) IfaceType {
name := intf.Name
if name == "tunl0" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if ipip tunnel has a different name?

}

func isBondIface(name string) bool {
bonding := fmt.Sprintf("/sys/class/net/%s/bonding", name)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could this be queried via netlink?

log.Debugf("Failed to get master interface details for '%s'", update.Name)
}
if !m.isDataIface(masterIfa.Name) {
log.Warnf("Master interface '%s' ignored. Add it to the config", masterIfa.Name)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the better behaviour would be to say "ok, master is not in the regexp but the slave is, seems like the user wants us to attach to the slave and not to the bond. User may know better, why not, lets to it. Attach to slave and ignore the master" WDYT? 🤔

@@ -92,4 +93,71 @@ var _ = infrastructure.DatastoreDescribe("_BPF-SAFE_ Felix bpf reattach object",
return out
}, "15s", "1s").ShouldNot(ContainSubstring("eth0"))
})

It("should attach programs to the bond interfaces", func() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

btw can this be tested in the unit test in bpf_ep_mgr_test.go? Woudn't that be a better place? Perhaps those cases with slave in regexp and master not in addition to this test? There is a mock for netlink.

Copy link
Contributor

@tomastigera tomastigera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, some nits around error handling

@@ -42,13 +42,27 @@ const (
FlgWEP = uint32(0x1)
FlgIPv4Ready = uint32(0x2)
FlgIPv6Ready = uint32(0x4)
FlgMax = uint32(0x7)
FlgHost = uint32(0x8)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So far, not having FlgWEP meant host. Is there any need for the new flag? We cannot have both WEP and Host. Also the name should probably we FlgHEP.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed it to FlgHEP. Want these flags to make sure iface detection is working fine.

Comment on lines 707 to 714
JustAfterEach(func() {
err := dp.deleteIface("bond0")
Expect(err).NotTo(HaveOccurred())
err = dp.deleteIface("eth10")
Expect(err).NotTo(HaveOccurred())
err = dp.deleteIface("eth20")
Expect(err).NotTo(HaveOccurred())
})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do you this clean up? Isn't dp recreated?

Comment on lines +759 to +770
err = dp.deleteIface("eth11")
Expect(err).NotTo(HaveOccurred())
err = dp.deleteIface("foo0")
Expect(err).NotTo(HaveOccurred())
genIfaceUpdate("eth11", ifacemonitor.StateNotPresent, 21)()
genIfaceUpdate("foo0", ifacemonitor.StateNotPresent, 11)()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this test? Would it make sense to add this to where bond matches the when bond is deleted slaves get the attachment?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to make sure things are fine when interface is deleted.

// update the ifaceType, master ifindex if bond slave.
link, err := m.dp.getIfaceLink(update.Name)
if err != nil {
log.Panicf("Failed to get interface information via netlink '%s'", update.Name)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Panic does not seem right? What if we just ignore the iface and log an error?

if err != nil {
log.WithError(err).Warn("Failed to list attached programs")
} else {
if err := m.cleanupOldAttach(update.Name, ai[update.Name]); err != nil {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could there be no error and ai[] to be empty as if the programs were not attached before?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. cleanupAttached handles that by checking if ai.xdp, ai.ingress, ai.egress != nil

// throw a warning and continue to attach to slave.
masterIfa, err := m.dp.interfaceByIndex(val.info.masterIfIndex)
if err != nil {
log.Debugf("Failed to get master interface details for '%s'. Continuing to attach program", iface)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
log.Debugf("Failed to get master interface details for '%s'. Continuing to attach program", iface)
log.Warnf("Failed to get master interface details for '%s'. Continuing to attach program", iface)

feels like this should be reported

if err != nil {
log.Debugf("Failed to get master interface details for '%s'. Continuing to attach program", iface)
} else if !m.isDataIface(masterIfa.Name) {
log.Warnf("Master interface '%s' ignored. Add it to the config", masterIfa.Name)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
log.Warnf("Master interface '%s' ignored. Add it to the config", masterIfa.Name)
log.Warnf("Master interface '%s' ignored. Add it to the <config name> in config", masterIfa.Name)

Copy link
Contributor

@tomastigera tomastigera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still think FlgHEP is redundant, but well, doesn't hurt either. There is some static check error. When you fix it, could you squash all the commits locally (not through GH UI) and force push it before merging? 🙏

@sridhartigera sridhartigera merged commit dfa5f61 into projectcalico:master May 30, 2024
2 checks passed
@sridhartigera sridhartigera deleted the bpf-iface-detect branch May 30, 2024 03:01
tomastigera added a commit that referenced this pull request Jun 17, 2024
…am-release-v3.28

[release-v3.28] Auto pick #8803: Interface autodetection - ebpf
@coutinhop coutinhop added cherry-pick-completed PR has been cherry-picked and removed cherry-pick-candidate labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-completed PR has been cherry-picked docs-pr-required Change is not yet documented release-note-required Change has user-facing impact (no matter how small)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants