, if
the VMs are together (belong to an app), then we have to put them into an
Instance Group.
-Message d'origine-
De : Chris Friesen [mailto:chris.frie...@windriver.com]
Envoyé : lundi 10 février 2014 18:45
À : openstack-dev@lists.openstack.org
Objet : Re: [openstack-dev] [Nova][Scheduler
2014-02-10 18:45 GMT+01:00 Chris Friesen chris.frie...@windriver.com:
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
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
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
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 would
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
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
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
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
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
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.
2014-02-11 18:28 GMT+01:00 Yathiraj Udupi (yudupi) yud...@cisco.com:
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
regards,
Toan
- Original Message -
From: Mike Spreitzer mspre...@us.ibm.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, February 4, 2014 9:05:22 AM
Subject: Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler
Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date: 02/04/2014 10:10 AM
Subject:Re: [openstack-dev] [Nova][Scheduler] Policy Based
Scheduler and Solver Scheduler
From: Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
...
There is an unexpected line break
From: Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
...
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: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver
Scheduler
Hi Khanh-Toan,
I only have one comment on your proposal : why are you proposing something new
for overcommitments with aggregates while the AggregateCoreFilter [1] and
AggregateRAMFilter [2]already exist, which
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
The solver-scheduler is designed to solve for an arbitrary list of instances of
different flavors. We need to have some updated apis in the scheduler to be
able to pass on such requests. Instance group api is an initial effort to
specify such groups.
Even now the existing solver scheduler
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
-Message d'origine-
De : Khanh-Toan Tran [mailto:khanh-toan.t...@cloudwatt.com]
Envoyé : mercredi 29 janvier 2014 13:25
À
Hi Khanh-Toan,
I only have one comment on your proposal : why are you proposing something
new for overcommitments with aggregates while the AggregateCoreFilter [1]
and AggregateRAMFilter [2]already exist, which AIUI provide same feature ?
I'm also concerned about the scope of changes for
/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
on this approach.
Regards,
Gil
From: Khanh-Toan Tran khanh-toan.t...@cloudwatt.com
To: OpenStack Development Mailing List \(not for usage questions\)
openstack-dev@lists.openstack.org,
Date: 01/30/2014 01:43 PM
Subject:Re: [openstack-dev] [Nova][Scheduler] Policy Based
Scheduler
: Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver
Scheduler
Hi Khanh-Toan,
I only have one comment on your proposal : why are you proposing something new
for overcommitments with aggregates while the AggregateCoreFilter [1] and
AggregateRAMFilter [2]already exist, which
23 matches
Mail list logo
