The constraint checking kind of needs to be in the db layer because
that's the only place we have access to it. Possibly a future clean up.
But I think Opinion marks the current real state.
** Changed in: nova
Status: Triaged => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1097605
Title:
osapi_compute_unique_server_name_scope is a strange little option
Status in OpenStack Compute (Nova):
Opinion
Bug description:
See https://review.openstack.org/19174
osapi_compute_unique_server_name_scope sounds like its a detail of the
openstack API layer, but the option and its usage lives in the DB
layer
It would be nice if we could figure out some way of moving it into the
API layer
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1097605/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
