[bind10-dev] Cisco-style configuration Re: config experiment

[Shane Kerr]

Francis,

On Wed, 2009-09-16 at 08:16 +0000, Francis Dupont wrote:
> Another point about config: we had hard discussions about the style of
> running config in AFTR/CGN. The choice was between the Cisco style with
> startup-config and running-config where the CLI modifies the
> running-config (*), and the anti-Cisco style where all changes are done
> in the config file and committed through a reload of the whole config (**).
> 
> As far as I can see the style in BIND 9 is anti-cisco but I don't know
> if you have a clear choice for BIND 10.

We do have a clear choice for BIND 10: Cisco style!

We go a bit further, and say there is no startup-config.

When the system stops, the running-config is already in secondary
storage somewhere. When it starts, the new copy uses that version.

Ideally we will have a transaction-based config setup, so you can make a
set of changes to configuration, confirm they parse and can be loaded by
the various components, then commit them. If things go bad a roll-back
can be done (actually applying an earlier version as a new version).

This is a HORRIBLE mismatch with the current BIND 9 style (anti-Cisco).
In the case administrators want to use BIND 9 configuration or really
can't get their head around the idea of the configuration being done
anywhere other than vi, we will offer a mode where the system zeros the
configuration on startup and reloads it from configuration files. In
this mode, most of the running-config will be READ ONLY. Just like it is
today. :)

--
Shane