Open Stack

On 9/7/19 6:09 AM, Matt Riedemann wrote:
> On 9/6/2019 6:59 PM, melanie witt wrote:
>>
>> * If Telemetry is no longer using the server usage audit log API, we 
>> deprecate it in Nova and notify deployment tools to stop setting 
>> [DEFAULT]/instance_usage_audit = true to prevent further creation of 
>> nova.task_log records and recommend manual cleanup by users
> 
> Deprecating the API would just be a signal to not develop new tools 
> based on it since it's effectively unmaintained but that doesn't mean we 
> can remove it since there could be non-Telemtry tools in the wild using 
> it that we'd never hear about. You might not be suggesting an eventual 
> path to removal of the API, I'm just bringing that part up since I'm 
> sure people are thinking it.
> 
> I'm also assuming that API isn't multi-cell aware, meaning it won't 
> traverse cells pulling records like listing servers or migration resources.
> 
> As for the config option to run the periodic task that creates these 
> records, that's disabled by default so deployment tools shouldn't be 
> enabling it by default - but maybe some do if they are configured to 
> deploy ceilometer.

Indeed, tripleo enables the periodic task when deploying Telemetry, 
which is how we have customers hitting the unbounded nova.task_log table 
growth problem.

>>
>> or
>>
>> * If Telemetry is still using the server usage audit log API, we 
>> create a new 'nova-manage db purge_task_log --before <date>' (or 
>> similar) command that will hard delete nova.task_log records before a 
>> specified date or all if --before is not specified
> 
> If you can't remove the API then this is probably something that needs 
> to happen regardless, though we likely won't know if anyone uses it. I'd 
> consider it pretty low priority given how extremely latent this is and 
> would expect anyone that's been running with this enabled in production 
> has developed DB purge scripts for this table long ago.

Yeah, based on Tim Bell's reply later in this thread, we can't remove 
the API (tools in the wild using it). So, I'll propose a new nova-manage 
command because we don't appear to have a standard way of cleaning up 
nova.task_log records for customers either, yet.

-melanie