[ClusterLabs] Passing and binding to virtual IP in my service
kgronlund at suse.com
Thu Jan 7 05:09:18 EST 2016
Nikhil Utane <nikhil.subscribed at gmail.com> writes:
> Of course, one way is to pass the same virtual IP configuration to my
> resource agent:
> "<nvpair id="ClusterIP-instance_attributes-ip" name="ip"
> But this will be duplicate information and error-prone.
> There ought to be a better way. :)
You can use attribute references to avoid having to configure the same
value twice. It is documented here for the crmsh syntax:
> On Thu, Jan 7, 2016 at 2:58 PM, Nikhil Utane <nikhil.subscribed at gmail.com>
>> 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
>> 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.
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
// Kristoffer Grönlund
// kgronlund at suse.com
More information about the Users