<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Sylvain,<br>
<br>
thanks a lot for your answer.<br>
<br>
I'd like to extend (if possible) the BLAZAR's list of the
supported lease types by adding a new one which covers a specific
use case which, it seems, it is not yet supported by BLAZAR. You
know, In OpenStack every project has a granted fixed quota which
cannot be extended dynamically. This implies that a project cannot
allocate unused resources assigned to different projects. The idea
is to lease such unused resources just for a limited duration time
(e.g. from few hours to 1 day). Suppose the project "A" has
consumed all own assigned resources while the project "B", in the
current time, has several available resources. "B" may offer its
own resources to "A" just for a limited and well known time
duration (i.e. not forever) so that in the future it can claim, if
needed, the available resources belonging to "A" (or other
projects).<br>
This is a fair-share mechanism which guarantees the resources
usage is equally distributed among users and projects by
considering the portion of the resources allocated to them (i.e.
share) and the resources already consumed. Please remark the
"share" is a different concept than "quota" in the cloud
terminology. You can consider this proposal as a way to update
dynamically the quotas by considering the historical usage of each
project. This approach should make OpenStack very efficient in
terms of resource utilization.<br>
<br>
About the blueprint I will try to create a new one. <br>
<br>
Thanks again.<br>
Cheers,<br>
Lisa<br>
<br>
On 18/09/2014 16:00, Sylvain Bauza wrote:<br>
</div>
<blockquote cite="mid:541AE58A.1080503@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">Le 18/09/2014 15:27, Lisa a écrit :<br>
</div>
<blockquote cite="mid:541ADDD7.8060103@pd.infn.it" type="cite">Hi
all, <br>
<br>
my name is Lisa Zangrando and I work at the Italian National
Institute for Nuclear Physics (INFN). In particular I am leading
a team which is addressing the issue concerning the efficiency
in the resource usage in OpenStack. <br>
Currently OpenStack allows just a static partitioning model
where the resource allocation to the user teams (i.e. the
projects) can be done only by considering fixed quotas which
cannot be exceeded even if there are unused resources (but)
assigned to different projects. <br>
We studied the available BLAZAR's documentation and, in
agreement with Tim Bell (who is responsible the OpenStack cloud
project at CERN), we think this issue could be addressed within
your framework. <br>
Please find attached a document that describes our use cases
(actually we think that many other environments have to deal
with the same problems) and how they could be managed in BLAZAR,
by defining a new lease type (i.e. fairShare lease) to be
considered as extension of the list of the already supported
lease types. <br>
I would then be happy to discuss these ideas with you. <br>
<br>
Thanks in advance, <br>
Lisa <br>
<br>
</blockquote>
<br>
Hi Lisa,<br>
<br>
Glad to see you're interested in Blazar.<br>
<br>
I tried to go thru your proposal, but could you please post the
main concepts of what you plan to add into an etherpad and create
a blueprint [1] mapped to it so we could discuss on the
implementation ?<br>
Of course, don't hesitate to ping me or the blazar community in
#openstack-blazar if you need help with the process or the current
Blazar design.<br>
<br>
Thanks,<br>
-Sylvain<br>
<br>
[1] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://blueprints.launchpad.net/blazar/">https://blueprints.launchpad.net/blazar/</a><br>
<br>
<blockquote cite="mid:541ADDD7.8060103@pd.infn.it" type="cite"><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a moz-do-not-send="true" 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>
<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>