[VoiceOps] Centralized management for distributed Asterisk servers
Leandro Dardini
ldardini at gmail.com
Tue Jan 11 02:59:06 EST 2011
Add to the already posted good hints:
3. Use cfEngine http://www.cfengine.org/ or puppet (I prefer this last one)
http://www.puppetlabs.com/ to distribute configuration.
The good thing about cfEngine or puppet is you can manage not only asterisk
configuration, but all server configuration on all boxes. Mind the big
trouble in managing the configuration by hand when you need to change the
root password, add an ssh-key or install a new package on all boxes.
Leandro
2011/1/10 Mark R Lindsey <lindsey at e-c-group.com>
> Two decent options come to mind, depending on how you manage your
> configurations:
>
> 1. Regular rsync of the configurations from a central server.
>
> 2. Put the configuration in mysql, and use mysql replication from master to
> the slave sites. Each site would use the configuration in the local MySQL
> installation.
>
>
>
>
>
> mark at ecg.co | +1-229-316-0013 | http://ecg.co/lindsey
> *
> *
>
>
>
>
> On Jan 10, 2011, at 3:22 PM, Dawson, Robert wrote:
>
> I have a customer that wants to maintain a standalone asterisk server at
> each of roughly 20 sites with a centralized configuration engine. Something
> similar to what Fonality (I think?) used to offer. They simply will not go
> with a centralized/hosted solution. Anyone know of anything similar to this?
>
> Thanks,
> Rob
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110111/ab4498dc/attachment.html>
More information about the VoiceOps
mailing list