This has been fixed by first checking whether the tables exist. As
a result, the upgrade from version 3 to version 4 succeeds even if
LoadBalancerPlugin is in use.
There are three known issues when upgrading version 3 to version 4
with LoadBalancer. They will be fixed in a future release.
1) Issue one is with respect to re-creating table 'vips'. This
will be fixed in a future release. To work around this issue run
the command:
neutron-db-manage --config-file /etc/neutron/neutron.conf --
config-file /etc/neutron/plugin.ini stamp f489cf14a79c
prior to the database upgrade.
2) The workaround for the second issue is renaming device_driver
path in /etc/neutron/lbaas-agent.ini from
quantum.plugins.services.agent_loadbalancer.drivers.haproxy.namesp
ace_driver.HaproxyNSDriver
to
neutron.services.loadbalancer.drivers.haproxy.namespace_driver.Ha
proxyNSDriver
3) To solve the third issue, the following command must be run in
the mysql command-line in neutron database:
INSERT INTO providerresourceassociations (resource_id,
provider_name) SELECT id, 'haproxy' FROM pools;
BZ #10789 9 9
This enhancement enables mysqld performance improvement if users
add the following configuration options to the /etc/my.cnf file:
innodb_buffer_pool_size = (10-20% of availble memory)
innodb_flush_method = O_DIRECT
innodb_file_per_table
These changes are expected to be implemented in the next release.
BZ #11024 6 6
It is recommended that you do not run sample scripts when
installing production systems. Sample scripts are for
demonstration and testing only. Specifically, the openstack-demo-
install script will create OpenStack Keystone accounts with
default credentials.
Kommentare zu diesen Handbüchern