9a9a620ea2
When calling "nova-manage cell_v2 simple_cell_setup" or "nova-manage cell_v2 map_cell0" without passing in the --database_connection option, we read the [database]/connection URL from nova.conf, try to split the URL and then create a default connection based on the name of the original connection, so if you're cell database's name is 'nova' you'd end up with 'nova_cell0' for the cell0 database name in the URL. The problem is the database connection URL has credentials in the netloc and if the password has special characters in it, those can mess up the URL split, like splitting on ? which is normally denoting the beginning of the path in a URL. This change handles special characters in the password by using a nice DB connection URL parsing utility method available in sqlalchemy to get the database name out of the connection URL string so we can replace it properly with the _cell0 suffix. Adds a release note as this bug causes issues when upgrading. Change-Id: I7a7678e4af8160e6f48b96095154fca6ca48ff09 Closes-Bug: #1673613
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
https://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at: