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

Support Elastic Inference Accelerator for worker groups #1175

Closed
1 of 4 tasks
rucha3 opened this issue Jan 6, 2021 · 2 comments · Fixed by #1176
Closed
1 of 4 tasks

Support Elastic Inference Accelerator for worker groups #1175

rucha3 opened this issue Jan 6, 2021 · 2 comments · Fixed by #1176

Comments

@rucha3
Copy link
Contributor

rucha3 commented Jan 6, 2021

I have issues

I'm submitting a...

  • bug report
  • feature request
  • support request - read the FAQ first!
  • kudos, thank you, warm fuzzy

What is the current behavior?

Curently, there is no way to specify an accelerator with worker_groups_launch_template.

What's the expected behavior?

We should be able to add a field in worker_groups_launch_template for the accelerator type.

Environment details

  • Affected module version: v13.2.1
@stale
Copy link

stale bot commented Apr 6, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 6, 2021
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant