On Tue, Mar 10, 2009 at 3:17 PM, Dan McDonald <[email protected]> wrote: > On Tue, Mar 10, 2009 at 03:09:43PM -0500, Jason King wrote: > > <mucho snippage deleted!> > >> Unfortunately, it still leaves the question of what to do about global >> LLDP properties. Unless I misread the rbridge documentation you >> pasted, it doesn't look like the rbridge model will map completely >> (per link: yes, global: no) since there's only one daemon. > > According to your design page (reposted for context): > > http://www.opensolaris.org/os/project/lld/design/ > > You have timer-type parameters in the lldp-global/ space. I'm guessing that > since you can instantiate link-specific versions of these as mentioned in the > lldp-<i>link</i> section of your above design page, you want a place where > systemwide default values live. > >> Just thinking out loud, while the standard strongly implies that they >> should be able to be manipulated, they are likely to be infrequently >> touched (and generally uninteresting), would it be bad from an admin >> point of view to just leave them in SMF with no corresponding method >> to manipulate them in dladm? > > IMHO SMF is an *optimal* place to put such systemwide defaults. Just make > sure you document them in the lldd(1M) man page appropriately, and mention > the the order of preference is: > > 1.) link-specific (per Jim's rbridges-inspired suggestion with > dladm). > > 2.) SMF > > That's my $0.02 anyway... > > Dan >
I haven't heard any disagreement on that, just should there be a method (outside of svccfg or libsmf calls) to manipulate them? If so, what form should it take. Currently, there's an additional dladm subcommand proposed for that, but is that optimal or needed? _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
