Opened 2 months ago

Closed 4 days ago

#5503 closed enhancement (duplicate)

Store and retrieves client classes in reservations in Cassandra

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


The code contributed in github37 do not support client classes specified for host reservations. Once the patch is merged, we need to extend the code to support client classes.


Change History (3)

comment:1 Changed 5 weeks ago by razvan.becheriu

The fields 'host_ipv4_client_classes_' and 'host_ipv6_client_classes_' fill the client classes information in cql_host_data_source (see CqlHostExchange?).
They are the correspondent 'dhcp4_client_classes' and 'dhcp6_client_classes' from mysql (see MySqlHostExchange?) and pgsql (see PgSqlHostExchange?).

However, there is a column in each 'dhcp4_options' and 'dhcp6_options' tables, with the name 'dhcp_client_class' (mysql and pgsql schemas).
These column are not used in cql, but neither are by mysql (see MySqlOptionExchange::createBindForSend) or pgsql (see PgSqlOptionExchange::INSERT_V4_HOST_OPTION and PgSqlOptionExchange::INSERT_V6_HOST_OPTION).

At the moment, cql_host_data_source included these columns as placeholder for whatever feature will fill these columns in the option table.

comment:2 Changed 4 weeks ago by razvan.becheriu

  • Summary changed from Store and retrives client classes in reservations in Cassandra to Store and retrieves client classes in reservations in Cassandra

comment:3 Changed 4 days ago by tomek

  • Resolution set to duplicate
  • Status changed from new to closed

This functionality is now available on master. It was merged in with github70. Resolving.

Note: See TracTickets for help on using tickets.