> Cathy> vanity naming component will only update link configuration (th dladm
> Cathy> configuration) accordingly based on the rename operation, and we think
> Cathy> a broader framework is needed to address configuration changes at all
> Cathy> other levels of the networking stack.
>
> Peter> Somewhat ironically, it seems like NWAM could be that "broader
> Peter> framework" -- but that's up to them :-)
>
> So if we build it, will you come?
>
> I.e., if NWAM provides such a framework, will the Clearview Vanity Names
> project team work with us to take advantage of it?
What do you have in mind? I view it the other way around: I hope the
basic link naming mechanism provided by Clearview will be used to build a
generally useful solution to the renaming problem, so that admins can
rename links without fear that random bits of configuration will get
stranded using the old names. It's a tough problem, and something we've
explicitly left outside the scope of Clearview[1], but is well-suited to
something that slices through multiple layers of the stack like NWAM.
[1] In particular, dladm works exclusively at the data link, and thus
if a link is renamed, it does not attempt to update state like
IP filter configuration and so forth. As such, we've generally
billed this feature as a way to keep the link name *unchanged*
as the underlying hardware or topology changes. But it would be
nice if someone could solve the opposite problem of "I've got the
same link, but I want to reuse it for a new purpose and would
like to rename it to indicate that purpose."
--
meem
_______________________________________________
networking-discuss mailing list
[email protected]
