On Tue, Mar 10, 2009 at 7:44 AM, James Carlson <[email protected]> wrote: > Jason King writes: >> On Mon, Mar 9, 2009 at 5:28 PM, Peter Memishian <[email protected]> >> wrote: >> > I'm a bit concerned about having multiple property universes. Is there a >> > technical issue with using the existing linkprop facility for holding the >> > lldp properties (with an appropriate prefix for the properties to make it >> > clear what they're for)? Further, offhand it seems like the information >> > shown by show-discovery-stats could be displayed by the existing >> > "show-link -s" facility. >> >> One issue for the 'show-discovery-config' option (I'm assuming this is >> what you're referring to vs. the peer data) is that there is both >> global configuration items that cover all links (and would present >> issues with things like the LLDP MIB if they were to be made per >> link), and then items that are per link. I think putting the per-link >> stuff in with the linkprop stuff would be fine, but then what to do >> about the global options? Just leave them in SMF and provide no >> separate way to manipulate them outside of svccfg / libscf? Would >> that be appropriate? > > I had exactly the same issue for the RBridges project: I put the > per-link configuration bits into linkprop and the global bridge > configuration into SMF, with some logic inside libdladm to hide the > SCF interfaces. > > As far as the user can tell, it all comes from dladm.
How are the global pieces managed from dladm? _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
