-
Notifications
You must be signed in to change notification settings - Fork 35
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
Create semantic interface for Load Balancers (Local) #25
Comments
The local load balancer is a bit of a beast with three key components: the load balancer, load balancer groups, and the services within a group. I think a polished semantic with be particularly helpful to people here. Whether we keep it all in one object or break it out is certainly up for debate... Load Balancer
Load Balancer GroupYou can always have alternative incoming/destination port mappings which form unique services, but most calls can probably default/assume the destination port is the as the LB group port (treat it as an optional parameter that defaults to the group's port)
Utility
Necessary Services
|
Hi there, do you have any plans to implement this? Have recently moved a bunch of servers / load balancers to Softlayer from another hosting company & it would be super useful to be able to access this from https://github.com/softlayer/knife-softlayer |
P.S. The subset of functionality we're most interested in would be
|
There are no definite plans to implement this interface. Work on the Ruby client is done on a volunteer basis (we don't have any engineering resources dedicated to it). The original implementation plan was to take the functionality available through the Python language bindings and re-create it through the softlayer_api gem. I will make sure that your desire to see this implemented "sooner" is known. |
OT: Incidentally we recently released changes to the load balancer interface within the SoftLayer Control Portal. The changes were made to accommodate customers who felt the previous interface was difficult to navigate. If you have any feedback (positive or negative) about those changes we would be happy to receive that feedback through the email address portalfeedback in the softlayer.com domain. |
Interesting, yes, my colleagues found UI problems with the new system, which was what prompted me to research an automated solution, which brought me here. I'll tell them to send an email... |
No description provided.
The text was updated successfully, but these errors were encountered: