You need to use aggregates if you want to use different storage backends
per compute.
For what's it worth, if you really want to have the scheduler having a
way to verify storage backends, that would be a new feature and not a
bug.
** Changed in: nova
Status: New => Invalid
--
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/1945401
Title:
scheduler can not filter node by storage backend
Status in OpenStack Compute (nova):
Invalid
Bug description:
If my aggregation has ceph backend node cmp01 and fcsan backend node cmp02,
and I create a ceph backend VM01 in cmp01, then execute migrate it.
The migration will be failed if scheduler filter cmp02 or I set the
target node is cmp02.
------Traceback------
oslo_messaging.rpc.client.RemoteError: Remote error:
ClientException Unable to create attachment for volume
(Invalid input received: Connector doesn't have required information: wwpns).
(HTTP 500)
I think nova need to pre-check the target node I set or
filter the available storage backend compute nodes when selecting destination.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1945401/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
