Message-
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: December-16-15 10:20 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: s...@yahoo-inc.com
Subject: Re: [openstack-dev] [magnum] Magnum conductor async container
operations
On Dec 16, 2015, at 6:24 PM, Joshua H
Josh,
Thanks for bringing up this discussion. Modulo-hashing introduces a
possibility for 'window of inconsistency', and to address the dynamism
'consistent hashing' is better.
BUT, for the problem in hand I think modulo hashing is good enough, as
number of worker instances for conductor in
Josh,
You pointed out correct! magnum-conductor has monkey-patched code, so
the underlying thread module is actually using greenthread.
- I would use eventlet.greenthread explicitly, as that would enhance the
readability
- greenthread has a potential of not yielding by itself, if no i/o,
blocki
-dev] [magnum] Magnum conductor async container
operations
> On Dec 16, 2015, at 6:24 PM, Joshua Harlow wrote:
>
> SURO wrote:
>> Hi all,
>> Please review and provide feedback on the following design proposal
>> for implementing the blueprint[1] on async-container-op
SURO wrote:
Josh,
Please find my reply inline.
Regards,
SURO
irc//freenode: suro-patz
On 12/16/15 6:37 PM, Joshua Harlow wrote:
SURO wrote:
Hi all,
Please review and provide feedback on the following design proposal for
implementing the blueprint[1] on async-container-operations -
1. Magnu
On 12/16/15 11:39 PM, Joshua Harlow wrote:
SURO wrote:
Please find the reply inline.
Regards,
SURO
irc//freenode: suro-patz
On 12/16/15 7:19 PM, Adrian Otto wrote:
On Dec 16, 2015, at 6:24 PM, Joshua Harlow
wrote:
SURO wrote:
Hi all,
Please review and provide feedback on the following des
SURO wrote:
Please find the reply inline.
Regards,
SURO
irc//freenode: suro-patz
On 12/16/15 7:19 PM, Adrian Otto wrote:
On Dec 16, 2015, at 6:24 PM, Joshua Harlow
wrote:
SURO wrote:
Hi all,
Please review and provide feedback on the following design proposal for
implementing the blueprint[1
Josh,
Please find my reply inline.
Regards,
SURO
irc//freenode: suro-patz
On 12/16/15 6:37 PM, Joshua Harlow wrote:
SURO wrote:
Hi all,
Please review and provide feedback on the following design proposal for
implementing the blueprint[1] on async-container-operations -
1. Magnum-conductor w
Please find the reply inline.
Regards,
SURO
irc//freenode: suro-patz
On 12/16/15 7:19 PM, Adrian Otto wrote:
On Dec 16, 2015, at 6:24 PM, Joshua Harlow wrote:
SURO wrote:
Hi all,
Please review and provide feedback on the following design proposal for
implementing the blueprint[1] on async-co
> On Dec 16, 2015, at 6:24 PM, Joshua Harlow wrote:
>
> SURO wrote:
>> Hi all,
>> Please review and provide feedback on the following design proposal for
>> implementing the blueprint[1] on async-container-operations -
>>
>> 1. Magnum-conductor would have a pool of threads for executing the
>>
SURO wrote:
Hi all,
Please review and provide feedback on the following design proposal for
implementing the blueprint[1] on async-container-operations -
1. Magnum-conductor would have a pool of threads for executing the
container operations, viz. executor_threadpool. The size of the
executor_
SURO wrote:
Hi all,
Please review and provide feedback on the following design proposal for
implementing the blueprint[1] on async-container-operations -
1. Magnum-conductor would have a pool of threads for executing the
container operations, viz. executor_threadpool. The size of the
executor_th
12 matches
Mail list logo