Skip to content

invert sled-agent's probe manager #9157

@iliana

Description

@iliana

Currently the probe manager in sled-agent periodically asks the Nexus internal API for a list of probes, and also triggers the vpc_route_manager background task if there's a new probe present to ensure the necessary firewall rules are present. These sled-agent --> Nexus requests would not be permitted today, and also introduces latency between the time probes are created/deleted and when they are actually created/deleted by sled-agent.

This logic should be inverted; sled-agent grows an API to accept the current list of probes, which Nexus periodically calls as part of a background task, which is immediately triggered when the list of probes changes. This does not need to be done immediately, but should be done if the probes_get API would otherwise need to change.

It may also be possible to remove the vpc_route_manager background task trigger in sled-agent by instead triggering the background task in Nexus when a probe is created (and removed?).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions