Erik Nordmark wrote:
>>> Say you have an ipmp0 group with bge0 and bge1.
>>> Would NWAM come around and try to use bge0 and bge1 directly?
If NWAM knows about the group as it is setup by NWAM, it
will know how to deal with it. If NWAM does not setup
the group, it has to detect that the group is being set
up/tear down and then react to it according to a profile.
This is why I chose to use "outside the NWAM framework."
>>> And how would IPMP be configured in such a case? Using /etc/hostname.???
>>
>>
>> NWAM can provide a way to setup IPMP and it will know how
>> to deal with it. The thing it ignores and does not understand
>> is a user bypasses NWAM and sets up an IPMP group. To handle
>> this, NWAM needs to detect and react to that. I am not saying
>> that we must not do that, in case you misunderstood.
>
> I don't understand. You seemed to be saying that all three IPMP items
> you listed could be deferred.
No, I was trying to find out what people consider to be
must support feature in the first deliverable. I am not
saying that all the three features I mentioned must be
deferred. This is the "multiple levels" I referred to in
my previous email. People may think that the first NWAM
deliverable does not need to have all three. Or people
may think that this is the whole point of the project so
we must do all of them. That is the original question.
> I don't understand how you can do that and not potentially brickify a
> system where both NWAM and IPMP are used. Both IPMP/ifconfig and NWAM
> will try to modify the interface configuration.
It depends on how we architect NWAM to support IPMP. It
is the detection and reaction to configuration done outside
the NWAM supported method which can cause potential problem.
A user can use NWAM to setup IPMP groups and everything
works fine. But if a user decides to tear down the IPMP
setup or change other configuration, say, remove the
/etc/resolv.conf file when DNS is used, what should NWAM do?
> Thus for the system to be functional at all when both are used, NWAM
> needs to be aware of IPMP groups and the relationship between these
> groups and the underlying NICs; only that way can it avoid potentially
> disrupting the configuration.
The question is not about whether NWAM knows about the
relationship, the question is about how NWAM reacts to
configuration change done not through NWAM. NWAM can
know about IPMP and set things up properly. But a user
can tear down the whole thing after it is set up. The
key is how NWAM should react to that. We may choose to
ignore this kind of disruption in the first deliverable.
Or if this is a must have feature, we need to decide how
to deal with that.
> Of course, since I think servers are more important than laptops, I
> think all the IPMP items are high priority. But that's a separate from
> what's the minimum NWAM needs to do to avoid brickifying an IPMP system.
--
K. Poon.
kacheong.poon at sun.com
