Open Stack

On 30 June 2014 16:05, Eric Frizziero <eric.frizziero at pd.infn.it> wrote:

> In more detail, some features of the FairshareScheduler are:
> a) It assigns dynamically the proper priority to every new user requests;
> 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;
> 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;
> 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;
> e) User requests are dequeued by a pool of WorkerThreads (configurable),
> i.e. no sequential processing of the requests;
> f) The failed requests at filtering + weighting phase may be inserted
> again in the queue for n-times (configurable).
>
> We have integrated the FairShareScheduler in our Openstack installation
> (release "HAVANA"). We're now working to adapt the FairShareScheduler to
> the new release "IceHouse".
>
> Does anyone have experiences in those issues found in our cloud scenario?
>
> Could the FairShareScheduler be useful for the Openstack community?
> In that case, we'll be happy to share our work.
>

Sounds like an interesting option to have available.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140630/127280c9/attachment.html>