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.

Sign up for GitHub

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

Jump to bottom

What's the reason for nitro instance types not being supported? Specifically I'd like to use the p3dn.24xlarge instance type #64

Closed
nickwalton opened this issue Feb 6, 2020 · 2 comments
Closed

What's the reason for nitro instance types not being supported? Specifically I'd like to use the p3dn.24xlarge instance type #64

nickwalton opened this issue Feb 6, 2020 · 2 comments
Labels
enhancement

Comments

@nickwalton
Copy link

No description provided.

@apls777
Copy link
Collaborator

apls777 commented Feb 7, 2020

Nitro-based instances have different device names for attached EBS volumes (see Amazon EBS and NVMe on Linux Instances). Moreover, they say:

The block device driver can assign NVMe device names in a different order than you specified for the volumes in the block device mapping.

That means, it should be a smarter way to figure out which volume is which.

At the moment, a Nitro-based instance would fail to start if you attached any volume. So, for now, I decided to disable this functionality at all.

This was referenced Feb 7, 2020
Closed
Closed
@apls777 apls777 mentioned this issue Jun 27, 2020
Merged
@apls777 apls777 mentioned this issue Oct 25, 2020
Merged
@apls777
Copy link
Collaborator

apls777 commented Oct 25, 2020

Now Spotty supports Nitro-based instances.

@apls777 apls777 closed this as completed Oct 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@apls777 @nickwalton