<div dir="ltr">You can define several backends with the same volume_backend_name and call that a group. For example:<div>[groupA-be1]</div><div>volume_backend_name=fast-ssd<br></div><div><br></div><div><div>[groupA-be2]</div><div>volume_backend_name=fast-ssd<br></div></div><div><br></div><div><div>[groupB-be3]</div><div>volume_backend_name=slow-disk<br></div></div><div><br></div><div>So, no matter what storage is behind every backend, it will be filtered based on the backend_name (and the other capabilities each backend reports). If you don't want to restart the volume service to each backend you add. You can add another instance of cinder-volume, even in the same controller. The scheduler will know how to handle the new ones.</div><div><br></div><div>Erlon</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 6:15 AM, chen ying <span dir="ltr"><<a href="mailto:chenyingkof@outlook.com" target="_blank">chenyingkof@outlook.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<p></p>
<div style="color:rgb(33,33,33);font-size:15px;margin:0px"><font face="宋体" size="3"><span style="font-size:12pt"><font face="Calibri,sans-serif" size="2" color="#1F497D"><span lang="en-US" style="font-size:10.5pt">
<div>Hi Duncan Thomas,</div>
<div> Does you means we can create a volume type include list of backend names(such as: backend_name="<in> name1 name2 name3 name4"), so when we create a volume, we can use the volume type to choose one backend from these list of backend names(name1,name2,name3,name4)?</div>
<div>But in this way, we cannot show the backends obviously capabilities to users(such as: performance, ssd, spinning-rust etc).</div>
</span></font></span></font></div>
<div style="color:rgb(33,33,33);font-size:15px;text-indent:9pt;margin:0px">
<font face="宋体" size="3"><span style="font-size:12pt"><font face="Calibri,sans-serif" size="2" color="#1F497D"><span lang="en-US" style="font-size:10.5pt"></span></font></span></font></div>
<br>
<p></p>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr style="display:inline-block;width:98%">
<div dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>发件人:</b> Duncan Thomas <<a href="mailto:duncan.thomas@gmail.com" target="_blank">duncan.thomas@gmail.com</a>><br>
<b>发送时间:</b> 2016年6月14日 8:03<br>
<b>收件人:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>主题:</b> Re: [openstack-dev] [cinder]The backend-group concept in Cinder</font>
<div> </div>
</div><div><div class="h5">
<div>
<div dir="ltr">As long as each backend has a unique name, you can key the type to a list of backend names if there's no useful capabilities to key off. No restart required.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 14 June 2016 at 10:16, chen ying <span dir="ltr"><<a href="mailto:chenyingkof@outlook.com" target="_blank">chenyingkof@outlook.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<p><span></span></p>
<p><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Hi
</span><span lang="EN-US" style="font-size:10pt">John,</span></p>
<p><span lang="EN-US" style="font-size:10pt"> </span></p>
<p><span lang="EN-US" style="font-size:10pt"> </span><span lang="EN-US">User case 1:<br>
The backends in backend-group-1 have SSD disk, more memory . The backend-group-1 can provide higher performance to user.<br>
The other backends in backend-group-2 have HHD disk, more capacity. The backend-group-2 can provide more storage space to user .</span></p>
<p><span lang="EN-US" style="font-family:'Cambria Math','serif'"></span><span lang="EN-US" style="font-family:'Courier New'">Not sure, but we sort of do some of this already via the filter scheduler. An Admin can define various types (they may be set up based
on performance, ssd, spinning-rust etc). Those types are then given arbitrary definitions via a type (again details hidden from end user) and he/she can create volumes of a specific type.</span></p>
<p><span lang="EN-US" style="font-size:10pt"> </span></p>
<p style="text-indent:21pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Yes, An Admin can arbitrary define various types and he/she can create volumes of a specific type. But we need to restart our cinder
driver after define various types in each driver(If the driver cannot report capabilities by itself). It will not easy to manage for Admin. </span></p>
<p style="text-indent:21pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Does Admin could use the concept of dynamically adding/removing backends to backend-group. In this way, we not need to modify backend
configure file(such as: report a capabilities of ssd, spinning-rust etc).We can arbitrary define various types for backend-group, and also he/she can create volumes of a specific type(from backend-group type).</span></p>
<p style="text-indent:21pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">So for example I could say "I want these backends with capability XYZ", and many of backends from different vendors. How to manage these
backends by Administrator?</span></p>
<p style="text-indent:21pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Currently:</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">1.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Admin need modify backend configure file, let the backend report capability XYZ to filter scheduler.</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">2.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Restart the volume service, make the capability valid</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">3.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Create volume type(test_type) with capability XYZ.</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">4.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">he/she can create volumes of a specific type(test_type)</span></p>
<p><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt"> Now we expect:</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">1.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Admin add backend to backend-group</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">2.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">Create volume type(test_type) with capability XYZ, use frefix(group or something else (group: capability = XYZ)) to distinguish between the backend
capability and the backend-group capability.</span></p>
<p style="margin-left:83.3pt"><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">3.<span style="font-family:'Times New Roman';font-size:7pt">
</span></span><span lang="EN-US" style="font-family:'Calibri','sans-serif';color:#1f497d;font-size:10.5pt">he/she can create volumes of a specific type(test_type)</span></p>
<span></span><br>
<p></p>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>
<div dir="ltr">
<div>-- <br>
Duncan Thomas</div>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>