Closed Pcolar closed 6 years ago
CSV file has the date of the last check for each object. CSV is a data base, refreshed as often as scheduled.
Response from Jon:
The audit was being generated hourly in test, which no longer exists. In production, it is generated weekly.
As far as "how Libnova should check it" seems to be a Libnova issue. The audit files have timestamps, so they can check the directory periodically for new files, and consume them however they want. It is their responsibility to delete them after they are done with them.
Here are some links to documentation and discussion regarding the audit:
https://github.com/oxsdd/ucm-dpn/blob/master/ingest-specification-draft1.md#audit - describes the agreed-upon audit function and establishes weekly frequency as a possibility.
https://github.com/oxsdd/ucm-dpn/#latest-news - indicates that it is generated weekly in production.
https://github.com/oxsdd/ucm-dpn/issues/2#issuecomment-382810684 - detailed response to LibNova's question on the audit function.
I checked the production UCM audit folder, and the UCM audit CSV files are there. They are empty, since no data has been ingested into the production UCM instance. There are four weeks worth of audit files in the directory. It's unclear whether Exanode has processed them yet; it is supposed to delete the files after consumption. As described elsewhere, the audit files are just a point-in-time dump of the UCM metadata. What fields are included in the audit is controlled by the .conf
file in the audit directory.
Creating the file weekly (every 7 days) is sufficient for DPN purposes. How does this affect EXANode status?
resolved with 7 day status generation.
What is the specification of this value? Where is it stored and can it be modified by a system administrator?
Every pre-determined number of days (as agreed by the USC and the DPN), the USC places a CSV file in the interchange folder.