Simplify and update Cirun.io config to use labels

[aktech]

See https://docs.cirun.io/reference/examples.html
Announcement here: https://twitter.com/AktechLabs/status/1551820040408006661

Now a single config can be used by multiple workflows using labels.

[hodgestar]

Thanks, @aktech! Looks good to me. I've triggered the workflow runs just to double check that things are working.

[aktech]

Hey @hodgestar seems like your vCPU limit is 0 in that region.

[hodgestar]

Hey @hodgestar seems like your vCPU limit is 0 in that region.

It worked in the past, so I don't know what happened. I will check a bit later. :/

[aktech]

Quota might have been reset I guess (due to non-usage probably):
https://github.com/qutip/qutip-cupy/pull/44/checks?check_run_id=7558192541

An error occurred (VcpuLimitExceeded) when calling the RunInstances operation: You have requested more
vCPU capacity than your current vCPU limit of 0 allows for the instance bucket that the specified instance type belongs to. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit."

[hodgestar]

The account still has All G and VT Spot Instance Requests set to 64 so I'm still confused.

[hodgestar]

Maybe removing instance_type: g4dn.xlarge from the config broke something?

[aktech]

The account still has All G and VT Spot Instance Requests set to 64 so I'm still confused.

That's for spot instance, since we have set preemptible: false, we're not using spot. I can set it to true in that case.

Maybe removing instance_type: g4dn.xlarge from the config broke something?

Where have we removed that? It's still there isn't it?

[aktech]

This time the AWS credentials didn't had permissions:

{
    "error": "An error occurred (AuthFailure.ServiceLinkedRoleCreationNotPermitted) when calling the RequestSpotInstances operation: The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances."
}

Ref: https://github.com/qutip/qutip-cupy/pull/44/checks?check_run_id=7600656032