[ClusterLabs] Passing and binding to virtual IP in my service

[Nikhil Utane]

Of course, one way is to pass the same virtual IP configuration to my
resource agent:
"<nvpair id="ClusterIP-instance_attributes-ip" name="ip"
value="10.206.1.253"/>"
But this will be duplicate information and error-prone.
There ought to be a better way. :)

On Thu, Jan 7, 2016 at 2:58 PM, Nikhil Utane <nikhil.subscribed at gmail.com>
wrote:

> Hi,
>
> I have my cluster up and running just fine. I have a dummy service that
> sends UDP packets out to another host.
>
>  Resource Group: MyGroup
>      ClusterIP  (ocf::heartbeat:IPaddr2):       Started node1
>      UDPSend    (ocf::nikhil:UDPSend):  Started node1
>
> If I ping to the virtual IP from outside, the response goes via virtual IP.
> But if I initiate ping from node1, then it takes the actual (non-virtual
> IP). This is expected since I am not binding to the vip. (ping -I vip works
> fine).
> So my question is, how to pass the virtual IP to my UDPSend OCF agent so
> that it can then bind to the vip? This will ensure that all messages
> initiated by my UDPSend goes from vip.
>
> Out of curiosity, where is this virtual IP stored in the kernel?
> I expected to see a secondary interface ( for e.g. eth0:1) with the vip
> but it isn't there.
>
> -Thanks
> Nikhil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160107/a013e849/attachment-0003.html>