Provision instance in specific AWS zone

[martbert]

Hi,

CML looks very promising for allowing easy MLOps. I've been playing around with it and stumbled upon a small issue. Say I want to run a job on a p3.2xlarge (AWS) instance on AWS in the us-east-1 region. Turns out those instances are not available in all zones. Hence when the runner tries to provision the said type of instance in us-east-1c, it fails. Would it be possible to consider the support of zones?

Cheers!

[DavidGOrtega]

👋 @martbert
Yes we are actually contemplating it and actually there is another ticket regarding this.
Will be resolved soon. I will ping you.

[0x2b3bfa0]

@DavidGOrtega, can you please link to the issue this is a duplicate of?

What if we allow specifying both regions and availability zones using the region attribute in the provider? For example, cml runner --cloud-region=us-east-1c would always the us-east-1c availability zone.

When a native region string ends with a lowercase letter, we can extract both values and use them accordingly. Adding a availability-zone filter condition here should do the trick. The same goes for the task resource.

[dacbd]

I believe that #814 and #795 are related since the fix would involve the same chunk of code, I intended to get a PR for in around the weekend.