2 Mar
2016
2 Mar
'16
9:24 p.m.
I agree I would and do use automation tools like chef and puppet for that very reason.
My original post did leave a fairly important potential benefit to native HTTP loading of
config though, that is you could dynamically generate config in a webapp which the mooted
5.0 runtime routing reloading could really take advantage of.
-----Original Message-----
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Tristan Mahé
Sent: 02 March 2016 18:15
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Kamailio 5.0 - HTTP loading of config files
Chef, Ansible, Puppet, and others, their job is exactly that, ensuring that nodes are
configured accordingly, also ensuring that any operation needed for that configuration
change is applied ( reloading dispatcher in case of new config, restarting kamailio in
case the whole config file changed, ... ).
Maybe better to use those dedicated tool rather than working to reinvent the wheel ?
My 2 cents...
On 03/02/2016 09:38 AM, Daniel Tryba wrote:
On Wed, Mar 02, 2016 at 05:10:15PM +0000, Tim Chubb
wrote:
As a suggestion for 5.0 being able to load config
files from a URL,
with any includes being taken relative to the URL would be a really
handy feature. It would allow a central source for config files in a
cluster and make it a much simpler process to push out changes to
routing to all nodes.
This problem has been solved by the many configuration
management
tools readily available.
And no I can't give you a suggestion since I use my own manual way to
upgrade from a central repos (a test server) that simply scps the
config to the active nodes, includes load the per server specific
parts from the filesystem.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users