[Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session
blair.bethwaite at gmail.com
Mon Apr 3 04:24:06 UTC 2017
So I've proposed a Forum session to discuss some of these issues and
use-cases: http://forumtopics.openstack.org/cfp/details/124 - there
would seem to be value in getting Nova, Blazar and OPIE folks together
to talk about advanced scheduling use-cases. In particular it looks
like there is a need (and gap?) for Nova's scheduler to model and
support (either directly or through extension/pluggability) more than
just on-demand scheduling workflows.
However, I'm not an active dev and am somewhat ignorant on the state
of nova-scheduler and related components now, so would appreciate
someone who knows what they are talking about to help chair this
session and provide some updates to the proposal that include
background reading etc.
On 2 April 2017 at 09:21, 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
> Regarding resource reservation, please see this older Nova spec which is
> 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.
>> 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.
> John Garbutt also has a WIP backlog spec in Nova related to pre-emtiple
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
More information about the OpenStack-operators