BIND 10 #565: Boss should start/stop b10-auth and b10-recurse without restart
BIND 10 Development
do-not-reply at isc.org
Mon Feb 14 17:44:41 UTC 2011
#565: Boss should start/stop b10-auth and b10-recurse without restart
-------------------------------------+-------------------------------------
Reporter: vorner | Owner: UnAssigned
Type: defect | Status: reviewing
Priority: major | Milestone: A-Team-
Component: Boss of | Sprint-20110223
BIND | Resolution:
Keywords: | Sensitive: 0
Estimated Number of Hours: 0.0 | Add Hours to Ticket: 0
Billable?: 1 | Total Hours: 0
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
I think it is ready for review.
However, I'd like to note few things. For one, I believe we will need to
have more flexible boss (with list of subsystems to have running, it isn't
possible not to start stats for example, or start auth without xfrout),
therefore this is kind of short to middle term solution.
Another one is, there are no tests for part of it - the part that shuts
down or starts the processes. I added only little bit of it, and I would
need to create a whole testing framework for it (to tests respawns,
starts, stops, etc). It seems an overkill for this task right now (because
this is a nice feature that the users might notice, so I want it to get to
the Y2 release). I'll create another ticket for it and put it to the A
team backlog, where I describe some ideas about how the boss could be
generalized and tested.
I propose this changelog entry:
{{{
[bug] vorner
It is possible to start and stop resolver and authoritative server without
restart of the whole system. Change of the configuration (Boss/start_auth
and Boss/start_resolver) is enough.
}}}
--
Ticket URL: <https://bind10.isc.org/ticket/565#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list