<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">He can't use SimpleScheduler *AND* multi-backend.<div><br><div><div>On Jun 18, 2013, at 2:10 AM, Huang Zhiteng <<a href="mailto:winston.d@gmail.com">winston.d@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hmm, maybe all your volume drivers are reporting 'infinite' as free capacity no matter how many volumes were created. So possible solutions are: 1) change to simple/chance scheduler, with this you will be able to do round robin placement but you miss advanced feature provided by filter scheduler; 2) change your volume drivers so that it correctly report free capacity; 3) add a custom weigher that doesn't weigh volume services with free capacity but other things like allocated volumes.<br>
<br>Both 2) and 3) require code change and doesn't seem trivial. So given that your environment is small/simple, I suggest you change to simple/chance scheduler.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Jun 18, 2013 at 5:02 PM, Sebastien Han <span dir="ltr"><<a href="mailto:sebastien.han@enovance.com" target="_blank">sebastien.han@enovance.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Thanks for your answer, the thing is, since it's always the same LUN, so all the new volume are created using the same block. The free capacity is always the same, this is why it's not well balanced. Any idea to tell the scheduler to do round robin?<div>
<div class="im"><br><div>––––<br>Sébastien Han<br>Cloud Engineer<br><br>"Always give 100%. Unless you're giving blood."<br><br><br><br><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span><span><image.png></span></span><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;min-height:14px;line-height:normal;text-transform:none;font-size:12px;white-space:normal;margin:0px;font-family:Arial;word-spacing:0px">
<br><br><br><br><br><br></div><div style="font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-family:Arial;font-size:11px;margin:0px;color:rgb(47,89,147)">
<b>Phone : </b><a href="tel:%2B33%20%280%291%2049%2070%2099%2072" value="+33149709972" target="_blank">+33 (0)1 49 70 99 72</a><span style="color:rgb(84,99,114)"> – </span><b>Mobile : </b><a href="tel:%2B33%20%280%296%2052%2084%2044%2070" value="+33652844470" target="_blank">+33 (0)6 52 84 44 70</a></div>
<div style="font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-family:Arial;font-size:11px;margin:0px;color:rgb(47,89,147)">
<b>Email :</b> <a href="mailto:sebastien.han@enovance.com" target="_blank"><span style="color:rgb(52,0,238)">sebastien.han@enovance.com</span></a> <span style="color:rgb(84,99,114)">– </span><b>Skype : </b>han.sbastien</div>
<div style="font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-family:Arial;font-size:11px;margin:0px;color:rgb(47,91,148)">
<span style="color:rgb(47,89,147)"><b>Address :</b> </span>10, rue de la Victoire – 75009 Paris</div><div style="font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-family:Arial;font-size:11px;margin:0px;color:rgb(47,89,147)">
<span style="color:rgb(47,91,148)"><b>Web : </b><a href="http://www.enovance.com/" target="_blank"><span style="color:rgb(52,0,238)">www.enovance.com</span></a></span> <span style="color:rgb(84,99,114)">– </span><b>Twitter : </b>@enovance</div>
</span></div><br></div><div class="im">On Jun 18, 2013, at 10:46 AM, Huang Zhiteng <<a href="mailto:winston.d@gmail.com" target="_blank">winston.d@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div class="im">
On Tue, Jun 18, 2013 at 3:57 PM, Sebastien Han <<a href="mailto:sebastien.han@enovance.com" target="_blank">sebastien.han@enovance.com</a>> wrote:<br>Hi,<br><br>I use this one: scheduler_driver=cinder.scheduler.filter_scheduler.FilterScheduler<br>
<br>Well, default weigher for filter scheduler sorts all volume services by free capacity if you haven't change default filter/weigher. So I think the reason one volume always get picked up to serve request is because it reports the most available capacity among all volume services. You may check log from volume services as well as scheduler to confirm.<br>
<br>Thanks!<br><br>––––<br>Sébastien Han<br>Cloud Engineer<br><br>"Always give 100%. Unless you're giving blood."<br><br><br><br></div><div><div class="h5"><span><image.png></span><br><br><br><br><br>
<br><br>Phone : <a href="tel:%2B33%20%280%291%2049%2070%2099%2072" value="+33149709972" target="_blank">+33 (0)1 49 70 99 72</a> – Mobile : <a href="tel:%2B33%20%280%296%2052%2084%2044%2070" value="+33652844470" target="_blank">+33 (0)6 52 84 44 70</a><br>
Email : <a href="mailto:sebastien.han@enovance.com" target="_blank">sebastien.han@enovance.com</a> – Skype : han.sbastien<br>Address : 10, rue de la Victoire – 75009 Paris<br>Web : <a href="http://www.enovance.com/" target="_blank">www.enovance.com</a> – Twitter : @enovance<br>
<br>On Jun 18, 2013, at 4:30 AM, Huang Zhiteng <<a href="mailto:winston.d@gmail.com" target="_blank">winston.d@gmail.com</a>> wrote:<br><br><blockquote type="cite">Hi Sebastien,<br><br>What scheduler are you using in Cinder?<br>
<br><br>On Mon, Jun 17, 2013 at 4:20 PM, Sebastien Han <<a href="mailto:sebastien.han@enovance.com" target="_blank">sebastien.han@enovance.com</a>> wrote:<br>Hi all,<br><br>Here the problem:<br><br>I have 2 Datacenters, 2 computes par DC, a SAN and the LUN is mapped on every compute nodes. So all the compute nodes share the same block device. I use the LVM iSCSI driver for Cinder and obviously the multi-backend. Thus I created AZ for cinder based on the location of the cinder-volume process (cinder-volume runs on every compute nodes), I have two AZ: DC1 and DC2. However when I try to create a volume I get most the volume on the first compute node of the specified location. Thus most of the iSCSI targets are created on the same node and I don't like this.<br>
<br>Little schema here <a href="http://www.asciiflow.com/#Draw7392320624318387463" target="_blank">http://www.asciiflow.com/#Draw7392320624318387463</a><br><br>My question is: can I tweak the scheduler to create volume in a round robin fashion, then I can have an even repartition of the targets.<br>
<br>Thanks in advance!<br><br>––––<br>Sébastien Han<br>Cloud Engineer<br><br>"Always give 100%. Unless you're giving blood."<br><br><br><br><image.png><br><br><br><br><br><br><br><br>Phone : <a href="tel:%2B33%20%280%291%2049%2070%2099%2072" value="+33149709972" target="_blank">+33 (0)1 49 70 99 72</a> – Mobile : <a href="tel:%2B33%20%280%296%2052%2084%2044%2070" value="+33652844470" target="_blank">+33 (0)6 52 84 44 70</a><br>
Email : <a href="mailto:sebastien.han@enovance.com" target="_blank">sebastien.han@enovance.com</a> – Skype : han.sbastien<br>Address : 10, rue de la Victoire – 75009 Paris<br>Web : <a href="http://www.enovance.com/" target="_blank">www.enovance.com</a> – Twitter : @enovance<br>
<br><br>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br><br><br><br>-- <br>Regards<br>Huang Zhiteng<br></blockquote><br><br><br><br>-- <br>Regards<br>Huang Zhiteng<br></div></div></blockquote><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Regards<br>Huang Zhiteng
</div>
_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br></blockquote></div><br></div></body></html>