)]}'
{"specs/kilo/fine_grained_retention_policy.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"b618663ca052885d721b5c853057916aa53939d7","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"It is possible to leverage the current ceilometer-expirer code to read the"},{"line_number":38,"context_line":"configuration or pipeline file and selectively delete Samples and Meters"},{"line_number":39,"context_line":"from the database."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Alternatives"},{"line_number":42,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baa201ad_297de51c","line":39,"updated":"2014-10-14 21:13:38.000000000","message":"I can understand the tempatation of using the pipeline file to control this sort of thing: it\u0027s convenient and has a related purpose. I fear, however, that we can end up with an overloaded file that becomes a bit inscrutable.\n\nI don\u0027t have a good alternative to suggest.","commit_id":"ade1db1a61dc98f40c86c6e27a3a8a091da6bcdf"},{"author":{"_account_id":7052,"name":"Fabio Giannetti","email":"fgiannet@cisco.com","username":"fabgia"},"change_message_id":"bb62c4076c3ba064299b91459e8c7cb8d91cde27","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"It is possible to leverage the current ceilometer-expirer code to read the"},{"line_number":38,"context_line":"configuration or pipeline file and selectively delete Samples and Meters"},{"line_number":39,"context_line":"from the database."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Alternatives"},{"line_number":42,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a8c0949_48ee0aee","line":39,"in_reply_to":"baa201ad_297de51c","updated":"2014-10-30 22:45:25.000000000","message":"Chris, I was following the path of least resistance from the working group.\nI think a valid and more comprehensive alternative is to write a retention-policy file. This could be done like a standard policy file where you specify the name of the meter and the lifespan associated with it.\nI would use the ISO 8601 that supports:\n\n    Start and end, such as \"2007-03-01T13:00:00Z/2008-05-11T15:30:00Z\"\n    Start and duration, such as \"2007-03-01T13:00:00Z/P1Y2M10DT2H30M\"\n    Duration and end, such as \"P1Y2M10DT2H30M/2008-05-11T15:30:00Z\"\n    Duration only, such as \"P1Y2M10DT2H30M\", with additional context information\n\nHTH, Fabio","commit_id":"ade1db1a61dc98f40c86c6e27a3a8a091da6bcdf"}]}