Workloads to Location Mapping #49
Description
What task were you trying to complete?
I was writing a workload spec.
Describe the usability issue
I want to tell the workload what location to deploy to, but when I see what I can put in the placement section, the only thing I can put in there is a citycode.
The problem is that the citycode only refers to the datum side of things. I could have mulitple google cloud regions and want to refer to them even if I'm still using DFW for the Datum side of things.
Why was this confusing or difficult for you?
Apparently the system today looks through all currently defined locations and whatever Location comes back first with the city code I used in it, is where it looks up what Google Cloud Region to put devices into. That is very unexpected, especially if I've gone through the trouble of creating multiple Locations to cover all my GCP regions.
What did you expect to happen instead? (Optional)
I expected instead to refer to the Location by the name of the Location object and Datum would figure out the City Code and Google Cloud region from there directly.
Do you have any suggestions for improvement? (Optional)
No response
Relevant URL or Section of the Application (Optional)
No response
Attachments / Screenshots (Optional)
No response