Description

What problem are you trying to solve?

I currently have 1 x windows and 1 x linux EC2NodeClass. In each of these you specify a disk size, which currently has to be big enough to handle the biggest possible node size. The smaller nodes are therefore wasteful as pointed out in our most recent AWS client review.

We have done a number of PoC's with some commercial offerings out there - I wont name them... but they have the ability to specify disk size based on a calculation of the number of CPUs in the node.

E.g

10G x number of CPUs = 20G (where CPU = 2)

Sure you can start creating multiple EC2NodeClasses labelled -small -medium -large, but this would be the only reason I'd be cluttering up the config, and it would still be a manual mishmash of what someone thinks is best.

How important is this feature to you?

It would just be really neat to be able to specify in some way a formula for the size.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment