Jeremy Stretch

Re-opening this for review as it looks like we'll end up cutting a v3.7.8 release for some unrelated bug fixes.

@GSeiNet please edit your post above to detail specifically what functionality you're proposing be added.

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the...

But your use case > and would like to track the EC2 instance type specifically entails clusters. I think it's fair to require users who need to track VM types...

From the comments here, I think we're conflating two different functions of device types: 1. Indicating the device manufacturer and model. 2. Automatically populating components on newly-created devices. Re-purposed for...

@xorrkaz What I'm getting at is that e.g. the `t3.large` type is decoupled from the "VM with interfaces X, Y, and Z" definition: You'll very likely have different iterations of...

I'd suggest defining a [custom script](https://netbox.readthedocs.io/en/stable/additional-features/custom-scripts/) to provision VMs in that manner. That way, you're free to automatically provision interfaces, IP addresses, VLANs, and whatever else you may need.

I'd like to spend some more time digging into the two related but distinct use cases I cited [above](https://github.com/netbox-community/netbox/issues/5795#issuecomment-818987390), to ensure that whatever approach we take here doesn't preclude a...

We're going to punt on this for v3.4 as it doesn't seem quite fully baked yet. It might help to open a complementary FR to separate out the two discrete...

@tomasz-c please open a separate issue/discussion, as your comments are unrelated to this FR.