Opened 10 months ago

Closed 6 days ago

#5312 closed task (complete)

Requirements and sketch design for HA (1.4 feature)

Reported by: tomek Owned by: marcin
Priority: medium Milestone: Kea1.4
Component: documentation 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


We assume that the next Kea release (1.4) will cover high availability and in general will embrace multi-core capabilities. This means that multiple instances (be it processes or threads) of Kea would be running in parallel.

This ticket calls for an overview of available approaches, should list what is in and what is out of scope and provide a napkin style design for such approach. Specific detailed design is out of scope for now, as it will be done during 1.4.

This should cover the following topics:

  • advantages/flaws of processes vs threads
  • performance and redundancy
  • properties required for an allocation strategy algorithms (how to avoid getting instances in sync)
  • sharing configuration and maintaining consistency between instances (subnets in DB?)


Change History (5)

comment:1 Changed 6 months ago by tomek

  • Milestone changed from Kea1.3 to Kea1.3-final

As discussed on 2017-09-14, the time is running out before beta deadline, so many decided to move many tickets to 1.3 final and 1.4.

comment:2 Changed 5 months ago by tomek

  • Milestone changed from Kea1.3-final to Kea1.4

After discussion with Marcin, we decided to postpone this ticket to 1.4.

comment:3 Changed 4 months ago by marcin

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

comment:4 Changed 3 months ago by tomek

The initial versions of requirements and design are now written.

comment:5 Changed 6 days ago by tomek

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

The requirements and the design are written. These are living documents and they may evolve over time, but the initial goal of having them written is done. Closing.

Note: See TracTickets for help on using tickets.