Hi,
On a multi-node setup, I set cpu_allocation_ration to 1.0 on the node
running nova scheduler but cpu allocations still overcommitted. How can I
force nova not to all overtimed?
thanks
Barrow
___
Mailing list: http://lists.openstack.org/cg
On 08/20/2015 10:39 AM, J-P Methot wrote:
Hi,
I've made a custom centos 6.7 image on a proxmox with kvm hypervisor
with the goal of using it with openstack. I setup all the necessary
cloud-init packages that are needed by openstack. Everything seems to
work fine on openstack, except that the dri
Thanks Mike,
That's exactly what it was, ALTERed the DB to have CHARACTER SET utf8
COLLATE utf8_unicode_ci and all the tables to explicitly have the same
& then
ALTER TABLE $table CONVERT TO CHARACTER SET utf8 COLLATE utf8_unicode_ci;
for each table, it was well smacked down & migration complet
Hi,
I've made a custom centos 6.7 image on a proxmox with kvm hypervisor
with the goal of using it with openstack. I setup all the necessary
cloud-init packages that are needed by openstack. Everything seems to
work fine on openstack, except that the drive speed in fio is about 50%
of what I can a
Check that both tables are set to the same collation (InnoDB, etc.) Several of
us have seen this same thing on foreign keys, and it’s because of a collation
mismatch between the tables.
On 8/20/15, 9:25 AM, "Jonathan Proulx" wrote:
>H i All,
>
>I'm hitting a DB migration error while attem
H i All,
I'm hitting a DB migration error while attempting a production upgrade
(despite having successfully ruin the same upgrade on an only slightly
older copy of the database last week)
in:
INFO [alembic.migration] Running upgrade 38495dc99731 -> 4dbe243cd84d, nsxv
Failing:
sqlalchemy.exc.Op
