Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable LBaaS neutron plugin #680

Open
larsks opened this issue Dec 20, 2024 · 2 comments
Open

Enable LBaaS neutron plugin #680

larsks opened this issue Dec 20, 2024 · 2 comments

Comments

@larsks
Copy link
Member

larsks commented Dec 20, 2024

We could really use a load balancer in ESI. To expose openshift nodeport services via the existing "floating ip port forwarding" mechanism, we are only able to forward to a single worker node. If this node goes offline, we lose access to all our services (which would probably render all hosted clusters unusable). A load balancer would allow us to forward that traffic to "all worker nodes" (or a subset thereof), so that we can offer a more robust service.

LBaaS docs

@tzumainn
Copy link
Contributor

It looks like the LBaaS plugin was deprecated in RHOS (https://docs.redhat.com/en/documentation/red_hat_openstack_platform/13/html/networking_guide/sec-lbaas#network-lbaas-topo); the replacement is Octavia, a full-fledged service which I'd be reluctant to deploy on current ESI. I think it may still be possible to enable the LBaaS plugin, but I don't know how supported it will be.

A question though - shouldn't this sort of failover handled in the OpenShift architecture? If we move towards the ACM/baremetal-operator model, I don't think we'd be able to take care of this use case in OpenStack.

@larsks
Copy link
Member Author

larsks commented Dec 20, 2024

It looks like the LBaaS plugin was deprecated in RHOS

Yeah, I was just reading about that.

A question though - shouldn't this sort of failover [be] handled in the OpenShift architecture?

Load balancers at the network layer are an extremely common bit of infrastructure -- we're making use of them for effectively all of our public-facing openshift clusters. Having something like this available in ESI would be incredibly useful, and not just for OpenShift.

It's possible to solve this in OpenShift instead, but having this feature at the network layer is substantially simpler.

It's unfortunate that Octavia seems to have a fairly weighty set of requirements (it appears to requires both Nova and Barbican, for example).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants