On Thu, 05 Feb 2009 09:35:05 -0500
James Carlson <James.D.Carlson at Sun.COM> wrote:
[...]
> > * if only one if is active, get ns info associated with that interface;
> > else if nameservices_ifs is non-empty, try to get ns info from each if on
> > that list in turn; else fail
>
> Please get information from all interfaces in parallel -- or, better
> yet, as soon as the interface is configured. There shouldn't be any
> serialized behavior in NWAM; it's a major failing in the old
> (pre-NWAM) system.
[...]
The intention is to get information as early in the process as possible
(usu. at the point we have or are getting basic L3 config) independent
of if the user has stated an interest in information or not (mod the
user might have said to be quiet on a specific interface; that won't be
the default).
For the rest of it we need to provide a f(current_config,
new_config_item) -> new_config that has a couple layers of control
surfaces. At the top are ones that assume the fairly standard
wired+wireless with one connected and DNS kind of config. Deeper down
we find one that allows the user to filter information as it makes its
way to the configuration database. This is probably simplifying too
much but often we end up with the trees crowding out real solutions on
this issue.
For 1.0 I'd like to see us do something fairly simple. I think getting
the infrastructure there will allow people to explore how to provide
the configuration control infrastructure needed but as importantly
solve how to expose that functionality to the user is very important at
this stage in the project. That is let the per interface information
gathering happen in parallel with the individual tree chopping ;)
mph
