[brussels-dev] Brussels: framework commitment materials

[James Carlson]

Sowmini.Varadhan at Sun.COM writes:
> On (10/05/07 06:52), James Carlson wrote:
> >   Bonus points for making
> > ndd issue warnings when used in the now-obsolete manner.
> 
> We were going to do this in each driver as it was converted
> (e.g., the ndd handler in bge will print out a message such as the
> one used for the ndd usage to set ip_forwarding as part of
> PSARC/2003/166). 

That sounds perfect.

> > I think the questionable part here is actually the timing of this
> > message and exactly what the message will say.  Perhaps it's too early
> > to be directing people to use dladm instead of ndd when this project
> > integrates ... ?
> 
> We can minimally emit warnings for all the MII properties of each converted
> driver after 2007/429. The other properties (e.g., drain_max)
> are typically hacky outliers, that can be converted to private
> properties (as shown in Appendix B of the design doc), and when 
> that is done, we can still emit a message for these in the ndd path. 

OK.

> > The design document seems to focus on the mechanics of making the
> > compatibility bits work.  That makes sense, but it doesn't explain
> > what we want users to do.
> 
> Ok, so that makes me feel that the 20q look like the more appropriate
> place to address the transition strategy. I just updated the 20q.txt
> with this information (see response to Question 2).

OK; I think we're in sync.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677