Opened 8 years ago

Closed 8 years ago

#1787 closed task (fixed)

update in-memory zone after xfrin

Reported by: jinmei Owned by:
Priority: medium Milestone: Sprint-20120515
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: xfr for in-memory
Estimated Difficulty: meta Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by jinmei)

Currently only the SQLite3 data source can be updated via incoming xfr.
We can extend this to in-memory with some extensions to b10-auth,
b10-xfrin, and the in-memory data source implementations. I propose
this feature for the end of y3 release. For the limited period of
development, it'd have to be a kind of hack, assuming sqlite3 only,

This is a meta ticket for that feature.

It consists of the following subtasks:

  • #1788 update auth spec to specify in-memory "filetype" with sqlite3 backend
  • #1789 update xfrin to maintain in-memory/sqlite3 zones
  • #1790 update xfrin to have auth reload transfered zones
  • #1791 update InMemoryZoneFinder::load() to support sqlite3 backend
  • #1792 update b10-auth config handler to support in-memory/sqlite3
  • #1793 update b10-auth command handler to reload in-memory/sqlite3
  • (#1794 add a lettuce test for "updating in-memory after xfr" feature)
  • (#1911 document how to configure in-memory data source with sqlite3 backend)

Note: this is a meta ticket and doesn't have to have an estimation.


Change History (6)

comment:1 Changed 8 years ago by jinmei

  • Description modified (diff)
  • Feature Depending on Ticket set to xfr for in-memory

comment:2 Changed 8 years ago by jinmei

  • Description modified (diff)

comment:3 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to meta

comment:4 Changed 8 years ago by jelte

  • Milestone changed from Year 3 Task Backlog to Sprint-20120417

comment:5 Changed 8 years ago by jinmei

  • Description modified (diff)

comment:6 Changed 8 years ago by muks

  • Resolution set to fixed
  • Status changed from new to closed

This ticket is now done as all its children are done.

Note: See TracTickets for help on using tickets.