[ClusterLabs] About RA ocf:heartbeat:portblock

[Oyvind Albrigtsen]

Correct. That should block the port when the resource is stopped on a
node (e.g. if you have it grouped with the service you're using on the
port).

I would do some testing to ensure it works exactly as you expect. E.g.
you can telnet to the port, or you can run nc/socat on the port and
telnet to it from the node it blocks/unblocks. If it doesnt accept
the connection you know it's blocked.


Oyvind Albrigtsen

On 06/10/24 22:46 GMT, Murat Inal wrote:
>Hello,
>
>I'd like to confirm with you the mechanism of ocf:heartbeat:portblock.
>
>Given a resource definition;
>
>Resource: r41_LIO (class=ocf provider=heartbeat type=portblock)
>  Attributes: r41_LIO-instance_attributes
>    action=unblock
>    ip=10.1.8.194
>    portno=3260
>    protocol=tcp
>
>- If resource starts, TCP:3260 is UNBLOCKED.
>
>- If resource is stopped, TCP:3260 is BLOCKED.
>
>Is that correct? If action=block, it will run just the opposite, correct?
>
>To toggle a port, a single portblock resource is enough, correct?
>
>Thanks,
>
>_______________________________________________
>Manage your subscription:
>https://lists.clusterlabs.org/mailman/listinfo/users
>
>ClusterLabs home: https://www.clusterlabs.org/