)]}'
{"specs/newton/approved/host-memory-metrics.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"3bff767fc3f8969261788689c4718456c3b7ccec","unresolved":false,"context_lines":[{"line_number":34,"context_line":"Proposed change"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"The existing Nova metric framework will be leveraged for this. Specifically,"},{"line_number":38,"context_line":"a new MemoryMonitor monitor will be created. The memory monitor will call"},{"line_number":39,"context_line":"a new virt driver method (i.e., get_host_memory_stats) to retrieve the"},{"line_number":40,"context_line":"memory utilization data for the respective hypervisor; this follows the same"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_64a54503","line":37,"range":{"start_line":37,"start_character":18,"end_line":37,"end_character":24},"updated":"2016-03-11 20:00:28.000000000","message":"Is it \u0027metric\u0027 or \u0027metrics\u0027?  Should it be the same throughout?","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":7664,"name":"Joe Cropper","email":"jwcroppe@us.ibm.com","username":"jwcroppe"},"change_message_id":"840eb3fbec541bc6e72cf2ba803dead317f65283","unresolved":false,"context_lines":[{"line_number":34,"context_line":"Proposed change"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"The existing Nova metric framework will be leveraged for this. Specifically,"},{"line_number":38,"context_line":"a new MemoryMonitor monitor will be created. The memory monitor will call"},{"line_number":39,"context_line":"a new virt driver method (i.e., get_host_memory_stats) to retrieve the"},{"line_number":40,"context_line":"memory utilization data for the respective hypervisor; this follows the same"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_43311ca2","line":37,"range":{"start_line":37,"start_character":18,"end_line":37,"end_character":24},"in_reply_to":"3afc51ec_64a54503","updated":"2016-03-11 21:37:42.000000000","message":"Done","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"3bff767fc3f8969261788689c4718456c3b7ccec","unresolved":false,"context_lines":[{"line_number":38,"context_line":"a new MemoryMonitor monitor will be created. The memory monitor will call"},{"line_number":39,"context_line":"a new virt driver method (i.e., get_host_memory_stats) to retrieve the"},{"line_number":40,"context_line":"memory utilization data for the respective hypervisor; this follows the same"},{"line_number":41,"context_line":"design precedent that the existing CPU monitor follows in that is calls the"},{"line_number":42,"context_line":"get_host_cpu_stats() driver method."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"A reference implementation will be provided for the libvirt driver, which"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_647c2573","line":41,"range":{"start_line":41,"start_character":63,"end_line":41,"end_character":65},"updated":"2016-03-11 20:00:28.000000000","message":"it","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":7664,"name":"Joe Cropper","email":"jwcroppe@us.ibm.com","username":"jwcroppe"},"change_message_id":"840eb3fbec541bc6e72cf2ba803dead317f65283","unresolved":false,"context_lines":[{"line_number":38,"context_line":"a new MemoryMonitor monitor will be created. The memory monitor will call"},{"line_number":39,"context_line":"a new virt driver method (i.e., get_host_memory_stats) to retrieve the"},{"line_number":40,"context_line":"memory utilization data for the respective hypervisor; this follows the same"},{"line_number":41,"context_line":"design precedent that the existing CPU monitor follows in that is calls the"},{"line_number":42,"context_line":"get_host_cpu_stats() driver method."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"A reference implementation will be provided for the libvirt driver, which"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_632c184b","line":41,"range":{"start_line":41,"start_character":63,"end_line":41,"end_character":65},"in_reply_to":"3afc51ec_647c2573","updated":"2016-03-11 21:37:42.000000000","message":"Done","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"3bff767fc3f8969261788689c4718456c3b7ccec","unresolved":false,"context_lines":[{"line_number":59,"context_line":"  Represents the total physical memory available (MBs)"},{"line_number":60,"context_line":"* Add MEMORY_USED"},{"line_number":61,"context_line":"  Represents the actual amount of memory that is being used on the host (MBs)"},{"line_number":62,"context_line":"* Add MEMORY_PERCENT"},{"line_number":63,"context_line":"  Represents the host\u0027s overall memory utilization %; value is within the range"},{"line_number":64,"context_line":"  [0.0, 1.0]"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"No database changes will be necessary for this as these new metrics just align"},{"line_number":67,"context_line":"with the existing metrics data model."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_c48d397d","line":64,"range":{"start_line":62,"start_character":0,"end_line":64,"end_character":12},"updated":"2016-03-11 20:00:28.000000000","message":"Seems like a thing called \"percent\" should be between zero and 100.  Are we following a precedent here, or can we make it make sense?","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":7664,"name":"Joe Cropper","email":"jwcroppe@us.ibm.com","username":"jwcroppe"},"change_message_id":"840eb3fbec541bc6e72cf2ba803dead317f65283","unresolved":false,"context_lines":[{"line_number":59,"context_line":"  Represents the total physical memory available (MBs)"},{"line_number":60,"context_line":"* Add MEMORY_USED"},{"line_number":61,"context_line":"  Represents the actual amount of memory that is being used on the host (MBs)"},{"line_number":62,"context_line":"* Add MEMORY_PERCENT"},{"line_number":63,"context_line":"  Represents the host\u0027s overall memory utilization %; value is within the range"},{"line_number":64,"context_line":"  [0.0, 1.0]"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"No database changes will be necessary for this as these new metrics just align"},{"line_number":67,"context_line":"with the existing metrics data model."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_43d8fc53","line":64,"range":{"start_line":62,"start_character":0,"end_line":64,"end_character":12},"in_reply_to":"3afc51ec_c48d397d","updated":"2016-03-11 21:37:42.000000000","message":"While I agree with the sentiment on this, we\u0027re following a precedent on this which was set forth for the previously defined CPU utilization % metrics.","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"3bff767fc3f8969261788689c4718456c3b7ccec","unresolved":false,"context_lines":[{"line_number":158,"context_line":"History"},{"line_number":159,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Optional section for Mitaka intended to be used each time the spec"},{"line_number":162,"context_line":"is updated to describe new design, API or any database schema"},{"line_number":163,"context_line":"updated. Useful to let reader understand what\u0027s happened along the"},{"line_number":164,"context_line":"time."},{"line_number":165,"context_line":""},{"line_number":166,"context_line":".. list-table:: Revisions"},{"line_number":167,"context_line":"   :header-rows: 1"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_44464924","line":164,"range":{"start_line":161,"start_character":0,"end_line":164,"end_character":5},"updated":"2016-03-11 20:00:28.000000000","message":"Looks like boilerplate/template language that needs to be removed?","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":7664,"name":"Joe Cropper","email":"jwcroppe@us.ibm.com","username":"jwcroppe"},"change_message_id":"840eb3fbec541bc6e72cf2ba803dead317f65283","unresolved":false,"context_lines":[{"line_number":158,"context_line":"History"},{"line_number":159,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Optional section for Mitaka intended to be used each time the spec"},{"line_number":162,"context_line":"is updated to describe new design, API or any database schema"},{"line_number":163,"context_line":"updated. Useful to let reader understand what\u0027s happened along the"},{"line_number":164,"context_line":"time."},{"line_number":165,"context_line":""},{"line_number":166,"context_line":".. list-table:: Revisions"},{"line_number":167,"context_line":"   :header-rows: 1"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3afc51ec_c3488c30","line":164,"range":{"start_line":161,"start_character":0,"end_line":164,"end_character":5},"in_reply_to":"3afc51ec_44464924","updated":"2016-03-11 21:37:42.000000000","message":"Done","commit_id":"030b5c402c74c5a2a652fa7d4b27ec4c2087e268"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"69e6fae766dc75b31ade307a063a11b7a5a8a46f","unresolved":false,"context_lines":[{"line_number":59,"context_line":"  Represents the total physical memory available (MBs)"},{"line_number":60,"context_line":"* Add MEMORY_USED"},{"line_number":61,"context_line":"  Represents the actual amount of memory that is being used on the host (MBs)"},{"line_number":62,"context_line":"* Add MEMORY_PERCENT"},{"line_number":63,"context_line":"  Represents the host\u0027s overall memory utilization %; value is within the range"},{"line_number":64,"context_line":"  [0.0, 1.0] (i.e., this follows the precedent already defined by the CPU"},{"line_number":65,"context_line":"  utilization % metrics)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"dab17558_703089e9","line":62,"range":{"start_line":62,"start_character":2,"end_line":62,"end_character":20},"updated":"2016-05-12 09:55:21.000000000","message":"Do we need to have 3 new fields? One can always be calculated from the others two.","commit_id":"9a67987a1500389dfff73bff29e4b2730f622620"}]}