Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Implement load balancing OpenStack queue #1

Closed
mzur opened this issue Oct 8, 2018 · 5 comments
Closed

Implement load balancing OpenStack queue #1

mzur opened this issue Oct 8, 2018 · 5 comments

Comments

@mzur
Copy link
Member

mzur commented Oct 8, 2018

The OpenStack queue (as described here) could have basic load balancing capabilities. This means that, if an OpenStack compute instance running the BIIGLE GPU server is currently busy, the queue boots up another (up to n) compute instance and submits new jobs round robin to all available instances. Each instance is deleted again if it is idle for a while.

@mzur mzur changed the title Implement load balancing for the OpenStack adapter Implement load balancing OpenStack queue Oct 12, 2018
@mzur
Copy link
Member Author

mzur commented Oct 12, 2018

This should be an extension of the biigle/laravel-remote-queue package, called biigle/remote-queue-openstack.

@mzur
Copy link
Member Author

mzur commented Nov 23, 2018

Maybe do not boot up and delete instances. Instead, use existing instances and suspend/resume them as needed. This should be faster and much easier to configure as the machines don't need any provisioning scripts or some such. Suspending instances seems to free up resources, too, which is what we want here.

However, we might need to extend php-opencloud/openstack to support this.

@mzur
Copy link
Member Author

mzur commented Dec 17, 2018

I implemented biigle/laravel-cached-openstack which makes it possible to share cached authentication tokens between different packages (e.g. biigle/laravel-image-cache). The OpenStack queue should use this package, too.

@mzur
Copy link
Member Author

mzur commented Dec 18, 2018

I opened php-opencloud/openstack#271 which implements resuming and suspending of instances.

@mzur
Copy link
Member Author

mzur commented Jan 22, 2019

This won't be implemented for now. The php-opencloud repo seems to be inactive and we wouldn't have a huge benefit with automatically suspending/resuming instances (as nobody has complained about us blocking GPUs so far).

@mzur mzur closed this as completed Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant