[Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

Joe Topjian joe at topjian.net
Sun Apr 2 00:32:01 UTC 2017

On Sat, Apr 1, 2017 at 5:21 PM, Matt Riedemann <mriedemos at gmail.com> wrote:

> On 4/1/2017 8:36 AM, Blair Bethwaite wrote:
>> Hi all,
>> The below was suggested for a Forum session but we don't yet have a
>> submission or name to chair/moderate. I, for one, would certainly be
>> interested in providing input. Do we have any owners out there?
>> Resource reservation requirements:
>> ==
>> The Blazar project [https://wiki.openstack.org/wiki/Blazar] has been
>> revived following Barcelona and will soon release a new version. Now
>> is a good time to get involved and share requirements with the
>> community. Our development priorities are described through Blueprints
>> on Launchpad: https://blueprints.launchpad.net/blazar
>> In particular, support for pre-emptible instances could be combined
>> with resource reservation to maximize utilization on unreserved
>> resources.+1
> Regarding resource reservation, please see this older Nova spec which is
> related:
> https://review.openstack.org/#/c/389216/
> And see the points that Jay Pipes makes in that review. Before spending a
> lot of time reviving the project, I'd encourage people to read and digest
> the points made in that review and if there responses or other use cases
> then let's discuss them *before* bringing a service back from the dead and
> assume it will be integrated into the other projects.

This is appreciated. I'll describe the way I've seen Blazar used and I
believe it's quite different than the above slot reservation as well as
spot instance support, but please let me know if I am incorrect or if there
have been other discussions about this use-case elsewhere:

A research group has a finite amount of specialized hardware and there are
more people wanting to use this hardware than what's currently available.
Let's use high performance GPUs as an example. The group is OK with
publishing the amount of hardware they have available (normally this is
hidden as best as possible). By doing this, a researcher can use Blazar as
sort of a community calendar, see that there are 3 GPU nodes available for
the week of April 3, and reserve them for that time period.

>> Is Blazar the right project to discuss reservations of finite
>> consumable resources like software licenses?
>>   Blazar would like to ultimately support many different kinds of
>> resources (volumes, floating IPs, etc.). Software licenses can be
>> another type.
>> ==
>> (https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg)
>> Cheers,
> John Garbutt also has a WIP backlog spec in Nova related to pre-emtiple
> instances:
> https://review.openstack.org/#/c/438640/
> --
> Thanks,
> Matt
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170401/1ff91505/attachment.html>

More information about the OpenStack-operators mailing list