Thanks for your feedback Andrew. And thanks for asking that question.
(Just to clarify your statement for others too -- Nova proxy Images API does not allow setting custom location for the end user.)
I've added the nova-core-sec to this bug after some discussion initiated by Mike Fedosin, questioning if is Glance-v2 is production ready or not. Hence, this is related in a way that if Nova defaults to using Glance-v2, operators would be expected to deploy Glance-v2 as well. If that happens, what means for deployments that require multiple locations related features to expose Glance-v2 to end users.
Image immutability/stability promise is broken with this bug, and the following bugs affect too [1], [2].
So, Mike has propose the following for Nova v1, v2 work:
* Add experimental support of glance v2 in Nova, but send OSSN where it is recommended not to use it until all issues are fixed.
Thanks for your feedback Andrew. And thanks for asking that question.
(Just to clarify your statement for others too -- Nova proxy Images API does not allow setting custom location for the end user.)
I've added the nova-core-sec to this bug after some discussion initiated by Mike Fedosin, questioning if is Glance-v2 is production ready or not. Hence, this is related in a way that if Nova defaults to using Glance-v2, operators would be expected to deploy Glance-v2 as well. If that happens, what means for deployments that require multiple locations related features to expose Glance-v2 to end users.
Image immutability/ stability promise is broken with this bug, and the following bugs affect too [1], [2].
So, Mike has propose the following for Nova v1, v2 work:
* Add experimental support of glance v2 in Nova, but send OSSN where it is recommended not to use it until all issues are fixed.
[1] https:/ /bugs.launchpad .net/glance/ +bug/1549483 /bugs.launchpad .net/glance/ +bug/1555590
[2] https:/