VIP Manager suggestions

[CS_DBA]

On 03/20/2014 10:51 AM, CS_DBA wrote:
>
> On 03/20/2014 07:37 AM, Mark Haney wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>>
>> On 03/20/14 09:26, CS_DBA wrote:
>>> A tool to manage the creation, assignment, shutdown, movement, etc
>>> of VIP's (or I.P. alliases)
>>>
>>>
>>>
>>> On 03/20/2014 05:31 AM, Patrick O'Callaghan wrote:
>>>> On Wed, 2014-03-19 at 21:31 -0600, CS_DBA wrote:
>>>>> Hi all;
>>>>>
>>>>> Anyone have any suggestions per Virtual I.P. managers?
>>>> OK, I'll bite. What's a Virtual I.P. manager?
>>>>
>>>> poc
>>>>
>> Well, the next question should be: Why?  Why would you need something
>> like that? What are you doing that requires that kind of setup that
>> DHCP wouldn't work better?
The applications can only write to one database at a time, only the 
master database is read/write. if the db fails and we need to promote 
the slave to the master then we don't want to mess with the apps but 
simply "move" the database IP they use so that IP now points to the new 
master




>>
>> - -- Mark Haney
>> Network/Systems Administrator
>> Practichem
>> W: (919) 714-8428
>> Fedora release 20 (Heisenbug) 3.13.6-200.fc20.x86_64
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQEcBAEBAgAGBQJTKu8mAAoJEM/YzwEAv6e7gTIIAJatUkppaLVCGaPc86QJ6z8k
>> N5rpvBMug3dT7LRbBD0dQJZmzvS9ftAEOo37NbkKQYCKe/DkA95GDi36dzNh7n30
>> cOv1QXXOGpv8dIls3w74YN+nsTxLy1M0y0ELkojD4FLlOGDJAxQWzcmxnGp3IrB+
>> 9RrcKLuYfAxmLpRPsrwZZkkWC9+ZEivHl+nlnsnwXDnf+twvzCS6qUdYeeFUqyu6
>> BUbatUO/3MllKETkf/EXyKzuJFd0N6ki/5PLmkfVTSlM1j/+N8Ik4/uSO/cVmN+C
>> Yy3zJJ03ExwHna3JCMKbYIRSr1Ee6L+CkKq1JvMb2Q/XG829OFMk124I5M6Qh+Y=
>> =hGRj
>> -----END PGP SIGNATURE-----
>
> So we're looking at database failover, application connections to the 
> db are via I.P.'s (or aliases) we can of course use ifconfig and 
> create/destroy aliases and thus "move" the IP aliases at failover 
> time, however I would like to leverage a tool so the IP alias move can 
> be both seamless and executable via command(s) on a single server.
>
> With ifconfig aliases we need to do the following in the failover script:
> - execute the ifdown  on the old / failed master server (probably via 
> commands over ssh)
> - validate that the ip alias came down
> - execute the ifup of the alias on the slave (going to be the new 
> master shortly)
> - verify that it came up
> - then finish the db failover
>
>
> It would be keen if I could execute a single command like we do with 
> amazon elastic ip's or RackSpace virtual ip's...
>
> Thoughts?
>
>
>