Opened 5 years ago

Last modified 3 years ago

#3851 new enhancement

Move FQDN generation to Allocation Engine to avoid lesae db update

Reported by: tmark Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: dhcp4 Version: git
Keywords: performance 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 (last modified by tomek)

While working on #3779 it became apparent that there exists a potential optimization that may be worth further exploration:

ISSUE: In cases when the server generates the FQDN for the client, the lease db is written to twice. Once when the lease is allocated and again shortly after once the FQDN has been generated.

This was the most expedient thing to do at the time since the generated name requires the (an) IP address from the lease, as well as configurable items such as prefix and suffix.

If the second update could be eliminated this could be a performance improvement, though it would only be realized in high traffic uses in which the server generates the FQDN. It is unclear how often this occurs in the real world.

In order to move name generation into the allocation engine, it would need to know when name generation is needed, what values to use for prefix and suffix, and of course how to construct the name. All of which can be added to the ClientContext by the server as needed. This would avoid coupling the allocation engine with CfgMgr?.

I've attache a small tar file for a utility class that could be instantiated by the server and passed into the context which is capable of generating a name given an IP address as a possible path to a solution.

Note while component is listed as dhcp4 this applies to dhcp6 as well.


Subtickets

Attachments (1)

fqdn_gen.tar (10.0 KB) - added by tmark 5 years ago.
possible utility class

Download all attachments as: .zip

Change History (5)

Changed 5 years ago by tmark

possible utility class

comment:1 Changed 4 years ago by hschempf

  • Milestone changed from Kea-proposed to Kea1.1

comment:2 Changed 4 years ago by tomek

  • Milestone changed from Kea1.1 to DHCP Outstanding Tasks

comment:3 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

comment:4 Changed 3 years ago by tomek

  • Description modified (diff)
  • Keywords performance added
Note: See TracTickets for help on using tickets.