efe64725e1
We're adding 2 services that are responsible for executing db purge and archive_deleted_rows. Services will be deployed by default, but left stopped/disabled. This way we allow deployers to enable/disable feature by changing value of nova_archive/purge_deleted. Otherwise, when variables set to true once, setting them to false won't lead to stopoing of DB trimming and that would need to be done manualy. Change-Id: I9f110f663fae71f5f3c01c6d09e6d1302d517466
20 lines
930 B
YAML
20 lines
930 B
YAML
---
|
|
features:
|
|
- |
|
|
Added option to periodically clean-up deleted records from Nova
|
|
database. Having a lot of records for the deleted instances affects
|
|
service performance.
|
|
With that 2 new services are being introduced: ``nova-archive-deleted``
|
|
and ``nova-purge-deleted`` that will be called periodically using
|
|
corresponsive systemd timers on the first nova-conductor host.
|
|
|
|
By default these services are disabled/stopped and database cleanup
|
|
is not performed. You can enable this behaviour by defining variables
|
|
``nova_archive_deleted`` and ``nova_purge_deleted``.
|
|
|
|
Service ``nova-archive-deleted`` will execute
|
|
`nova-manage db archive_deleted_rows` while ``nova-archive-deleted``
|
|
will execute `nova-manage db purge`. Please correspond to nova-manage
|
|
documentation for more information on what these commands do:
|
|
https://docs.openstack.org/nova/latest/cli/nova-manage.html
|