b8ebbe9919
This will enable a number of possible features that need to select amphorae based on their availability zone. This would allow for quick-lookups on large lists and could be stale, but it would be expected that future code that uses this would check with nova for an update if it needs fully accurate data. Having it be explicitly "cached" should take care of concerns about users (operators, in this case) being confused about correctness. Using simply the word "zone" should address concerns about commonality between compute providers. Change-Id: I8e26f99bca3496a454ba7bae2570f517e07d5fc2 Story: 2001221 Task: 5732
11 lines
517 B
YAML
11 lines
517 B
YAML
---
|
|
features:
|
|
- |
|
|
The compute zone (if applicable) is now cached in the database and returned
|
|
in the Amphora API as `cached_zone`. Please note that this is only set at
|
|
the original time of provisioning, and could be stale for various reasons
|
|
(for example, if live-migrations have taken place due to maintenances). We
|
|
recommend it be used for reference only, unless you are absolutey certain
|
|
it is current in your environment. The source of truth is still the system
|
|
you use for compute.
|