floating_ip on local net

[rjams]

Is it possible to use your ocf-resource script on local networks ?
At Hetzner Cloud you can have local networks to connect cloud instances, but floating actualy works only on official ips.
Thanks in advance

[svensp]

I don't see why not.

However I believe the concept ot Networks and Floating IPs don't intersect.

• A (Cloud) Network is pretty much a VPN on virtual hardware level
• The Floating IP resource is a (public) ip address you buy from Hetzner and use their WebUI, the API or this Agent(which uses the API) to point to one of your servers.

So you can create public 'ingress' servers with a public floating ip, then use a load balancer to route to your other servers by talking to them via their Cloud Network ip address rather than their 'public' server address.

However if you question is: can you create a private Floating IP address inside a Cloud Network with it then I believe the answer is no. Not because of the agent but because the Floating IP Cloud Resource can't be used that way.

[rjams]

At Hetzner Cloud you can use networks to create your own local subnet to locally connect some Cloud Instances.
Your floating_ip Resource Agent doesnt work on network because it use a different set of API-calls.

# add/change alias ip
curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer <api access code>" \
	-d '{"network": <network-id>, "alias_ips": ["10.0.0.14"]}' \
 "https://api.hetzner.cloud/v1/servers/<server-id>/actions/change_alias_ips"

# delete alias ip
curl -X POST -H "Content-Type: application/json" \
	-H "Authorization: Bearer <api access code>" \
	-d '{"network": <network-id>, "alias_ips": []}' \
 "https://api.hetzner.cloud/v1/servers/<server-id>/actions/change_alias_ips"

In combination with Resource Agent "IPaddr2" you can have a floating ip on a local network.
Does this sound interesting for you to implement ?

[svensp]

I won't have a use for this personally because I have moved from managing my resources with Pacemaker to Kubernetes CSI/FIP-Operator.
But I'll investigate how easy it is to adapt the existing agents for this use case. However I can't promise how soon I'll get around to do this as I'm rather swamped with other stuff to do.

[svensp]

Small update here.

The bad news:

• The python library I used is now deprecated and does not support alias ips
• alias ips are not actual api objects so 'attaching' an ip is actually getting the pervious list of ips and setting the same list again plus the one you want to add. This could be prone to race conditions.

The good news:

• there is a newer python library which supports this. And since the agents are technically independant executables it's possible to only write the new agent with the new lib

I'll try to write an agent but as of now no eta on testing it from my side.