That looks like a bug. We need to run makedhcp when restarting xcatd on a service node to be sure the dhcpd.conf and leases files are up to date, but seems we're taking a slightly different code path that misses the "disjointdhcps" processing. I'll open another defect...
(For those that know the code internals: during xcatd startup on the
service node, AAsn.pm is calling the dhcp.pm process_request function
directly and bypassing the preprocess_request where disjointdhcps is
handled).
Linda
From: Dave Barry <[email protected]>
To: xCAT Users Mailing list <[email protected]>
Date: 07/20/2011 02:27 PM
Subject: Re: [xcat-user] Confused regarding service node pools and
defining specific service nodes
Excellent! Thanks for the clarification.
Something else I noticed that may be a bug, and perhaps you or someone else
can chime in. I have "disjointdhcps" set to 1 so that I could,
theoretically, separate out which compute nodes will boot from which group
of service nodes in a service node pool architecture. This works great when
doing nodeset's (service nodes that are not assigned to a specific node
won't write out that node's lease information in dhcpd.leases), however
when the xcatd process is restarted on a service node, instead of it
writing out the DHCP lease information for only the nodes it is responsible
for, it appears to write out the lease information for every node, thereby
apparently ignoring my "disjointdhcps" setting in the site table.
Is this a bug, or a feature? :)
<<inline: ecblank.gif>>
------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
