On 02 Nov 2016, at 15:15, Ben Swartzlander
> wrote:
On 11/02/2016 06:23 AM, Arne Wiebalck wrote:
Hi Valeriy,
I wasn’t aware, thanks!
So, if each driver exposes the storage_protocols it supports, would it be
sensible to have
manila-ui check
On 11/02/2016 06:23 AM, Arne Wiebalck wrote:
Hi Valeriy,
I wasn’t aware, thanks!
So, if each driver exposes the storage_protocols it supports, would it
be sensible to have
manila-ui check the extra_specs for this key and limit the protocol
choice for a given
share type to the supported
> On 02 Nov 2016, at 11:52, Tom Barron wrote:
>
>
>
> On 11/02/2016 06:23 AM, Arne Wiebalck wrote:
>> Hi Valeriy,
>>
>> I wasn’t aware, thanks!
>>
>> So, if each driver exposes the storage_protocols it supports, would it
>> be sensible to have
>> manila-ui check the
On 11/02/2016 06:23 AM, Arne Wiebalck wrote:
> Hi Valeriy,
>
> I wasn’t aware, thanks!
>
> So, if each driver exposes the storage_protocols it supports, would it
> be sensible to have
> manila-ui check the extra_specs for this key and limit the protocol
> choice for a given
> share type to
Hi Valeriy,
I wasn’t aware, thanks!
So, if each driver exposes the storage_protocols it supports, would it be
sensible to have
manila-ui check the extra_specs for this key and limit the protocol choice for
a given
share type to the supported protocols (in order to avoid that the user tries to
Hello, Arne
Each share driver has capability called "storage_protocol". So, for case
you describe, you should just define such extra spec in your share type
that will match value reported by desired backend[s].
It is the purpose of extra specs in share types, you (as cloud admin)
define its
Hi,
We’re preparing the use of Manila in production and noticed that there seems to
be no strong connection
between share types and share protocols.
I would think that not all backends will support all protocols. If that’s true,
wouldn’t it be sensible to establish
a stronger relation and have