Hi Alan / Calum,
Thee are two elements here:
1) NCP Selection - Automatic vs User
On this one, I think you've captured my suggestion, but
I'd still like
Calum's input on this...
2) NCP Policy / NCU Selection Rules
This one is a little more difficult to achieve, and I'll
discuss in detail
below.
I'll try break the NCP Policy area down more:
1) Activation Mode
Currently we only have 3 settings available to use in
the UI Spec:
- Disabled (NEVER)
- Enabled (ALWAYS)
- Conditional (CONTINGENT)
We now need to add MANUAL and DEPENDENT, so how do we
address this:
- MANUAL v NEVER
I'm actually not sure what the different is between
NEVER and MANUAL -
on both cases the admin could switch it on manually -
is it that in the
case of NEVER nwamd would actually tear it down when
it notices it is
activated, while if it's set as MANUAL, nwamd will
ignore it?
If this is the case, then they could be both
represented as Disabled in
the checkbox, but have another (seen when you select
the NCU) in the
rules section to say something like :
[ ] Ignore external modification of interface.
- DEPENDENT v CONTINGENT
Again, I think these could be represented as
Conditional in the checkbox
in the list, and have the decision on whether it's
based on priority or
based on dependency on the "dependency"
string evaluation, eg:
(*) Activate based on ordering (Priority
settings)
( ) Activated based on following rules:
[ ]
We could even expand on the rules element to provide a
UI representaion
(rather than a string) - something more like that
currently in the UI
Spec for "Location Preferences: Rules" (pg
18):
(*) Activate based on ordering (Priority
settings)
( ) Activated based on following rules:
Matches ( ) all or (*) any of
[NCU Type v] [ is v] [ LINK
v] [+][-]
[Media Type v] [ is v] [ Ethernet
(802.3) v] [+][-]
How would this sound?
2) Priority
When it was only possible to have 1 interface at a given
priority, a
simply list provided all that was needed to visualise,
and to reorder was
a simply drag/drop, or Up/Down Buttons.
ath0
bge0
bge1
When it comes to Visualising multiple interfaces at a
given priority, then
we need to consider using a tree to view the list:
> Prio 0 (SHARED)
- bge0
- bge1
> Prio 1 (EXCLUSIVE)
- ath0
This is certainly possible to do - it's not clear to me
how to name the
priority nodes on the tree, but a it could also be
possible to have the
tree express the "priority group mode", in
that EXCLUSIVE wouldn't be a
child node, but level with the priority:
> Prio 0 (SHARED)
- bge0
- bge1
- ath0 (EXCLUSIVE)
SHARED and ALL would have the same visual
representation.
The "priority group mode" will probably also
need to be modifiable for an
NCU, and this would be the only way to promote/demote an
interface.
I think that is enough to provide a solution, or at least
spark off the
discussion... ;)
Thanks,
Darren.
Alan Maguire wrote:
> For NCPs (an NCP is a set of link/IP interface
configuration preferences),
> we need to support the switching of active NCP from
automatic
> (system-provided,
> non-editable network configuration which specifies
autoconfiguration
> for IP interfaces and enables hotplugged links
automatically)
> to user-specified configuration (which allows
specification of address
> acquisition
> method, policy preferences such as "prefer wired
over wireless",
> "one link at a time should be active" etc).
I've tried to capture some
> of our
> inital ideas about GUI support for NCP switching under
section 8.3 here:
>
> h
ttp://opensolaris.org/os/project/nwam/p1spec/NCPs/
>
> It may be helpful to have the GUI spec open when taking
a look
> at this:
>
> http://opensolaris.org/os/project/nwam/UIDesi
gn/Phase1/nwam-1.5.pdf
>
> Comments are welcome!
>
> Alan
> _______________________________________________
> nwam-discuss mailing list
> nwam-discuss opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/nwam-discu
ss
_______________________________________________
nwam-discuss mailing list
nwam-discussopensolaris.org
http://mail.opensolaris.org/mailman/listinfo/nwam-discu
ss
|
