If code push is your issue, make code push easier... In that I mean you don't have to push full code for twiddling something like the list of memcached's. Split the list of servers off into a seperate source file that's included, then give ops the ability to push those subsets of files quickly and easily. Don't have your app code pushes overwrite them either.
-Dormando On Wed, 7 Oct 2009, Edward M. Goldberg wrote: > > Yes, I use DNS Made Easy for this use: > > 1) Create an A Record for each Memcached server with the SAME name > memcached.domain.com > 2) Create an A Record for each Memcached server with a UNIQUE name > memcache.00.domain.com > > Then do: > > $ dig +short memcache.domain.com # This returns --> > 10.0.0.1 > 10.0.0.2 > 10.0.0.3 > ... > > This gets the list of Memcache servers by IP, You can also use the > "unique" names for DNS Access. > Or just use the Ip values as you like. > > As I add more server to "Scale-Up" the DIG command just returns more > addresses. So the idea scales. > > The A records as DNSMadeEasy can be updated with DDNS API calls. > > I like the performance, but have had issues with DNS performance. > I just wanted feedback as to other system level users do this "scale- > up" operation in production. > Pushing new code works for some users. But lacks a dynamic update for > OPs needs. > > Edward M. Goldberg > > http://myCloudWatcher.com/ >
