2014-02-11 18:28 GMT+01:00 Yathiraj Udupi (yudupi) :
>
>
> Thanks for your pointers about Climate. I will take a closer look at it
> and try it out. So after a reservation lease for a VM is made by Climate,
> who acts on it to finally instantiate the VM ? Is it Climate or Nova should
> act on t
>
> So after a reservation lease for a VM is made by Climate, who acts on it
> to finally instantiate the VM ? Is it Climate or Nova should act on the
> lease to finally provision the VM.
Now to take resources for VM it's actually created and then immediately
shelved, not to be in active state an
hi Sylvain and Dina,
Thanks for your pointers about Climate. I will take a closer look at it and
try it out. So after a reservation lease for a VM is made by Climate, who acts
on it to finally instantiate the VM ? Is it Climate or Nova should act on the
lease to finally provision the VM.
Tha
>
> This is something to explore to add in Nova, using
> a local service or external service (need to explore Climate).
I need to find out more about Climate.
Here is Climate Launchpad: https://launchpad.net/climate
That's still really young project, but I believe it'll have great future
speak
Le 11/02/2014 17:23, Yathiraj Udupi (yudupi) a écrit :
Hi Dina,
Thanks for note about Climate logic. This is something that will be
very useful, when we will have to schedule from Nova multiple
instances (of potentially different flavors) as a single request. If
the Solver Scheduler, can ma
Hi Dina,
Thanks for note about Climate logic. This is something that will be very
useful, when we will have to schedule from Nova multiple instances (of
potentially different flavors) as a single request. If the Solver Scheduler,
can make a request to the Climate service to reserve the resour
I thought of adding some more points about the Solver Scheduler to this
conversation.
Think of SolverScheduler as a placement decision engine, which gives an
optimal solution for the specified request based on the current
information available at a specific time. The request could potentially
be a
Thanks, I will look closely at it.
De : Dina Belova [mailto:dbel...@mirantis.com]
Envoyé : mardi 11 février 2014 16:45
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
Solver Scheduler
Like a restaurant
>
> Like a restaurant reservation, it would "claim" the resources for use by
> someone at a later date. That way nobody else can use them.
> That way the scheduler would be responsible for determining where the
> resource should be allocated from, and getting a reservation for that
> resource. It
Le 11/02/2014 16:09, Chris Friesen a écrit :
Yes. So what I'm suggesting is that we schedule the two VMs as one
call to the SolverScheduler. The scheduler then gets reservations for
the necessary resources and returns them to the caller. This would be
sort of like the existing Claim object
On 02/11/2014 03:21 AM, Khanh-Toan Tran wrote:
Second, there is nothing wrong with booting the instances (or
instantiating other
resources) as separate commands as long as we support some kind of
reservation token.
I'm not sure what reservation token would do, is it some kind of informing
the
that reservations should be managed by Nova, but rather
> by another service.
No argument here J
De : Sylvain Bauza [mailto:sylvain.ba...@gmail.com]
Envoyé : mardi 11 février 2014 10:39
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Nova][Sch
2014-02-10 18:45 GMT+01:00 Chris Friesen :
>
> In that model, we would pass a bunch of information about multiple
> resources to the solver scheduler, have it perform scheduling *and reserve
> the resources*, then return some kind of resource reservation tokens back
> to the caller for each resour
stack-dev@lists.openstack.org
> Objet : Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
Solver
> Scheduler
>
> On 02/10/2014 10:54 AM, Khanh-Toan Tran wrote:
>
> > Heat
> > may orchestrate the provisioning process, but eventually the instances
> > will
On 02/10/2014 10:54 AM, Khanh-Toan Tran wrote:
Heat
may orchestrate the provisioning process, but eventually the instances will be
passed to Nova-scheduler (Gantt) as separated commands, which is exactly the
problem Solver Scheduler wants to correct. Therefore the Instance Group API is
needed, w
l scheduler addressing
> compute+storage+network.
> Feedback is most welcome.
Thank you for the link, I will give it a try.
Best regards,
Toan
- Original Message -
> From: "Mike Spreitzer"
> To: "OpenStack Development Mailing List (not for usage question
OpenStack Development Mailing List \(not for usage questions\)"
,
Date: 02/04/2014 10:10 AM
Subject: Re: [openstack-dev] [Nova][Scheduler] Policy Based
Scheduler and Solver Scheduler
> From: Khanh-Toan Tran
...
> There is an unexpected line break in the middle of
> From: Khanh-Toan Tran
...
> There is an unexpected line break in the middle of the link, so I post
it
> again:
>
>
https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bqolOri
> IQB2Y
The mailing list software keeps inserting that line break. I
re-constructed the URL and look
;
Subject:Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver
Scheduler
On 02/03/2014 12:28 PM, Khanh-Toan Tran wrote:
> Another though would be the need for Instance Group API [1].
> Currently users can only request multiple instances of the same
> flavors. These reques
On 02/03/2014 12:28 PM, Khanh-Toan Tran wrote:
Another though would be the need for Instance Group API [1].
Currently users can only request multiple instances of the same
flavors. These requests do not need LP to solve, just placing
instances one by one is sufficient. Therefore we need this API
[1] https://wiki.openstack.org/wiki/InstanceGroupApiExtension
- Original Message -
From: Yathiraj Udupi (yudupi)
To: OpenStack Development Mailing List (not for usage questions)
Sent: Thu, 30 Jan 2014 18:13:59 - (UTC)
Subject: Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
Solver
rds,
Gil
From:Khanh-Toan Tran
mailto:khanh-toan.t...@cloudwatt.com>>
To:"OpenStack Development Mailing List \(not for usage questions\)"
mailto:openstack-dev@lists.openstack.org>>,
Date: 01/30/2014 01:43 PM
Subject: Re: [openstack-dev] [Nova][
initial thoughts on this approach.
Regards,
Gil
From: Khanh-Toan Tran
To: "OpenStack Development Mailing List \(not for usage questions\)"
,
Date: 01/30/2014 01:43 PM
Subject: Re: [openstack-dev] [Nova][Scheduler] Policy Based
Scheduler and Solver Scheduler
Hi
/1gr4Pb1ErXymxN9QXR4G_jVjLqNOg2ij9oA0JrL
wMVRA
Toan
De : Sylvain Bauza [mailto:sylvain.ba...@gmail.com]
Envoyé : jeudi 30 janvier 2014 11:16
À : OpenStack Development Mailing List (not for usage questions)
Objet : Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
Solver Scheduler
Hi
pment Mailing List (not for usage questions)'
> > Objet : [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
> Solver
> > Scheduler
> >
> > Dear all,
> >
> > As promised in the Scheduler/Gantt meeting, here is our analysis on th
ier 2014 13:25
> À : 'OpenStack Development Mailing List (not for usage questions)'
> Objet : [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and
Solver
> Scheduler
>
> Dear all,
>
> As promised in the Scheduler/Gantt meeting, here is our analysis on the
&g
Dear all,
As promised in the Scheduler/Gantt meeting, here is our analysis on the
connection between Policy Based Scheduler and Solver Scheduler:
https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bqolOri
IQB2Y
This document briefs the mechanism of the two schedulers and the
poss
27 matches
Mail list logo
