@peterschmidt85, please describe what's meant by the support for Capacity Blocks. Do you suggest dstack provides an interface to purchase reserved instances or do you suggest dstack should be able to launch instances in capacity blocks purchased by users?

Also note that testing EC2 Capacity Blocks for ML can be costly. The minimum reservation price is p4d.24xlarge for 1 day =. $14.75 * 24 = $354.

@peterschmidt85, please describe what's meant by the support for Capacity Blocks. Do you suggest dstack provides an interface to purchase reserved instances or do you suggest dstack should be able to launch instances in capacity blocks purchased by users?

@r4victor I think, we only need to add a way to specify the existing reservation ID. I believe this can be a field in YAML/Profile.

This issue is stale because it has been open for 30 days with no activity.

This issue is stale because it has been open for 30 days with no activity.

This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

This issue is stale because it has been open for 30 days with no activity.

Working on this.

@peterschmidt85 One question: this issue covers capacity blocks only, ignoring generic capacity reservations, correct?

Working on this.

@peterschmidt85 One question: this issue covers capacity blocks only, ignoring generic capacity reservations, correct?

@solovyevt This particular issue I suppose is about capacity blocks only - because as far as I understand they are commonly used for ML (https://aws.amazon.com/blogs/aws/announcing-amazon-ec2-capacity-blocks-for-ml-to-reserve-gpu-capacity-for-your-machine-learning-workloads/)