Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5232
Something went wrong while setting issue due date.
Closed
Open
Issue created 8 years ago by bmortier@bmortierMaintainer
  • New related issue

  • New related issue

we miss a dropdown for failover in the Create new DHCP section

Closed

we miss a dropdown for failover in the Create new DHCP section

Hello,

we miss a dropdown to be able to fill entries for the failover functionality

https://kb.isc.org/article/AA-00502/0/A-Basic-Guide-to-Configuring-DHCP-Failover.html

Cheers

(from redmine: issue id 5232, created on 2016-10-26, closed on 2016-11-13)

  • Relations:
    • relates #5198 (closed)
    • relates #5446 (closed)
  • Changesets:
    • Revision 72f6b1a1 by Côme Chilliet on 2016-10-26T10:14:17.000Z:
Fixes #5232 Added failover peer handling
  • Revision 15accf95 by Côme Chilliet on 2016-10-26T15:06:30.000Z:
Fixes #5232 Added failover peer handling
  • Revision e6930936 by Côme Chilliet on 2016-10-26T15:29:42.000Z:
Fixes #5232 failover peer also needed to be added is section list
  • Revision a25c2466 by Côme Chilliet on 2016-10-26T15:30:25.000Z:
Fixes #5232 failover peer also needed to be added is section list
  • Revision 2a7788a2 by Swaelens Jonathan on 2016-11-13T10:49:33.000Z:
Fixes #5232 Choice explicitly DHCP Primary Server and DHCP Secondary Server
  • Revision ce209743 by Benoit MORTIER on 2016-11-13T12:05:11.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setpu

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
  • Revision 5b41b971 by Benoit MORTIER on 2016-11-13T16:13:19.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setpu

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
  • Revision 8a621ca0 by Benoit MORTIER on 2016-11-13T20:27:47.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setup

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
  • Revision 25ab4c0f by Benoit MORTIER on 2016-11-13T20:51:58.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setup

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
  • Revision c6adc6aa by Swaelens Jonathan on 2017-01-17T08:46:28.000Z:
Fixes #5232 Choice explicitly DHCP Primary Server and DHCP Secondary Server

Conflicts:
	dhcp/admin/systems/services/dhcp/class_serviceDHCP.inc
  • Revision 1104dd31 by Benoit MORTIER on 2017-01-17T08:55:39.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setup
  • Revision 30720214 by Benoit MORTIER on 2017-01-17T08:56:53.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setup

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
  • Revision a95becbd by Benoit MORTIER on 2017-01-17T08:57:07.000Z:
Fixes: #5232 we miss a dropdown for failover in the Create new DHCP section

Putting default values for primary and secondary in failover setup

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>
  • Revision 6f0c4e06 by Côme Chilliet on 2017-01-17T09:45:38.000Z:
Fixes #5232 Removed unused code
  • Uploads:
    • 0001-Fixes-5232-Choice-explicitly-DHCP-Primary-Server-and.patch

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • Jonathan Swaelens
      Jonathan Swaelens @jswaelens · 8 years ago
      Developer

      Close issue

      (from redmine: written on 2016-10-26)

    • bmortier
      bmortier @bmortier · 8 years ago
      Author Maintainer

      hello,

      i found we need isc-dhcp-server-ldap at minimum 4.3.3 to benefit from it reading the ldap failover objects, this version is only on strech will backport it to jessie to test our code.

      i also think we need 2 dropdown one for the primary and one for the secondary as the field needed are not the same and some should not be present in secondary

      Cheers

      Reopen issue

      (from redmine: written on 2016-11-03)

    • Jonathan Swaelens
      Jonathan Swaelens @jswaelens · 8 years ago
      Developer

      I just tried it on stretch. We dont neet another dropdown, the DHCP find the information in 1 failover-peer record. But we need a solution to define when a DHCP is primary or secondary on a system so that we can use failover dhcp.

      It would be nice to have some default value for failover-peer. mclt 3600 and split 128, that are also mandatory values.

      Cheers.

      (from redmine: written on 2016-11-04)

    • Jonathan Swaelens
      Jonathan Swaelens @jswaelens · 8 years ago
      Developer

      Hello,

      I tried to make a patch so we may choose the primary and secondary server because we need the possibility to set the 2 attributs if we use a failover class.

      Cheers.

      (from redmine: written on 2016-11-12)

    • bmortier
      bmortier @bmortier · 8 years ago
      Author Maintainer

      Hello,

      applied, need to be tested with our 3 scenarios to see if there is no regression with dhcp in non failover mode

      Cheers

      (from redmine: written on 2016-11-13)

    • bmortier
      bmortier @bmortier · 8 years ago
      Author Maintainer

      hello,

      from ldap view its seems correct, putting it on solved, still need test :)

      Cheers

      (from redmine: written on 2016-11-13)

    • bmortier
      bmortier @bmortier · 8 years ago
      Author Maintainer

      Hello,

      added default values for primary and secondary in failover setup

      Cheers

      (from redmine: written on 2016-11-13)

    • bmortier
      bmortier @bmortier · 8 years ago
      Author Maintainer

      Close issue

      (from redmine: written on 2016-11-13)

    • Jonathan Swaelens closed 7 years ago

      closed

    • bmortier reopened 7 years ago

      reopened

    • bmortier closed 7 years ago

      closed

    • bmortier added Added label 6 years ago

      added Added label

    Please register or sign in to reply
    Assignee
    Jonathan Swaelens's avatar
    Jonathan Swaelens
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets