Skip to content

Conversation

@glazychev-art
Copy link
Contributor

@glazychev-art glazychev-art commented Apr 4, 2022

Delete tap interfaces on startup

Now each mechanism is responsible for dumping and deleting its interfaces on startup by tag.
In this PR kernel mechanism calls onDump

Issue: #512

Signed-off-by: Artem Glazychev [email protected]

@glazychev-art glazychev-art changed the title Add tap interface restoring Delete tap interfaces on startup Apr 6, 2022
@glazychev-art
Copy link
Contributor Author

@denis-tingaikin @edwarnicke
I've updated this PR - now each mechanism is responsible for dumping and deleting its interfaces on startup by tag. In this PR kernel mechanism calls dumpAndDelete


dumpOption := &dumptool.DumpOption{
Ctx: ctx,
PodName: opts.name,
Copy link
Member

Choose a reason for hiding this comment

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

Is this actually just a prefix for the tag? If so, could we name it something like TagPrefix rather than PodName? With the advent of networkservicemesh/cmd-nse-simple-vl3-docker#1 we will be using SDK components in non-K8s environments.

Copy link
Member

Choose a reason for hiding this comment

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

+1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. Thank you.
I've simplified a little this PR - now TagPrefix is not passed to the mechanism chain element as parameter.
Instead, there is only DumpNSM func as option, that applies OnDump func of the mechainsm

Signed-off-by: Artem Glazychev <[email protected]>
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