Alan Maguire wrote: > we've talked a bit about the SMF representation of datalinks and > interfaces, and how these representations will be present whether > NWAM is enabled or not. previously, our API design > assumed that manipulation of these entities was an NWAM-specific > activity, and as such the API for handling such manipulations > was part of libnwam. what i'd like to propose is a library > API that is not tied to any network policy engine, provisionally > called libnetadm. the aim is to have an API that any policy > engine can use to manipulate the link/interface representations. > these manipulations include creating/destroying instances, > setting/retrieving properties/dependencies, renaming instances > etc. > > any comments, particularly from the Clearview folks about the > adequacy of the API would be appreciated. thanks!
At the link-layer, we already have an API responsible for creating/deleting/renaming/(etc.) data-link objects. The implementation of libdladm needs to change to use SMF as a repository and tweak services (obviously, that much is already known), but is it beneficial to implement this through another library? -Seb
