(You guys confirmed what I was thinking when I started the thread.. thank you all for your replies, they gave me a lot of confidence on DMQ and I'm already testing it out)
On Mon, Apr 30, 2018 at 9:06 AM, Alex Balashov <[email protected]> wrote: > On Mon, Apr 30, 2018 at 11:13:13AM +0200, Aleksandar Sosic wrote: > > > We have a scalable dockerized environment and it's difficult to > > configure DMQ having dynamic IPs, instances booting up and scaling > > down on demand. > > A DNS alias that resolves to multiple entries is a great way to do that: > > https://kamailio.org/docs/modules/5.1.x/modules/dmq. > html#dmq.p.notification_address > https://kamailio.org/docs/modules/5.1.x/modules/dmq. > html#dmq.p.multi_notify > > although it'd be great if DMQ could exclude the local host from those > notification peers automatically, so that one didn't have to set up > multiple, exclusionary DNS entries for specific instances. Who knows, > maybe it can. > > But in principle, such DNS records can be tied to the internal DNS > resolution of a container discovery mechanism, be it Docker's internal > mechanism or something more like Consul. > > -- Alex > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
