<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 06/30/2014 04:35 PM, Jesse Pretorius
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAGSrQvxbYhcSWF1csb5uGFcEggaYQEbUeAZ-r=FXTD8YJrf=3Q@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On 30 June 2014 16:05, Eric Frizziero
            <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:eric.frizziero@pd.infn.it" target="_blank">eric.frizziero@pd.infn.it</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">In more
              detail, some features of the FairshareScheduler are:<br>
              a) It assigns dynamically the proper priority to every new
              user requests;<br>
              b) The priority of the queued requests will be
              recalculated periodically using the fairshare algorithm.
              This feature guarantees the usage of the cloud resources
              is distributed among users and groups by considering the
              portion of the cloud resources allocated to them (i.e.
              share) and the resources already consumed;<br>
              c) all user requests will be inserted in a (persistent)
              priority queue and then processed asynchronously by the
              dedicated process (filtering + weighting phase) when
              compute resources are available;<br>
              d) From the client point of view the queued requests
              remain in “Scheduling” state till the compute resources
              are available. No new states added: this prevents any
              possible interaction issue with the Openstack clients;<br>
              e) User requests are dequeued by a pool of WorkerThreads
              (configurable), i.e. no sequential processing of the
              requests;<br>
              f) The failed requests at filtering + weighting phase may
              be inserted again in the queue for n-times (configurable).<br>
              <br>
              We have integrated the FairShareScheduler in our Openstack
              installation (release "HAVANA"). We're now working to
              adapt the FairShareScheduler to the new release
              "IceHouse".<br>
              <br>
              Does anyone have experiences in those issues found in our
              cloud scenario?<br>
              <br>
              Could the FairShareScheduler be useful for the Openstack
              community?<br>
              In that case, we'll be happy to share our work.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Sounds like an interesting option to have available.</div>
          </div>
        </div>
      </div>
    </blockquote>
    Thank you very much for your feedback!<br>
    <br>
    Cheers,<br>
     Eric.<br>
    <br>
    <br>
    <blockquote
cite="mid:CAGSrQvxbYhcSWF1csb5uGFcEggaYQEbUeAZ-r=FXTD8YJrf=3Q@mail.gmail.com"
      type="cite">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>