Looking at the openstack-discuss thread, it seems that they need to keep it. I'm not aware of anything in starlingx that is looking at this API though the audit is enabled by default by openstack-helm nova. From the thread though, it does appear that there is no purge mechanism for the task_log table in nova. Prior to stx2.0, we had a stx-nova patch that would purge task_log table records older than 30 days. So I'm thinking we should pull in any upstream nova fix that is proposed for this or help create one. Gerry -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Friday, September 06, 2019 9:27 PM To: starlingx Subject: [Starlingx-discuss] [nova] server usage audit API I'm not sure how many folks here also follow the openstack-discuss list so I'm bringing some attention to this bit of API that the Nova team is considering deprecating. http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009199... melwitt> TL;DR: I have a question, does the Telemetry service (or any other service) still make use of the server usage audit log API in Nova [1]? Do any flock services use this API? If so we should head over to openstack-discuss and join the conversation. dt -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss