| 2016-09-27 13:35:39 |
Goutham Pacha Ravi |
description |
In cases where the share servers are supposed to be created and managed at the storage pools level, this is confusing to administrators. Since we have the stance that share servers need not span storage pools of a given backend, and that driver developers may choose to limit servers to a given pool, we should reflect the pool name in the host field and possibly add an attribute to specify whether the share server services different storage pools or not. |
Applies to DHSS=True only.
In cases where the share servers are supposed to be created and managed at the storage pools level, this is confusing to administrators. Since we have the stance that share servers need not span storage pools of a given backend (See HPE Storage Pools implementation [1]), and that driver developers may choose to limit servers to a given pool, we should reflect the pool name in the host field and possibly add an attribute to specify whether the share server services different storage pools or not.
[1] was merged with a workaround for this bug by passing the necessary pool information to the driver through a kwarg: metadata with the 'request_host' in it that contained the host of the share instance that was being created (share instance host field values are of the form host@backend#pool)
[1] https://review.openstack.org/#/c/329552 |
|
