BIND 10 #2025: system test for notify
BIND 10 Development
do-not-reply at isc.org
Tue Jun 26 09:50:33 UTC 2012
#2025: system test for notify
-------------------------------------+-------------------------------------
Reporter: | Owner: muks
jinmei | Status: reviewing
Type: task | Milestone:
Priority: high | Sprint-20120703
Component: xfrin | Resolution:
Keywords: | Sensitive: 0
Defect Severity: N/A | Sub-Project: DNS
Feature Depending on Ticket: | Estimated Difficulty: 5
Add Hours to Ticket: 0 | Total Hours: 0
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => muks
Comment:
Hello
Replying to [comment:10 muks]:
> > The `test_notify_slaves` ‒ I don't like the idea of having „test“
options in the configuration. Also, what is the difference between this
and the `also_notify` configuration we plan to have?
>
> "test_" is in the key because it is only meant to be used in testing.
>
> On the difference between this and `also_notify`, I don't know what
`also_notify` is supposed to do. But `test_notify_slaves` is a list of
slave addresses which get sent NOTIFYs by Xfrout. It is necessary for
having this test run under lettuce right now. If `also_notify` is
implemented in the future, we can revisit this test
Well, I understand the reason and the meaning of the configuration
variable. And that is exactly what I don't like ‒ having user-facing
configuration that should not be used.
The `also_notify` is something a user might want to use when they need to
send notifies to addresses not listed in the NS records. It seems to me
this is exactly the same feature. So I propose to rename it to also-
notify, make a note about it to #1992 and put it to next-sprint-proposed
to add tests for it. Would that be OK with you?
> This is the `inmemory_over_sqlite3.feature` ? Strange that it passed for
me here! In any case I have made the changes that jinmei suggested about
address config so it all runs in IPv6.
It passed now.
--
Ticket URL: <http://bind10.isc.org/ticket/2025#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list