On 09/05/14 at 10:18am, Marc Milgram wrote:
Hi,
Sorry for the late response.
On 08/21/2014 08:34 AM, Baoquan He wrote:
>I think you are right about this. Since Marc said other modules could
>use network too, such as heartbeat. In kdump we need build the network
>conf for it. I don't remember this clearly, need wait for Marc to check
>this.
>
>The reason I tried the exact route is some duplicate routes may exist in
>dracut. From dracut's point of view, it can handle route correctly if
>user can pass it the correct route. If duplicate routes are added,
>either we tolerate the warning message, or we require to change the
>implementation of dracut handling. But from dracut's side, they don't do
>anything wrong, why they need be changed.
Hi Marc,
Re-read your mail, I am kind of confused.
I have found the following things that could each use a different
route, and should be fully supported:
* ssh/NFS/iscsi - but only one of these per configuration (as far
as I know).
For above configuration, we can get route and add in 2nd kernel by kdump
scripts.
* Name resolution (/etc/resolv.conf specifies this)
* Heartbeat
For above 2, how do we handle them? And who will setup network
connections for them, especially Heartbeat?
Currently even previous design just add routes through a specific NIC.
If kdump script only take care of the NIC which dumping will go through,
but Heartbeat takes different path through different NIC, what will
happen? Is this related to static route issue and need be considered in
kdump scripts?
Thanks
Baoquan