reply: [Opendnssec-develop] 2.0 - zonelist.xml

[wangguodong]

If we remove the zonelist configuration file, there may be some disadvantages:

1. It's not very friendly for the users because it's inconsistent for the configuration. some from the files, and some from database.
  
2. No obvious convenience.
Now we update the zonelist file then execute the update command.
After changed, we should export -> edit -> import, may be more steps.

If we base on the database not the configuration files, the configuration based on web may be more friendly for users.


Besides, 
The communication method between enforcer and signer is not very good for thousands of zones scenes.
Because there are so many files. If there are more than one thounsand files under a file, the OS's search speed would slow down.
 
Jakob mentioned that we can use a shared database may be a nice choice.
We can added some new tables that record the information signconf contains.

-----邮件原件-----
发件人: opendnssec-develop-bounces at lists.opendnssec.org [mailto:opendnssec-develop-bounces at lists.opendnssec.org] 代表 Jerry Lundstr?m
发送时间: 2013年9月12日 16:15
收件人: Siôn Lloyd
抄送: opendnssec-develop at lists.opendnssec.org
主题: Re: [Opendnssec-develop] 2.0 - zonelist.xml

On 12 sep 2013, at 10:08, "Siôn Lloyd" <sion at nominet.org.uk> wrote:

> One file per zone could work

We need to think more about this.

There are limits to the number of files in a single directory for about half of the filesystems and the most common one (ext*).

> we could add the config information that the signer needs for the 
> adapters, etc. to the signconf files.

Yes, we should add all nessesary configuration for a zone in the same space.

/Jerry
_______________________________________________
Opendnssec-develop mailing list
Opendnssec-develop at lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop