openstack/nova
Code Issues Proposed changes

Correct reno for archiving task_log database records

Browse Source 
The release note incorrectly stated that the Telemetry service calls
the /os-instance_usage_audit_log REST API to retrieve instance usage
data. Telemetry rather consumes the notifications that are only generated
when [DEFAULT]instance_usage_audit=True.

Related-Bug: #1877189

Change-Id: Iea358090c42877bedfdcc4a04019f6dc406176c2
This commit is contained in:
melanie witt 2021-07-16 21:53:38 +00:00
parent 3545356ae3
commit d093849c3c
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
releasenotes/notes/archive-task-logs-fa9dd7c5859b5e30.yaml
View File

@ -11,8 +11,11 @@ features:
The ``task_log`` database table contains instance usage audit records if
``nova-compute`` has been configured with ``[DEFAULT]instance_usage_audit =
True``. This will be the case if OpenStack Telemetry is being used in the
deployment, as the option causes Nova to generate audit data that Telemetry
then retrieves from the server usage audit log API [1].
deployment, as the option causes Nova to generate audit notifications that
Telemetry consumes from the message bus.
Usage data can also be later retrieved by calling the
``/os-instance_usage_audit_log`` REST API [1].
Historically, there has been no way to delete ``task_log`` table records
other than manual database modification. Because of this, ``task_log``