print cloud info in cluster status

[BelSasha]

Output will looks as follows:

Single-node GPU
AWS g5.xlarge cluster | 🌍 us-east-1 | 💰 $1.006/hr

Multi-node GPU
2x AWS g5.xlarge cluster | 🌍 us-east-1 | 💰 $1.006/hr

Single-node CPU
AWS m6i.xlarge cluster | 🌍 us-east-1 | :💸: $0.096/hr

Multi-node CPU
2x AWS m6i.xlarge cluster | 🌍 us-east-1 | :💸: $0.096/hr

[BelSasha]

• status cmd prints cluster name as hyperlink to den #1226
• status cli prints active funtions info #1224
• print cloud info in cluster status #1209 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BelSasha and the rest of your teammates on Graphite

[jlewitt1]

what about the cloud property necessitates this?

[BelSasha]

We could add a validation for the launched_properties in the status output, but i think it is more of a den test.
The point of test is to make sure that the cloud info is printed as expected to stdout.
@jlewitt1 is this what you were referencing to? Or something else?

[jlewitt1]

i meant what makes cloud differnt from the other properties, but seems like it's just bc of how Sky formats it?

[BelSasha]

yes, i think so. We could also double check it with Caroline.

[carolineechen]

you added this line cloud = cloud_properties.get("cloud").upper() in _print_cloud_properties. I think this might be in response to me adding the cloud = str(launched_resource.cloud).lower() in setting the launched properties cloud attribute?

In the sky status resource, they have the cloud capitalized (Kubernetes, AWS, GCP, Lambda, etc) but I thought it simpler to just use the lowercase form (since that's what we prefer/use in our examples anyways). I think we can leave it that way for printing out in status too? But if we want the original form then we should update the launched_properties attribute to that too. Since calling upper() doesn't work in every case

[BelSasha]

@carolineechen sounds good, I don't have strong opinion about that. If lower case is consistent with out examples, let's print the cloud in the status as lower case as well. :)