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

Boost regional analyses #192

Closed
ansoncfit opened this issue Nov 29, 2018 · 3 comments
Closed

Boost regional analyses #192

ansoncfit opened this issue Nov 29, 2018 · 3 comments
Assignees
Labels

Comments

@ansoncfit
Copy link
Member

With #191 and related changes (e.g. per-second EC2 billing), it should now be fairly safe to allow end users to launch spot instances.

In the UI, maybe this would be a 🚀 to the left of the regional analysis status update bar? We could start with a low limit (e.g. 20) on user-requested spot instances.

We could also consider starting multiple workers automatically when a regional analysis is launched.

@ansoncfit ansoncfit self-assigned this Dec 16, 2018
@ansoncfit
Copy link
Member Author

ansoncfit commented Dec 16, 2018

As part of this task, I'm refactoring much of the EC2-specific code out of Broker. I plan to use EC2Fleet to take advantage of a single interface for both spot and on-demand instance requests. I'm also considering having the regional analysis controller launch ~50 spot instances after a few tasks have successfully been completed on a regional analysis.

@ansoncfit
Copy link
Member Author

It appears that the launch template overrides for EC2 Fleet do not yet support user data, which we use to provide the worker startup script.

Currently, the only supported override is instance type.

So back to separate on-demand and spot requests.

@ansoncfit
Copy link
Member Author

Closed by #201, merged into master in #204

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

No branches or pull requests

1 participant