- Original Message -
> From: "Chris Friesen"
> To: openstack-operators@lists.openstack.org
>
> On 09/25/2015 12:34 PM, Steve Gordon wrote:
>
> > Nikola's reply got bounced because he isn't subscribed, but:
> >
> > """
> > Thanks Steve!
> >
> > So the below is likely the same root cause a
As Kris Lindgren noted, this has bit us big time. Defaults appear wrong,
desired behavior would be other than it is. I'm re-reading this entire
thread now (sorry for not weighing in earlier.)
On Fri, May 15, 2015 at 12:52 PM, Aubrey Wells
wrote:
> Greetings,
> Trying to decide if this is a bug o
On 09/25/2015 12:34 PM, Steve Gordon wrote:
Nikola's reply got bounced because he isn't subscribed, but:
"""
Thanks Steve!
So the below is likely the same root cause as this bug:
https://launchpad.net/bugs/1461777
Which has been fixed in Liberty and backported to stable/kilo (see
https://rev
This is a long-standing issue. Nikola has been working on it in Liberty for the
CPU pinning case, not sure about the non-pinned case. And of course patching
back to Kilo hasn't been done yet.
Aubrey, what you're seeing is definitely a bug. There is an existing bug
https://bugs.launchpad.net
- Original Message -
> From: "Kris G. Lindgren"
> To: "Steve Gordon" , "Aubrey Wells"
> , "David Medberry"
>
> I believe TWC - (medberry on irc) was lamenting to me about cpusets,
> different hypervisors HW configs, and unassigned vcpu's in numa nodes.
>
> The problem is the migration d
I believe TWC - (medberry on irc) was lamenting to me about cpusets, different
hypervisors HW configs, and unassigned vcpu's in numa nodes.
The problem is the migration does not re-define the domain.xml, specifically,
the vcpu mapping to match what makes sense on the new host. I believe the
is
Adding Nikola as he has been working on this.
- Original Message -
> From: "Aubrey Wells"
> To: openstack-operators@lists.openstack.org
>
> Greetings,
> Trying to decide if this is a bug or just a config option that I can't
> find. The setup I'm currently testing in my lab with is two co
Greetings,
Trying to decide if this is a bug or just a config option that I can't
find. The setup I'm currently testing in my lab with is two compute nodes
running Kilo, one has 40 cores (2x 10c with HT) and one has 16 cores (2x 4c
+ HT). I don't have any CPU pinning enabled in my nova config, whic
