- Original Message -
> From: "Attila Fazekas"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, March 10, 2015 12:48:00 PM
> Subject: Re: [openstack-dev] [nova] blueprint about multiple wor
- Original Message -
> From: "Nikola Đipanov"
> To: openstack-dev@lists.openstack.org
> Sent: Tuesday, March 10, 2015 10:53:01 AM
> Subject: Re: [openstack-dev] [nova] blueprint about multiple workers
> supported in nova-scheduler
>
> On 03/06/2015
- Original Message -
> From: "Jay Pipes"
> To: openstack-dev@lists.openstack.org
> Sent: Wednesday, March 4, 2015 9:22:43 PM
> Subject: Re: [openstack-dev] [nova] blueprint about multiple workers
> supported in nova-scheduler
>
> On 03/04/2015 01:51 A
On 03/06/2015 03:19 PM, Attila Fazekas wrote:
> Looks like we need some kind of _per compute node_ mutex in the critical
> section,
> multiple scheduler MAY be able to schedule to two compute node at same time,
> but not for scheduling to the same compute node.
>
> If we don't want to introduce a
Hi, just some oslo.messaging thoughts about having multiple
nova-scheduler processes (can also apply to any other daemon acting as
rpc server),
nova-scheduler use service.Service.create() to create a rpc server, that
one is identified by a 'topic' and a 'server' (the
oslo.messaging.Target).
- Original Message -
> From: "Attila Fazekas"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Friday, March 6, 2015 4:19:18 PM
> Subject: Re: [openstack-dev] [nova] blueprint about multiple workers
> supported in
v@lists.openstack.org
> Sent: Friday, March 6, 2015 10:29:52 AM
> Subject: Re: [openstack-dev] [nova] blueprint about multiple workers
> supported in nova-scheduler
>
> On 03/06/2015 01:56 AM, Rui Chen wrote:
> > Thank you very much for in-depth discussion about this topic, @Niko
On 03/06/2015 01:56 AM, Rui Chen wrote:
> Thank you very much for in-depth discussion about this topic, @Nikola
> and @Sylvain.
>
> I agree that we should solve the technical debt firstly, and then make
> the scheduler better.
>
That was not necessarily my point.
I would be happy to see work on
Thank you very much for in-depth discussion about this topic, @Nikola and
@Sylvain.
I agree that we should solve the technical debt firstly, and then make the
scheduler better.
Best Regards.
2015-03-05 21:12 GMT+08:00 Sylvain Bauza :
>
> Le 05/03/2015 13:00, Nikola Đipanov a écrit :
>
> On 03/
Le 05/03/2015 13:00, Nikola Đipanov a écrit :
On 03/04/2015 09:23 AM, Sylvain Bauza wrote:
Le 04/03/2015 04:51, Rui Chen a écrit :
Hi all,
I want to make it easy to launch a bunch of scheduler processes on a
host, multiple scheduler workers will make use of multiple processors
of host and enh
On 03/04/2015 09:23 AM, Sylvain Bauza wrote:
>
> Le 04/03/2015 04:51, Rui Chen a écrit :
>> Hi all,
>>
>> I want to make it easy to launch a bunch of scheduler processes on a
>> host, multiple scheduler workers will make use of multiple processors
>> of host and enhance the performance of nova-sch
spent the past several months adding
>>>> features directly to SQLAlchemy that allow an ORM-based app to have
>>>> routes
>>>> to operations that perform just as fast as that of Core without a
>>>> rewrite of
>>>> code.
>>>>
>
>> To: "OpenStack Development Mailing List (not for usage
questions)" mailto:openstack-dev@lists.openstack.org>>
>> Sent: Wednesday, March 4, 2015 4:51:07 AM
>> Subject: [openstack-dev] [nova] blueprint about
The scheduler does lot of thing in the application, like filtering
>>> > what can be done on the DB level more efficiently. Why it is not done
>>> > on the DB side ?
>>> >
>>> > There are use cases when the scheduler would need to know even more
>
ng` in all schedulers process
>> memory up-to-date ?
>> > (Maybe zookeeper)
>> >
>> > The opposite way would be to move most operation into the DB side,
>> > since the DB already knows everything.
>> > (stored procedures ?)
>> >
>> &g
> since the DB already knows everything.
> > (stored procedures ?)
> >
> > Best Regards,
> > Attila
> >
> >
> > - Original Message -
> >> From: "Rui Chen"
> >> To: "OpenStack Development Mailing List (not for usage qu
res ?)
>
> Best Regards,
> Attila
>
>
> - Original Message -
>> From: "Rui Chen"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Sent: Wednesday, March 4, 2015 4:51:07 AM
>> Subject: [openstack-d
March 4, 2015 4:51:07 AM
Subject: [openstack-dev] [nova] blueprint about multiple workers supported
in nova-scheduler
Hi all,
I want to make it easy to launch a bunch of scheduler processes on a host,
multiple scheduler workers will make use of multiple processors of host and
enhance the perfo
nesday, March 4, 2015 4:51:07 AM
> Subject: [openstack-dev] [nova] blueprint about multiple workers supported
> in nova-scheduler
>
> Hi all,
>
> I want to make it easy to launch a bunch of scheduler processes on a host,
> multiple scheduler workers will make use of multipl
Le 04/03/2015 04:51, Rui Chen a écrit :
Hi all,
I want to make it easy to launch a bunch of scheduler processes on a
host, multiple scheduler workers will make use of multiple processors
of host and enhance the performance of nova-scheduler.
I had registered a blueprint and commit a patch t
Hi all,
I want to make it easy to launch a bunch of scheduler processes on a host,
multiple scheduler workers will make use of multiple processors of host and
enhance the performance of nova-scheduler.
I had registered a blueprint and commit a patch to implement it.
https://blueprints.launchpad.n
21 matches
Mail list logo
