wiki:RTeam20101102

R-Team Sprint

Start: 2 November 2010
End: 16 November 2010

In the R-Team sprint planning meeting on 2 November 2010 (minutes), it was agreed that since many of the team are out at conferences in the next couple of weeks, no new tasks would be introduced. Instead, the sprint would include unfinished tasks from the last sprint, and outstanding review tasks.

In addition, it was agreed that the list of tasks would be placed in the Wiki (this page) and that people would assign themselves to work by editing the Wiki and adding their name alongside the appropriate task.

Tasks remaining from Sprint ending 2 November 2010

Refactoring: put in library for DNS services
See Ticket #327
Estimate: 5 days
Assigned:
Status:

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

Refactoring authoritative and recursive tests
This involves moving common tests into a single file for use by both. (See Ticket #327. The task was seperated to ticket #402.)
Estimate: 1 day
Assigned: Likun
Status: Complete

Refactoring authoritative and recursive tests - Review
Assigned:
Status:

Review of All Tasks
This involves a broad review of the changes made to ticket #327 before it is merged back into trunk.
Estimate: 1 day
Assigned:
Status:

Configuration to determine whether to run authoritative or recursive server
Estimate: 3 days
Assigned:
Status:

Configuration to determine whether to run authoritative or recursive server - Review
Assigned:
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: 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
This is the framework of the processing described in NameserverAddressStoreDesign
Estimate: 2.5
Assigned: vorner
Status:

General Control Logic - Review
Assigned:
Status:

Logic to Handle NS and A Queries
Part of the processing described in NameserverAddressStoreDesign that actually issues the queries and, when the queries return, updates the data structures and handles the post-processing.
Esimtate: 5
Assigned:
Status:

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: Minor changes needed as result of review

Logic to update RTT - Review
Assigned: Stephen
Status: Complete

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:
Status:

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

Pre-Requistite Tasks

Discussed at the planning meeting, these are tasks that need doing in order that other tasks can proceed. All of these are based on ticket #384 where a problem was found in configuration structures.

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: Ready for review

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

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:

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:

Outstanding Reviews

Ticket #389: Configuration of b10-recurse through the config manager
Assigned: Jelte
Status: Complete

Ticket #393: Marking places where logging would happen
Assigned: Stephen
Status: Complete

Ticket #401: Timeouts in the recursor
Assigned: Stephen
Status: Complete

Last modified 7 years ago Last modified on Nov 26, 2010, 7:01:09 AM