[Maintain-dev] [JIRA] Commented: (MNT-1381) Allow multiple failover peers

Greg Connor (JIRA) jira at osuosl.org
Sat Feb 17 00:09:57 PST 2007


     [ http://bugs.osuosl.org/browse/MNT-1381?page=comments#action_11252 ]
     
Greg Connor commented on MNT-1381:
----------------------------------

I could not find anything in the documentation or the 3.0 demo that describes how to enable more than two DHCP servers.

The underlying problem is that DHCPD config must list the subnets that a server is primary-for, and secondary-for, but must NOT list other subnets that are neither primary nor secondary.  This requires writing subnets to different files.

My proposed patch had the following parts:
  Add "Workgroup" field to subnets
  Add "Failover peer" field to workgroups
  Allow subnets to be part of workgroups, not just hosts
  Allow different files to be created for different DHCP peers.

The "Workgroup" change was just one possible way to organize subnets into different groups, and provides some other bonuses as well (such as being able to apply dhcp options to hundreds of subnets without making them global or hand-editing config files).  It's not required for solving the >2 DHCP server problem, but there must be something in the user interface somewhere allowing subnets to go to different files.

Based on this info, can you tell me exactly what you believe was "fixed" for this bug?  If it's not really fixed, can you reopen it and move it to a later version?

We won't be able to use Maintain 3.0 if it doesn't correctly handle >2 dhcpd servers.  Subnets-in-workgroups would be nice but not 100% required.  I put a fair amount of effort into creating the patch I submitted... hopefully that doesn't mean our site is now isolated on a branch of our own and have lost the ability to benefit from future Maintain versions and updates.

Thanks for any info...

> Allow multiple failover peers
> -----------------------------
>
>          Key: MNT-1381
>          URL: http://bugs.osuosl.org/browse/MNT-1381
>      Project: Maintain
>         Type: Improvement
>     Versions: 2.4.0
>  Environment: Patch tested on: RedHat Enterprise Server 3.0
>     Reporter: Greg Connor
>     Assignee: Frederic Wenzel
>     Priority: Minor
>      Fix For: 3.0
>  Attachments: README.wg-failover-patch
>
>
> We have have 4 dhcp servers, one primary, and three secondaries, corresponding to the different regions.  The proposed patch allows any number of dhcp servers, not just "primary" and "secondary", and also generates multiple dhcpd.conf.data files (each intended to be read by two dhcp servers)
> ISC dhcpd supports multiple secondaries, but it's kind of a pain... you have to change 'failover peer "dhcp"' to some specific name that matches one of the failover stanzas in the peer file.  And, you have to split up the data file so that each server only sees the subnets assigned to it, and cannot see subnet declarations if it is neither primary nor secondary.
> See proposed patch here: http://lists.osuosl.org/pipermail/maintain-dev/2005-July/000102.html
> (Note that the proposed patch applies to this feature req, and also to MNT-1380.  It's possible to do MNT-1380 (Associate subnets with workgroups) by itself, but I would not recommend doing this one (Allow multiple failover peers) without doing MNT-1380 first or at the same time.  If Subnets are not somehow related to Workgroups, then more UI changes would be needed to tell Maintain which Subnet goes with which peering scheme.)
> The proposed patch also renames some of the config files, so it should be applied with care and not pushed as is to users as an update.  With a bit of tweaking, it can be made to use "primary" and "secondary" files if the feature is not activated in config, and use dhcpd.config.${hostname} if the user enters the new config option, but the patch I prepared uses just the new naming scheme.
> Old naming scheme:
> dhcpd.conf - same on all servers
> dhcpd.conf.primary - shipped to "primary" server as "dhcpd.conf.peer"
> dhcpd.conf.secondary - shipped to "secondary" server as "dhcpd.conf.peer"
> dhcpd.conf.data - auto-generated
> New naming scheme:
> dhcpd.conf.${hostname} - shipped to ${hostname} as dhcpd.conf
> dhcpd.conf.data - auto-generated, includes hosts, and any subnets without dynamic ranges
> dhcpd.conf.groups/* - shipped to all machines, but should only be included by certain hosts
> dhcpd.conf.groups/dhcpd.conf.peer.dhcp1-dhcp2-primary - Peer file for "dhcp1-dhcp2" scheme
> dhcpd.conf.groups/dhcpd.conf.peer.dhcp1-dhcp2-secondary - Peer file for "dhcp1-dhcp2" scheme
> dhcpd.conf.groups/dhcpd.conf.data.dhcp1-dhcp2 - Data file for subnets tagged as "dhcp1-dhcp2"
> I have the patch running on our production server.  OK to contact me at "gconnor at sgi.com" or "gconnor at nekodojo.org" with questions or comments about the patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://bugs.osuosl.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



More information about the Maintain-dev mailing list