On Monday 14 June 2021 at 20:31:53, Parth Patel wrote:
> Hi All,
>
> Let's say we have 500 network devices
I'm sure there are people here who would not describe that as "massive" :)
> and we use ansible or nornir.
> If we deploy it from let's say single configuration management server that
> single would be single point of failure
Keep a mirror of your ansible server and its configuration. Either machine can
then perform updates and installations. There's no reason ansible and its
configuration needs to exist on only one machine.
> or let's say single point of security hit ?
Your ansible server should not be exposed to access from the Internet.
Your ansible server needs to connect to your managed servers, but it does not
need to be reachable by any external system.
> What are other strategy to manage such scenario such as doing regular
> backup of devices and storing running config in some sort of storage ?
Taking backups of devices which are managed / installed by ansible is probably
a good idea, but is entirely outside the scope of what ansible needs to do
(other than perhaps install the backup system).
As for "storing running config", that depends very much on what your managed
servers are doing, and how you would intend to recover if one went down, got
corrupted, caught fire, or became unreachable.
Ansible is a configuration management system. Backups and high availability
are separate topics with separate tools.
Antony.
--
In Heaven, the beer is Belgian, the chefs are Italian, the supermarkets are
British, the mechanics are German, the lovers are French, the entertainment is
American, and everything is organised by the Swiss.
In Hell, the beer is American, the chefs are British, the supermarkets are
German, the mechanics are French, the lovers are Swiss, the entertainment is
Belgian, and everything is organised by the Italians.
Please reply to the list;
please *don't* CC me.