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

[11.0 stable] Enhance LinuxCollector to support detecting multiple app VIF IPs #4257

Open
wants to merge 1 commit into
base: 11.0-stable
Choose a base branch
from

Conversation

milan-zededa
Copy link
Contributor

Application VIF may have multiple IP address assigned. They can be either assigned directly on the same interface, or used on separate VLAN sub-interfaces which share the parent interface MAC address.

LinuxCollector should detect and publish all of them, instead of flapping between them and generating many IP address change notifications, which trigger a flood of NI and App info messages published to the controller.

For DHCP assigned IP addresses, we use lease time to determine if a previously detected IP address is still valid. For statically assigned IP, we expect to see at least one associated ARP packet every 10 minutes. Otherwise, we consider the IP address to be removed or simply not used anymore.

This commit also enhances LinuxCollector to support enabling or disabling ARP snooping in runtime, without requiring to recreate all switch network instances or rebooting device.

Signed-off-by: Milan Lenco [email protected]
(cherry picked from commit 5b2acf4)

Application VIF may have multiple IP address assigned. They can be
either assigned directly on the same interface, or used on separate
VLAN sub-interfaces which share the parent interface MAC address.

LinuxCollector should detect and publish all of them, instead of
flapping between them and generating many IP address change
notifications, which trigger a flood of NI and App info messages
published to the controller.

For DHCP assigned IP addresses, we use lease time to determine if
a previously detected IP address is still valid. For statically
assigned IP, we expect to see at least one associated ARP packet
every 10 minutes. Otherwise, we consider the IP address to be removed
or simply not used anymore.

This commit also enhances LinuxCollector to support enabling or
disabling ARP snooping in runtime, without requiring to recreate all
switch network instances or rebooting device.

Signed-off-by: Milan Lenco <[email protected]>
(cherry picked from commit 5b2acf4)
Copy link
Member

@OhmSpectator OhmSpectator left a comment

Choose a reason for hiding this comment

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

Run the tests

@OhmSpectator
Copy link
Member

The Eden test results look suspicious, I would say.

@milan-zededa
Copy link
Contributor Author

The Eden test results look suspicious, I would say.

Eden tests are very broken on 11.0
Problem is that the patches I did for Eden are likely not compatible with EVE 11.0 so I cannot bring them to this branch (but I can try just as an experiment).

@OhmSpectator
Copy link
Member

The Eden test results look suspicious, I would say.

Eden tests are very broken on 11.0 Problem is that the patches I did for Eden are likely not compatible with EVE 11.0 so I cannot bring them to this branch (but I can try just as an experiment).

So, the only way to test the PR with any smoke tests is by ztests?
I just want to have at least some guarantee that a PR does not break anything... I know it's very unlikely in this case, but still...

@milan-zededa
Copy link
Contributor Author

The Eden test results look suspicious, I would say.

Eden tests are very broken on 11.0 Problem is that the patches I did for Eden are likely not compatible with EVE 11.0 so I cannot bring them to this branch (but I can try just as an experiment).

So, the only way to test the PR with any smoke tests is by ztests? I just want to have at least some guarantee that a PR does not break anything... I know it's very unlikely in this case, but still...

OK, let's try this: #4260
If test results are better, I can then rebase this PR.

Copy link
Contributor

@eriknordmark eriknordmark left a comment

Choose a reason for hiding this comment

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

LGTM

@OhmSpectator
Copy link
Member

As far as we do not have reliable Eden tests for this PR... should we just believe the PR is fine? )
Runnign ztests...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants