[kolla-ansible] [nova] Database connection points to nova cell db
Hi, In Kolla-Ansible deployments, the connection parameter under the [database] section in the nova.conf template points to the *nova_cell* database [1] <https://opendev.org/openstack/kolla-ansible/src/commit/4e3208b16c452d1cf2cd38392774ae0935e1b0ae/ansible/roles/nova/templates/nova.conf.j2#L94>. As far as I understand, the *nova_cell* database is primarily used to store failed operations. I was wondering: if we are not using a multi-cell architecture, should the connection instead point directly to the *nova* database rather than *nova_cell*? There was an open bug related to this issue almost a year ago, but it has not received any updates yet [2] <https://bugs.launchpad.net/kolla-ansible/+bug/2088264>. Could you please confirm whether the current configuration is correct? We have deployed OpenStack using the existing configuration and it is currently running in production. If we change the database connection in the running environment, would that cause any issues? Thank you for your time and assistance. Best regards, İzzettin
On 22/10/2025 12:37, İzzettin Erdem wrote:
Hi,
In Kolla-Ansible deployments, the |connection| parameter under the |[database]| section in the |nova.conf| template points to the *nova_cell* database [1] <https://opendev.org/openstack/kolla-ansible/src/commit/4e3208b16c452d1cf2cd38392774ae0935e1b0ae/ansible/roles/nova/templates/nova.conf.j2#L94>. As far as I understand, the *nova_cell* database is primarily used to store failed operations.
so to be clear as of the intoduction fo cells v2 in pike? rocky? whenever we made it required ther is no such thing as a signle cell nova deployment you always ahve cell_0 and at least 1 addtional cell. cell_0 is used for instance that pass the api checks but cannot be scheduled to any host but its also used to store teh service records for top level services like the schduler. last time i checked kolla-ansible correctly deploy nova and the conenction infromation was rednerd properly. looking at https://bugs.launchpad.net/kolla-ansible/+bug/2088264 the bug seams invlid the api should be using cell0 not 1 you shoudl have all 3 dbs (api, cell_0 and nova is "cell_1") the fact your cell1 does not have a name is a little od but the name is just for humans internally nova usess the uuid for all joins across tables if we look at devstack https://zuul.opendev.org/t/openstack/build/98bba2ae8bd74b4e93817cf77d2cff9f/... or redhats new operator based installer we generate the connection url here https://github.com/openstack-k8s-operators/nova-operator/blob/main/templates... https://github.com/openstack-k8s-operators/nova-operator/blob/main/controlle... https://github.com/openstack-k8s-operators/nova-operator/blob/main/test/func... so kolla is correctly deploying the nova api with the database connection url pointing at cell 0
I was wondering: if we are not using a multi-cell architecture, should the connection instead point directly to the *nova* database rather than *nova_cell*?
There was an open bug related to this issue almost a year ago, but it has not received any updates yet [2] <https://bugs.launchpad.net/kolla-ansible/+bug/2088264>.
Could you please confirm whether the current configuration is correct? We have deployed OpenStack using the existing configuration and it is currently running in production. If we change the database connection in the running environment, would that cause any issues?
Thank you for your time and assistance.
Best regards, İzzettin
participants (2)
-
İzzettin Erdem
-
Sean Mooney