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
-------------------------------------+-------------------------------------

Comment (by tmark):

 This ticket includes tasks 1 and 2 above.  Changes include:

 * Adding new class, dhcp_ddns::!WatchSocket to provide a file descriptor
 whose readiness to read by set and unset.  Adding the use of !WatchSocket
 to !NameChangeUPDSender, such that it the sender's asynchronous IO can be
 monitored with select.

 * Added accessors for the internal send queue and its contents to
 !NameChangeSender (primarily for testing).  Adding a method, assumeQueue,
 to allow one sender instance to take another sender's queue contents.

 * Adding !NameChangeSender instance management and wrapper services to
 D2ClientManager. This includes instantiating the sender when the manager
 is passed a new configuration as well as methods to start and stop the
 sender, posts requests to send, monitor the sender's queue.

 * Added the sender callback, runReadyIO (part of Task 4).

 * Added a new file, d2_upd_unittest.cc which contains tests that exercise
 the NCR UDP IO through the D2ClientMgr.


 The following class diagram shows the D2ClientMgr and how it relates to
 NameChangeUDPSender:

 [[Image(d2_client_mgr_and_udp_sender_classes.svg)]]


 The following sequence diagram shows the overall flow of events through
 D2ClientManager as it instantiates a UPD sender, receives a NCR to send,
 and sends that NCR:

 [[Image(udp_ncr_through_mgr_sequence.svg)]]

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