BIND 10 #3221: DHCP4 should send generated NameChangeRequests to b10-dhcp-ddns

[BIND 10 Development]

#3221: DHCP4 should send generated NameChangeRequests to b10-dhcp-ddns
-------------------------------------+-------------------------------------
            Reporter:  tmark         |                        Owner:  tmark
                Type:  enhancement   |                       Status:
            Priority:  medium        |  assigned
           Component:  dhcp-ddns     |                    Milestone:  DHCP-
            Keywords:                |  Kea0.9-alpha
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  40            |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Old description:

> Once DHCP4 is able to construct !NameChangeRequests based upon DHCP lease
> allocations, it must be able to send those requests to the DHCP-DDNS
> server, b10-dhcp-ddns. DHCP4 should be extended to use the
> !NameChangeSender interface provided in libdhcp-ddns to send requests.

New description:

 Once DHCP4 is able to construct !NameChangeRequests based upon DHCP lease
 allocations, it must be able to send those requests to the DHCP-DDNS
 server, b10-dhcp-ddns. DHCP4 should be extended to use the
 !NameChangeSender interface provided in libdhcp-ddns to send requests.

--

Comment (by tmark):

 The scope of this ticket was underestimated.  Upon initial implementation,
 integrating NCR IPC into Kea was a bit more complex than originally
 thought. Kea relies on the IfaceMgr's use of select() within its receive
 methods to monitor IO activity.  It accommodated bind10 session IO
 monitoring through use a dedicated socket and callback.   In order to
 integrate NCR IO into this scheme, the following tasks to be completed:

 1. D2ClientMgr needs to instantiate a NameChangeSender based upon current
 configuration, and
 provide wrapper methods to start the sender stop the sender,  post
 messages to send, and examine
 messages in the sender's queue.

 2. NCR IPC needs to support IO readiness detection via select, such that
 it can be monitored through select.

 3. IfaceMgr needs to be extended to support registering an arbitrary
 number of external sockets with callbacks.

 4. D2ClientMgr needs to register and unregister its NameChangeSender with
 IfaceMgr when appropriate and provide a callback to service the sender's
 IO.

 5. Dhcp4Srv needs to utilize the services provided by D2ClientMgr to
 start/stop sending and post NCRs to send.


 Tasks #1 and #5 were the originally anticipated scope of this ticket. The
 work to be completed under this ticket will includes Tasks #1 and #2.

 Task #3 is covered by Trac #3315

 Task #4 and #5 will be implemented under a new ticket, Trac #3329.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3221#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development