BIND 10 #99: bindctl will allow options for modules that aren't running
BIND 10 Development
do-not-reply at isc.org
Thu Aug 5 01:35:37 UTC 2010
#99: bindctl will allow options for modules that aren't running
---------------------------+------------------------------------------------
Reporter: jreed | Owner: zhanglikun
Type: defect | Status: assigned
Priority: major | Milestone: 05. 3rd Incremental Release: Serious Secondary
Component: bind-ctl | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: 0.0 | Hours:
Billable: 0 | Totalhours:
Internal: 0 |
---------------------------+------------------------------------------------
Comment(by zhanglikun):
How you plan to let it return an error? since configmanager or cmdctl
doesn't know it now.
BTW, I have some comments about the operation for configuration.
1. For the low-level configuration item, maybe it's not easy to config it
by bindctl, like I want to change one port of the master, the commmand
will like "config set xfrin/masters[2]/port 53", I don't know whether we
will provide lower level config items.
'''
{
module_name: 'xfrin':
[
{
masters: [
{ 'ip':1.1.1.1, 'port':53 }
{ 'ip':2.2.2.2, 'port':12345 }
{ 'ip':3.3.3.3, 'port':12345 }
]
}
]
}
'''
2. I am not sure whether the 'static' configuration APIs can handle the
"big" configuration operation, like I want to set several 'masters' for
more than one zone, I had thought it can be down through bindctl, but it
really frustrating, because I have to 'config set master 1.1.1.1, then
config commit" again and again. It's better let user to write the
configuration in one file, then load it to config manager. (We talked it
in beijing f2f meeting.)
--
Ticket URL: <http://bind10.isc.org/ticket/99#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list