On Tue, Sep 24, 2024 at 7:24 PM John Thurston
wrote:
> I'm looking for your ideas. What works? What doesn't work?
>
> Are you leveraging your existing configuration management tools (e.g.
> Puppet, Ansible, Chef)?
>
For OARC's name servers (significantly simpler than yours, but once you're
talkin
Our 'special' zone definitions are less than 10kb (at the moment), so
the 64kb limit isn't an issue. And if it ever is, it can be broken up
into several 'included' .conf files.
The 255-character string limit isn't a problem with base64:
base64 -w 250 special.conf | sed 's/^/"/;s/$/"/' | tr -d
Are you leveraging your existing configuration management tools (e.g.
Puppet, Ansible, Chef)?
Ansible (my choice of poison) works well for this type of situation I find,
particularly because a lot of work can be done via Jinja templating. This
trivial example hopefully illustrates what I mean:
Thirty years ago, we had a pretty simple DNS configuration; a couple of
AIX servers configured as dual-purpose authorities and resolvers. Once
it was set, the configuration didn't change much. But when it did, with
two hosts, it was simple to rlogin to each and make similar mods to the
config o
4 matches
Mail list logo
