wiki:RTeam20101116

R-Team Sprint

Start: 16 November 2010
End: 30 November 2010

The focus of team is the BIND-10 caching resolver. This sprint is aimed at completing two components of that:

  • Dispatcher (basically Ticket #327)
  • Nameserver Address Store

In the R-Team sprint planning meeting on 16 November 2010 (minutes), it was agreed that no new tasks would be introduced. Instead, the sprint would include unfinished tasks from the last sprint, and outstanding review tasks.

Tasks

Refactoring: put in library for DNS services
See Ticket #327. 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 (i.e. extracting common code from the authoritative and recursive servers into a common library.)
Estimate: 5 days
Assigned:
Status:

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

Ticket #402: Refactoring authoritative and recursive tests
This involves moving common tests into a single file for use by both. (See Ticket #327.) There are some small changes to be made as a result of the last review. As Likun is on holiday for most of the sprint, Michal will make these changes.
Estimate: 1 day
Assigned: Michal
Status: Complete

Refactoring authoritative and recursive tests - Review
Assigned: jreed
Status: Complete

Merge tickets #393, #401 and #402 back into #327
These tickets are all branches off #327. They need to be merged back into it before the review can take place.
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: 2 days
Assigned:
Status:

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

Ticket #412: Configuration to determine whether to run authoritative or recursive server
Estimate: 3 days
Assigned: Stephen
Status: Merged into trunk, r3676

Ticket #412: Configuration to determine whether to run authoritative or recursive server - Review
Assigned: Michal
Status: Complete.

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: 1 day
Assigned: Evan
Status:

Demux: design phase 1 - Review
Assigned:
Status:

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

Demux: design phase 2 - Review
Assigned:
Status:

Ticket #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: 5
Assigned: Michal
Status:

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

Logic to update RTT
Definition of the data structures and processing required for the caller to update the RTT associated with nameserver addresses.
Estimate: 1
Assigned: Ocean
Status: Awaiting review

Logic to update RTT - Review
Assigned: Stephen
Status:

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: 5
Assigned: Ocean
Status:

Address Selection Logic/RTT Banding - Review
Assigned:
Status:

Ticket #403: Fix the "/" bug
When parsing data, for lists, the parser appends a "/" to the end of the name in the maps that contains the list.
Assigned: Jelte
Status: Complete

Ticket #403: Fix the "/" bug - Review
Assigned: vorner
Status: Complete

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).
Assigned: Jelte
Status: Awaiting review

Add basic support for addressing individual list items - Review
Assigned:
Status:

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.
Assigned: Jelte
Status:

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

Last modified 7 years ago Last modified on Nov 30, 2010, 3:36:11 PM