On 11/12/2015 5:34 PM, Joshua Harlow wrote:
Ok, so the following is starting to form:
https://etherpad.openstack.org/p/remote-conductor-performance
Hopefully we can get to the bottom of this (especially for clouds that
run a large amount of computes in a single cell/only one cell).
Andrew La
Folks,
we'll take a look if we have observed this issue during MOS testing on 200
nodes lab. Sadly I do not remember this pattern being seen, although we do
not keep lots of the VMs for a long time during the synthetic tests.
Cheers,
Dina
On Fri, Nov 13, 2015 at 2:34 AM, Joshua Harlow
wrote:
>
Ok, so the following is starting to form:
https://etherpad.openstack.org/p/remote-conductor-performance
Hopefully we can get to the bottom of this (especially for clouds that
run a large amount of computes in a single cell/only one cell).
Andrew Laski wrote:
On 11/12/15 at 10:53am, Clint Byr
On 11/12/15 at 10:53am, Clint Byrum wrote:
Excerpts from Joshua Harlow's message of 2015-11-12 10:35:21 -0800:
Mike Dorman wrote:
> We do have a backlog story to investigate this more deeply, we just have not
had the time to do it yet. For us, it’s been easier/faster to add more hardware
to c
Excerpts from Joshua Harlow's message of 2015-11-12 10:35:21 -0800:
> Mike Dorman wrote:
> > We do have a backlog story to investigate this more deeply, we just have
> > not had the time to do it yet. For us, it’s been easier/faster to add more
> > hardware to conductor to get over the hump temp
Mike Dorman wrote:
We do have a backlog story to investigate this more deeply, we just have not
had the time to do it yet. For us, it’s been easier/faster to add more
hardware to conductor to get over the hump temporarily.
We kind of have that work earmarked for after the Liberty upgrade, in
We do have a backlog story to investigate this more deeply, we just have not
had the time to do it yet. For us, it’s been easier/faster to add more
hardware to conductor to get over the hump temporarily.
We kind of have that work earmarked for after the Liberty upgrade, in hopes
that maybe it’
On 11/12/2015 8:15 AM, Andrew Laski wrote:
On 11/12/15 at 09:31pm, Yaguang Tang wrote:
There are still performance issue in large deployment to use
nova-conductor, how do we make this decision to deprecate local mode?
I see
the patch is merged only three days after submit.
There is no timeli
On 11/12/15 at 09:31pm, Yaguang Tang wrote:
There are still performance issue in large deployment to use
nova-conductor, how do we make this decision to deprecate local mode? I see
the patch is merged only three days after submit.
There is no timeline for removal of local mode at this time for
There are still performance issue in large deployment to use
nova-conductor, how do we make this decision to deprecate local mode? I see
the patch is merged only three days after submit.
On Thu, Nov 12, 2015 at 10:51 AM, Matt Riedemann wrote:
> Details are in the change:
>
> https://review.opens
Details are in the change:
https://review.openstack.org/#/c/242168/
--
Thanks,
Matt Riedemann
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
11 matches
Mail list logo
