I ran into the different core count thing a while back too and its not
fixed in Kilo (that's where I discovered it). I posted to the mailing list
and didn't get any feedback on it, but as I was just looking in the
archives to send you the link to the hack I found to fix it, I noticed that
it silent
ar
up the confusion?
[1] http://www.juniper.net/us/en/products-services/sdn/contrail/
[2] http://www.opencontrail.org/frequently-asked-questions-faq/
-
Aubrey Wells
Manager, Network Operations
Digium Cloud Services
Main: 888.305.3850
Support: 877.344.4861 or http://www.digiu
Minor, but "This bug report has been closed [...]" sounds much better than
"This bug report got closed [...]"
---------
Aubrey Wells
Manager, Network Operations
Digium Cloud Services
Main: 888.305.3850
Support: 877.344.4861 or http://www.digium.com/en/support
&l
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