#5675 closed enhancement (complete)

HA: Implement a command to resume operation after holding in a waiting state.

Reported by: tomek Owned by: marcin
Priority: medium Milestone: Kea1.5
Component: high-availability Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Ticket #5673 covers requirements and a design for a new feature that allows Kea running in HA mode to hold in a waiting state.

This ticket covers implementation of a command that would tell Kea to conclude its waiting and move to operational state. Two names were proposed: ha-go and ha-state-set.

One aspect to consider here is whether this mechanism could be extended in the future to move Kea to specified state on demand, e.g. partner-down. From that perspective a name that is generic and can be later extended with new capability is more preferred.


Change History (7)

comment:1 Changed 20 months ago by marcin

  • Owner set to marcin
  • Status changed from new to accepted

comment:2 Changed 20 months ago by marcin

  • Owner changed from marcin to UnAssigned
  • Status changed from accepted to reviewing

I implemented the ha-continue command and I also added sections into the User's Guide that describe the feature.

Proposed ChangeLog entry:

14XX.	[func]		marcin
	Implemented ha-continue command in HA hooks library and
	updated the Kea User's Guide with the information how to
	pause and resume the HA state machine.
	(Trac #5675, git cafe)

comment:3 Changed 20 months ago by marcin

  • Owner changed from UnAssigned to marcin

I am taking this ticket back as it needs to be rebased to the latest changes for $5674.

comment:4 Changed 20 months ago by marcin

  • Owner changed from marcin to UnAssigned

I made all necessary updates and the ticket is again ready for review.

comment:5 Changed 19 months ago by tmark

  • Owner changed from UnAssigned to tmark

comment:6 Changed 19 months ago by tmark

  • Owner changed from tmark to marcin

I added a missing "the" to the guide so please pull first.

I wonder if we should add a sentence or two reminding people that pausing one server can affect
that states of other,cooperating server(s)? I suppose it ought to be obvious but one never knows.

Changes are straight forward and fine for merging. Unit tests pass under Centos 7.4.

On a related note, I really think we should implement a command(s) to put a running server into a specific state and/or pause it. Do we have plans for that in 1.5 or at all? Heck even ISC DHCP can be told to go to a given state ;).

comment:7 Changed 19 months ago by marcin

  • Resolution set to complete
  • Status changed from reviewing to closed

Added a note as suggested and merged with commit 98a9bd4f6766ff2f53681d84d55c56988be4d501

Note: See TracTickets for help on using tickets.