wiki:RTeam20101130

R-Team Sprint

Start: 30 November 2010
End: 14 December 2010

This sprint is the first two-week sprint of a six-week release cycle. At the end of the cycle we hope to deliver:

  • The ability to use a simple recursor as a forwarder
  • The first part of the code for the recursor cache

Tasks

Tasks Carried Through from Sprint Ending 30 November 2010

Refactoring: put in library for DNS services
Extracting common code from the authoritative and recursive servers into a common library. It was agreed though that this will only be done when all branches from ticket #327 have been merged back into that ticket and then the completed ticket merged back into trunk.
Estimate: 5
Assigned:
Status:

Refactoring: put in library for DNS services - Review
Assigned:
Status:

Review of All Tasks related to #327
This involves a broad review of the changes made to ticket #327 before it is merged back into trunk.
Estimate: 5
Assigned: Shane, Stephen, Jelte, Likun
Status: Complete

Merge #327 back into trunk
Estimate: 1
Assigned: Jelte
Status:

Demux: design phase 1
The Demux component is the component that matches incoming responses with outgoing queries. This is a task for Evan (if we can get him back from BIND-9 for a day) to write down initial thoughts on this.
Estimate: 3
Assigned:
Status:

Demux: design phase 1 - Review
Assigned:
Status:

Demux: design phase 2
Expanding Evan's thoughts into a more detailed design.
Estimate: 5
Assigned:
Status:

Demux: design phase 2 - Review
Assigned:
Status:

#408: General Control Logic/Logic? to Handle NS and A Queries
This is the framework of the processing described in NameserverAddressStoreDesign, and includes the part that actually issues the queries and, when the queries return, updates the data structures and handles the post-processing.
Estimate: 3
Assigned: Michal
Status: Completed

#408: General Control Logic/Logic? to Handle NS and A Queries - Review
Assigned: Stephen
Status: Completed

#356: Logic to update RTT/Address Selection Logic/RTT Banding
These tasks have been combined from the previous sprint. This concerns the logic needed to select the address with the lowest RTT, yet periodically try other addresses in case their RTT has dropped.
Estimate: 2
Assigned: Ocean
Status: Completed

#356: Logic to update RTT/Address Selection Logic/RTT Banding - Review
Assigned: Stephen
Status: Completed

#405: Add basic support for addressing individual list items
i.e. use [i] in a data structure identifier string to get to the i-th element (or something similar).
Estimate: 3
Assigned: Jelte
Status: Completed

#405: Add basic support for addressing individual list items - Review
Assigned: Stephen
Status: Completed

#384: Fix bindctl printing of config data
Currently bindctl tries to be a bit smart (and not too well), and does not automatically print the contents of maps or lists unless you specifically ask for that map or list item. That property, combined with the current inability to address individual list items, makes it currently impossible to actually print out the contents of a list that contains maps. So it should be simpler: it should either print out 1 level of data (perhaps the default), or print the full JSON representation of whatever is there.
Estimate: 5
Assigned: Jelte
Status:

#384: Fix bindctl printing of config data - Review
Assigned:
Status:

New Tasks in this Sprint

Recursor Cache

Recursor Cache: Requirements
Drawing up the requirements for the recursor cache.
Estimate: 8
Assigned: Likun
Status: Complete

Recursor Cache: Requirements - Review
Assigned:
Status: Complete
(Much review has taken place on the bind10-dev mailing list; a review from a BIND-9 developer is outstanding. However, for the purposes of this sprint, the task is marked as complete - work can begin on the next stage.)

Recursor Cache: API Design
Design of the API into the cache.
Estimate: 5
Assigned:
Status:

Recursor Cache: API Design - Review
Assigned:
Status:

Recursor Cache: Test Code
Writing tests for the cache code.
Estimate: 8
Assigned:
Status:

Recursor Cache: Test Code - Review
Assigned:
Status:

Recursor Logic

Outline design for processing logic
Produce a design for the processing (primarily based on section 7 of RFC 1035 but also including anything from other relevant RFCs). This does not include DNSSEC processing.
Estimate: 0
Assigned:
Status: Task Withdrawn
(A fair bit of this work has already been done - see here - and on examination it was felt that no further work was needed on this aspect of the recursor. For this reason the task was withdrawn and it does not appear in the sprint velocity calculation.)

Logging

#421: Logging: Requirements
Drawing up the requirements for BIND-10 logging.
Estimate: 3
Assigned: Stephen
Status: Completed

#421: Logging: Requirements - Review
Assigned: <all>
Status: Completed

Logging: API Design
API design for BIND-10 logging. Although it is likely that the logging will be implemented using an existing logging framework, a level of abstraction will make it easier to change the implementation if desired.
Estimate: 5
Assigned: Stephen
Status:

Logging: API Design - Review
Assigned:
Status:

Logging: Test Code
Writing tests for the logging code.
Estimate: 5
Assigned:
Status:

Logging: Test Code - Review
Assigned:
Status:

Outstanding Bugs

#85: Test case of "./DS query
Bug was fixed, needs a unit test.
Estimate: 1
Assigned: vorner
Status: Complete

#85: Test case of "./DS query - Review
Assigned:
Status: Complete

#202: cfgmgr and bindctl and unknown configurations
Needs to complain about unknown configuration.
Estimate: 1
Assigned: Jelte
Status: Complete

#202: cfgmgr and bindctl and unknown configurations - Review
Assigned: Likun
Status: Complete

#226: msgq and distcheck and read-only socket directory
Estimate: 1
Assigned: Jeremy
Status:

#226: msgq and distcheck and read-only socket directory - Review
Assigned:
Status:

#229: If b10-auth cores, bind10 doesn't say so and keeps restarting
bind10 should report the exit status of the dead child.
Estimate: 1
Assigned: Stephen
Status: Complete

#229: If b10-auth cores, bind10 doesn't say so and keeps restarting - Review
Assigned: Jelte
Status: Complete

#126: xfrout hang
Maybe already fixed? 8 months old. (Was a timeout interface added?)
Estimate: 1
Assigned:-
Status: 'Done'; Was indeed already fixed when we added timeouts in msgq API

#126: xfrout hang - Review
Assigned:
Status: Not required

Summary

Task Description Estimate Complete
Refactoring: put in library for DNS services 5
#327 Review of All Tasks related to #327 5 yes
#327 Merge #327 back into trunk 1
Demux: design phase 1 3
Demux: design phase 2 5
#408 General Control Logic/Logic? to Handle NS and A Queries 3 yes
#356 Logic to update RTT/Address Selection Logic/RTT Banding 2 yes
#405 Add basic support for addressing individual list items 3 yes
#384 Fix bindctl printing of config data 5
Recursor Cache: Requirements 8 yes
Recursor Cache: API Design 5
Recursor Cache: Test Code 8
#421 Logging: Requirements 3
Logging: API Design 5
Logging: Test Code 5
#85 Test case of "./DS query 1 yes
#202 cfgmgr and bindctl and unknown configurations 1 yes
#226 msgq and distcheck and read-only socket directory 1
#229 If b10-auth cores, bind10 doesn't say so and keeps restarting 1 yes
#126 xfrout hang 1 yes
Estimate points completed 25
Last modified 7 years ago Last modified on Dec 14, 2010, 5:10:41 PM