)]}'
{"specs/liberty/dbaas-notifications.rst":[{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"f9e50674939b33821d8c6dc8fb6c436b7f1a25ad","unresolved":false,"context_lines":[{"line_number":104,"context_line":"and audit_period_ending for each exists event will be used to compute the uptime"},{"line_number":105,"context_line":"hours"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"A counter type - database can be used to associate the trove samples"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Add a new listener class - TroveMetricsNotificationBase that extends"},{"line_number":110,"context_line":"plugin.NotificationBase for DBaaS service to transform Trove event data"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_2471760f","line":107,"range":{"start_line":107,"start_character":17,"end_line":107,"end_character":25},"updated":"2015-06-18 06:04:29.000000000","message":"what is the meter that you will be creating? database.uptime?","commit_id":"483aa9d17a95bc19c1732412dabe3cab67807c04"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"f9e50674939b33821d8c6dc8fb6c436b7f1a25ad","unresolved":false,"context_lines":[{"line_number":162,"context_line":"Other deployer impact"},{"line_number":163,"context_line":"---------------------"},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"None."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"Developer impact"},{"line_number":168,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_446cba34","line":165,"range":{"start_line":165,"start_character":4,"end_line":165,"end_character":5},"updated":"2015-06-18 06:04:29.000000000","message":"enable Trove exchange","commit_id":"483aa9d17a95bc19c1732412dabe3cab67807c04"},{"author":{"_account_id":13560,"name":"Rohit Jaiswal","email":"rohit.jaiswal@gmail.com","username":"rjaiswal"},"change_message_id":"2bae713232356a8098d076294c14f2e816dbf08d","unresolved":false,"context_lines":[{"line_number":104,"context_line":"and audit_period_ending for each exists event will be used to compute the uptime"},{"line_number":105,"context_line":"hours"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"A counter type - database can be used to associate the trove samples"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Add a new listener class - TroveMetricsNotificationBase that extends"},{"line_number":110,"context_line":"plugin.NotificationBase for DBaaS service to transform Trove event data"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_bc11fa53","line":107,"updated":"2015-06-18 19:42:00.000000000","message":"gordc: Its not completely clear as to what all meters we need from Trove, but yes, this is one which we need to begin with.","commit_id":"41c69fb67a9807f2e5e164d2600fc6689f91fc21"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"5edbd293bf5840a410ccec0d3dbd071bf899b11a","unresolved":false,"context_lines":[{"line_number":199,"context_line":"There could be new types of notifications when new resource types are added"},{"line_number":200,"context_line":"or new features are supported like backup/restore, patching, monitoring etc."},{"line_number":201,"context_line":""},{"line_number":202,"context_line":"When Trove confirms with the PaaS event format, the field mappings for integrated"},{"line_number":203,"context_line":"events will need to be refactored to adjust to the new event format."},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"With the impending move towards declarative metering in Ceilometer, the proposed"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_36c73066","line":202,"updated":"2015-06-19 09:47:11.000000000","message":"conforms","commit_id":"41c69fb67a9807f2e5e164d2600fc6689f91fc21"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"5edbd293bf5840a410ccec0d3dbd071bf899b11a","unresolved":false,"context_lines":[{"line_number":204,"context_line":""},{"line_number":205,"context_line":"With the impending move towards declarative metering in Ceilometer, the proposed"},{"line_number":206,"context_line":"notification plugin for Trove will become redundant/deprecated and replaced with"},{"line_number":207,"context_line":"declarative meter definitions."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"Dependencies"},{"line_number":210,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_f69f8863","line":207,"updated":"2015-06-19 09:47:11.000000000","message":"I was getting ready to leave a comment to this effect but you already did it :)","commit_id":"41c69fb67a9807f2e5e164d2600fc6689f91fc21"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"8ec7a4bf4e325db64ba27e316e5f086218663bc1","unresolved":false,"context_lines":[{"line_number":104,"context_line":"and audit_period_ending for each exists event will be used to compute the uptime"},{"line_number":105,"context_line":"hours"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"A counter type - database can be used to associate the trove samples"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Add a new listener class - TroveMetricsNotificationBase that extends"},{"line_number":110,"context_line":"plugin.NotificationBase for DBaaS service to transform Trove event data"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_eb9433e9","line":107,"updated":"2015-06-22 15:26:10.000000000","message":"can we add the initial meter just for reference? or is this completely separate from bp?","commit_id":"cf276b089c7d955621ee1d3a94af8e3cfefc6cf0"},{"author":{"_account_id":13560,"name":"Rohit Jaiswal","email":"rohit.jaiswal@gmail.com","username":"rjaiswal"},"change_message_id":"5920e66892f8522ae1776f2c3643d4ded65c1348","unresolved":false,"context_lines":[{"line_number":104,"context_line":"and audit_period_ending for each exists event will be used to compute the uptime"},{"line_number":105,"context_line":"hours"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"A counter type - database can be used to associate the trove samples"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Add a new listener class - TroveMetricsNotificationBase that extends"},{"line_number":110,"context_line":"plugin.NotificationBase for DBaaS service to transform Trove event data"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_9d84860b","line":107,"in_reply_to":"fa32b979_eb9433e9","updated":"2015-06-23 21:40:05.000000000","message":"@gordc: At this point, Trove is not yet including the audit_period_beginning and audit_period_ending attributes in their trove.instance.exists event, which are used to determine the uptime metric value.  If we add this in the bp, the implementation will not be ready until Trove sends the above attributes in the exists event.","commit_id":"cf276b089c7d955621ee1d3a94af8e3cfefc6cf0"}]}