<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Hi Valeriy,</div>
<div class=""><br class="">
</div>
<div class="">I wasn’t aware, thanks! </div>
<div class=""><br class="">
</div>
<div class="">So, if each driver exposes the storage_protocols it supports, would it be sensible to have</div>
<div class="">manila-ui check the extra_specs for this key and limit the protocol choice for a given</div>
<div class="">share type to the supported protocols (in order to avoid that the user tries to create</div>
<div class="">incompatible type/protocol combinations)?</div>
<div class=""><br class="">
</div>
<div class="">Thanks again!</div>
<div class=""> Arne</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On 02 Nov 2016, at 10:00, Valeriy Ponomaryov <<a href="mailto:vponomaryov@mirantis.com" class="">vponomaryov@mirantis.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Hello, Arne
<div class=""><br class="">
</div>
<div class="">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].</div>
<div class=""><br class="">
</div>
<div class="">It is the purpose of extra specs in share types, you (as cloud admin) define its connection yourself, either it is strong or not.</div>
<div class=""><br class="">
</div>
<div class="">Valeriy</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Wed, Nov 2, 2016 at 9:51 AM, Arne Wiebalck <span dir="ltr" class="">
<<a href="mailto:Arne.Wiebalck@cern.ch" target="_blank" class="">Arne.Wiebalck@cern.ch</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br class="">
<br class="">
We’re preparing the use of Manila in production and noticed that there seems to be no strong connection<br class="">
between share types and share protocols.<br class="">
<br class="">
I would think that not all backends will support all protocols. If that’s true, wouldn’t it be sensible to establish<br class="">
a stronger relation and have supported protocols defined per type, for instance as extra_specs (which, as one<br class="">
example, could then be used by the Manila UI to limit the choice to supported protocols for a given share<br class="">
type, rather than maintaining two independent and hard-coded tuples)?<br class="">
<br class="">
Thanks!<br class="">
Arne<br class="">
<br class="">
--<br class="">
Arne Wiebalck<br class="">
CERN IT<br class="">
<br class="">
______________________________<wbr class="">______________________________<wbr class="">______________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.<wbr class="">openstack.org?subject:<wbr class="">unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-dev</a><br class="">
</blockquote>
</div>
<br class="">
<br clear="all" class="">
<div class=""><br class="">
</div>
-- <br class="">
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr" class="">Kind Regards<br class="">
Valeriy Ponomaryov<br class="">
<a href="http://www.mirantis.com/" target="_blank" class="">www.mirantis.com</a><br class="">
<a href="mailto:vponomaryov@mirantis.com" target="_blank" class="">vponomaryov@mirantis.com</a><br class="">
</div>
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
<div class="">--<br class="">
Arne Wiebalck<br class="">
CERN IT </div>
<br class="">
</body>
</html>