Opened 8 years ago

Closed 8 years ago

#1911 closed task (fixed)

document how to configure in-memory data source with sqlite3 backend

Reported by: jinmei Owned by: muks
Priority: medium Milestone: Sprint-20120515
Component: documentation 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: 3 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

...and about its implication for updating in-memory zone after inbound xfrs.

Subtickets

Change History (9)

comment:1 Changed 8 years ago by muks

  • Milestone changed from Next-Sprint-Proposed to Sprint-20120515

Move to current sprint as its parent #1787 is in.

An example to use when writing the documentation can be found in the lettuce tests.

comment:2 Changed 8 years ago by muks

  • Owner set to UnAssigned
  • Status changed from new to reviewing

Up for review.

comment:3 follow-up: Changed 8 years ago by jinmei

About "Incoming Transfers with In-memory Datasource":

The "incoming zone" in "In the case of an incoming zone" sounds
awkward, that is, what's "incoming zone"? Do you mean "incoming zone
transfer" (but then "which is served..." doesn't make much sense)? Or
maybe it should be "secondary zone"? I think this sentence should be
clarified.

I'd also clarify what the administrator should do (or doesn't have to)
if they want to serve a zone from in-memory for normal queries while
updating it by incoming zone transfers.

comment:4 Changed 8 years ago by jinmei

  • Owner changed from UnAssigned to muks

comment:5 in reply to: ↑ 3 ; follow-up: Changed 8 years ago by muks

  • Owner changed from muks to jinmei

Hi jinmei

Replying to jinmei:

About "Incoming Transfers with In-memory Datasource":

The "incoming zone" in "In the case of an incoming zone" sounds
awkward, that is, what's "incoming zone"? Do you mean "incoming zone
transfer" (but then "which is served..." doesn't make much sense)? Or
maybe it should be "secondary zone"? I think this sentence should be
clarified.

This text has been updated now.

I'd also clarify what the administrator should do (or doesn't have to)
if they want to serve a zone from in-memory for normal queries while
updating it by incoming zone transfers.

I don't follow this. Can you say what you want to see?

comment:6 in reply to: ↑ 5 ; follow-up: Changed 8 years ago by jinmei

Replying to muks:

The "incoming zone" in "In the case of an incoming zone" sounds
awkward, that is, what's "incoming zone"? Do you mean "incoming zone
transfer" (but then "which is served..." doesn't make much sense)? Or
maybe it should be "secondary zone"? I think this sentence should be
clarified.

This text has been updated now.

Okay, it's now clearer. A few more small points:

  • I'd replace "data source file" with "data source" because "data source" is a more abstract notion that a concrete "file"
  • Similarly, I'd simply say "backend" instead of "backend file".

I'd also clarify what the administrator should do (or doesn't have to)
if they want to serve a zone from in-memory for normal queries while
updating it by incoming zone transfers.

I don't follow this. Can you say what you want to see?

Something like this: "The administrator doesn't have to do anything
for b10-auth to serve the new version of zone except for the
configuration such as the one described in <reference to
in-memory-datasource-with-sqlite3-backend>".

But I'd leave it to you. Please feel free to merge with addressing
the above two points.

comment:7 Changed 8 years ago by jinmei

  • Owner changed from jinmei to muks

comment:8 in reply to: ↑ 6 Changed 8 years ago by muks

Replying to jinmei:

Replying to muks:

The "incoming zone" in "In the case of an incoming zone" sounds
awkward, that is, what's "incoming zone"? Do you mean "incoming zone
transfer" (but then "which is served..." doesn't make much sense)? Or
maybe it should be "secondary zone"? I think this sentence should be
clarified.

This text has been updated now.

Okay, it's now clearer. A few more small points:

  • I'd replace "data source file" with "data source" because "data source" is a more abstract notion that a concrete "file"
  • Similarly, I'd simply say "backend" instead of "backend file".

Done. :)

I'd also clarify what the administrator should do (or doesn't have to)
if they want to serve a zone from in-memory for normal queries while
updating it by incoming zone transfers.

I don't follow this. Can you say what you want to see?

Something like this: "The administrator doesn't have to do anything
for b10-auth to serve the new version of zone except for the
configuration such as the one described in <reference to
in-memory-datasource-with-sqlite3-backend>".

Added. :)

comment:9 Changed 8 years ago by muks

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

Pushed to master:

* ce461b1 [master] Regen HTML and text versions of the guide
* e876441 [1911] Add paragraph about what the admin needs to do to serve new versions of zones
* dd75179 [1911] Make more minor text updates from review
* 3bed90a [1911] Clarify text about incoming zone transfers
* bc9d78d [1911] Update guide on how to configure in-mem datasource with sqlite3 backend

Resolving as fixed. Thank you for the review.

Note: See TracTickets for help on using tickets.