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

RFE: openstack network load balancing #1517

Open
simzacks opened this issue Dec 4, 2019 · 3 comments
Open

RFE: openstack network load balancing #1517

simzacks opened this issue Dec 4, 2019 · 3 comments

Comments

@simzacks
Copy link

simzacks commented Dec 4, 2019

In OpenStack, we have multiple networks defined, each with its own range of IP addresses. However, often a single network becomes overloaded. We would like to be able to list multiple valid networks and have linchpin check which of those networks has the lowest usage and use that one for all the provisioning in the pinfile.

@samvarankashyap
Copy link
Collaborator

@simzacks
It looks like an interesting feature to implement.
Do you happen to have a script that does the above actions when given parameters? or any library which does that?
It would be helpful if you could point us to resources that are useful for the implementation.

@simzacks
Copy link
Author

simzacks commented Dec 4, 2019

A similar feature is being implemented in the OpenStack Cloud Plugin:
jenkinsci/openstack-cloud-plugin#279

That might be a good place to start. I've heard of another script in an older provisioner, but no one I spoke to knows what I'm talking about.

@olivergondza
Copy link

The java implementation in the PR @simzacks has mention might not serve the didactic purposes very well. Let me try to define what is desired:

  • User would like to specify not only which networks to connect to (which I presume is currently implemented), but even that particular NIC is supposed to be in one of the number of networks, but it does not matter which one. The user wish the network to be auto-selected based on the number of free fixed IP to increase the likelihood the provisioning will not be botched because of running out of IPs.

  • Implementation wise, there is an API endpoint to consult that reports the utilization of fixed IPs to base the decision on.

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

No branches or pull requests

4 participants