Opened 5 years ago

Closed 5 years ago

#3559 closed task (complete)

Design for host reservation

Reported by: tomek Owned by: marcin
Priority: medium Milestone: Kea0.9.1beta
Component: database-all 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

Description

We need a proper design for host reservation, use cases written down.

There's fair bit of preparatory work here:
https://lists.isc.org/pipermail/kea-dev/2014-June/000044.html

But we still need to iron out the details. In particular:
Whether we load hosts info on start-up/reconfigure (slower startup, faster operation) or consult database during packet processing (fast startup, slower operation).

Also, as this is a second (out of three planned, the last one being subnet) information entity that is going to be stored in a database, we need to design how users configure their database access. In particular, Marcin and I discussed two cases:

  1. user keeps his leases in database A, but wants to keep host info in database B
  2. user wants to keep everything in a single database and wants to keep his configuration simple.

If leases and hosts are kept in separate databases, the solution will be more flexible, but at the same time it will be more difficult to sanity check it.

We need to keep in mind that there's configuration scaling parameter that is around the corner. There are many similarities, so the host reservation design should probably foresee some code reuse.

Subtickets

Change History (7)

comment:1 Changed 5 years ago by marcin

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

comment:2 Changed 5 years ago by marcin

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

I have created a design document on the wiki:
http://kea.isc.org/wiki/HostReservationDesign

Please review.

comment:3 Changed 5 years ago by tomek

  • Owner changed from UnAssigned to tomek

comment:4 Changed 5 years ago by tomek

  • Owner changed from tomek to marcin

comment:5 Changed 5 years ago by marcin

  • Owner changed from marcin to tomek

I addressed Tomek's comments and replied here: https://lists.isc.org/pipermail/kea-dev/2014-October/000148.html

There were also issues rised by Thomas which I addressed and replied in the following thread: https://lists.isc.org/pipermail/kea-dev/2014-October/000147.html

comment:6 Changed 5 years ago by tomek

  • Owner changed from tomek to marcin

comment:7 Changed 5 years ago by marcin

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

There were followup discussions in the threads cited above. The consensus was reached and the document has been updated accordingly. We agreed with Tomek on jabber that the ticket can be now closed. Should any followup questions occur, we will address them on the kea-dev mailing list.

Note: See TracTickets for help on using tickets.