Skip to content

Conversation

hajapy
Copy link
Contributor

@hajapy hajapy commented Dec 1, 2021

When AWS is unable to provide an instance in a given availability zone, this action can fail repeatedly (if the condition preventing AWS from having available instances persists). This happens particularly with gpu instance types.

By adding support for multiple subnet ids as input, we can configure the action to try multiple subnets and hence availability zones, giving us a better chance of finding a zone with available instances.

@philschmid
Copy link

Would be very appreciated to add! Would love this feature as well!

@jpalomaki
Copy link
Contributor

jpalomaki commented Jan 7, 2022

@hajapy Have you looked into using AWS Fleet API instead of current RunInstances? From what I can tell, Fleet API could also help with #82?

@hajapy
Copy link
Contributor Author

hajapy commented Jan 8, 2022

@hajapy Have you looked into using AWS Fleet API instead of current RunInstances? From what I can tell, Fleet API could also help with #82?

@jpalomaki Interesting, no I hadn't considered that, but it seems like it would be a more elegant solution to this and other issues (also providing options for Spot instances, or mixed spot/on-demand). I don't have capacity to work on this, but it is a nice idea.

brandboat added a commit to Canner/github-runner that referenced this pull request Mar 14, 2022
brandboat added a commit to Canner/github-runner that referenced this pull request Mar 14, 2022
brandboat added a commit to Canner/github-runner that referenced this pull request Mar 14, 2022
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

Successfully merging this pull request may close these issues.

3 participants