)]}'
{"nova/compute/resource_tracker.py":[{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"5be9ee6e70063bd8b41e6fe6045329f62c32451f","unresolved":false,"context_lines":[{"line_number":63,"context_line":"]"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"allocation_ratio_opts \u003d ["},{"line_number":66,"context_line":"    cfg.FloatOpt("},{"line_number":67,"context_line":"        \u0027cpu_allocation_ratio\u0027,"},{"line_number":68,"context_line":"        default\u003d0.0,"},{"line_number":69,"context_line":"        help\u003d\u0027Virtual CPU to physical CPU allocation ratio which affects \u0027"},{"line_number":70,"context_line":"             \u0027all CPU filters. This configuration specifies a global ratio \u0027"}],"source_content_type":"text/x-python","patch_set":1,"id":"5a5ae5dd_4b81d04c","line":67,"range":{"start_line":66,"start_character":0,"end_line":67,"end_character":31},"updated":"2016-02-09 14:38:14.000000000","message":"This is an unrelated formatting change.","commit_id":"d41d6f8402ab017d5b501a2adcfb1173c661e506"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"5be9ee6e70063bd8b41e6fe6045329f62c32451f","unresolved":false,"context_lines":[{"line_number":73,"context_line":"             \u0027NOTE: This can be set per-compute, or if set to 0.0, the value \u0027"},{"line_number":74,"context_line":"             \u0027set on the scheduler node(s) will be used \u0027"},{"line_number":75,"context_line":"             \u0027and defaulted to 16.0\u0027),"},{"line_number":76,"context_line":"    cfg.FloatOpt("},{"line_number":77,"context_line":"        \u0027ram_allocation_ratio\u0027,"},{"line_number":78,"context_line":"        default\u003d0.0,"},{"line_number":79,"context_line":"        help\u003d\u0027Virtual ram to physical ram allocation ratio which affects \u0027"},{"line_number":80,"context_line":"             \u0027all ram filters. This configuration specifies a global ratio \u0027"}],"source_content_type":"text/x-python","patch_set":1,"id":"5a5ae5dd_ab8c0480","line":77,"range":{"start_line":76,"start_character":0,"end_line":77,"end_character":31},"updated":"2016-02-09 14:38:14.000000000","message":"This too.","commit_id":"d41d6f8402ab017d5b501a2adcfb1173c661e506"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"29eb0787a522dc4e2c02587d9522a62fd15f6a43","unresolved":false,"context_lines":[{"line_number":82,"context_line":"             \u0027set on the scheduler node(s) will be used \u0027"},{"line_number":83,"context_line":"             \u0027and defaulted to 1.5\u0027),"},{"line_number":84,"context_line":"    cfg.FloatOpt(\u0027disk_allocation_ratio\u0027,"},{"line_number":85,"context_line":"        default\u003d1.0,"},{"line_number":86,"context_line":"        help\u003d\u0027This is the virtual disk to physical disk allocation ratio used \u0027"},{"line_number":87,"context_line":"             \u0027by the disk_filter.py script to determine if a host has \u0027"},{"line_number":88,"context_line":"             \u0027sufficient disk space to fit a requested instance. A ratio \u0027"}],"source_content_type":"text/x-python","patch_set":3,"id":"5a5ae5dd_6b9e0309","line":85,"updated":"2016-02-09 16:56:51.000000000","message":"We have to default to 0.0 here, I think to make this all work.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1420a99e0bb75977440a5a58654b5ef0b542a769","unresolved":false,"context_lines":[{"line_number":82,"context_line":"             \u0027set on the scheduler node(s) will be used \u0027"},{"line_number":83,"context_line":"             \u0027and defaulted to 1.5\u0027),"},{"line_number":84,"context_line":"    cfg.FloatOpt(\u0027disk_allocation_ratio\u0027,"},{"line_number":85,"context_line":"        default\u003d1.0,"},{"line_number":86,"context_line":"        help\u003d\u0027This is the virtual disk to physical disk allocation ratio used \u0027"},{"line_number":87,"context_line":"             \u0027by the disk_filter.py script to determine if a host has \u0027"},{"line_number":88,"context_line":"             \u0027sufficient disk space to fit a requested instance. A ratio \u0027"}],"source_content_type":"text/x-python","patch_set":3,"id":"5a5ae5dd_862496af","line":85,"in_reply_to":"5a5ae5dd_6b9e0309","updated":"2016-02-09 17:00:22.000000000","message":"see:\nhttps://review.openstack.org/#/c/277934/1/nova/objects/compute_node.py","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"}],"releasenotes/notes/disk_ratio_to_rt-b6224ab8c0272d86.yaml":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"bcfab8d7500384548f9e436ea1a65ce2cfa0f636","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - Disk allocation ratio is now defined on the compute node namespace. You"},{"line_number":4,"context_line":"    need to ensure that the values are consistent across all your"},{"line_number":5,"context_line":"    compute nodes."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5a5ae5dd_0b466fbf","line":5,"updated":"2016-02-09 16:54:05.000000000","message":"I don\u0027t remember if thats how we did this last time.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"b2d1f4046323f6303bfdd0ba32763fa203bac852","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - Disk allocation ratio is now defined on the compute node namespace. You"},{"line_number":4,"context_line":"    need to ensure that the values are consistent across all your"},{"line_number":5,"context_line":"    compute nodes."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"3a57f1b5_8410e202","line":5,"in_reply_to":"3a57f1b5_24b6ce3d","updated":"2016-02-11 09:10:03.000000000","message":"Actually, thinking more of that, I feel that John is right.\n\nCurrently, the opt is checked by the n-sch process. By this change, it will still checked by the same process, it will just be defined in a different module but imported, so that\u0027s fine.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"6459a411943c290401f162fa01a260f74e062bba","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - Disk allocation ratio is now defined on the compute node namespace. You"},{"line_number":4,"context_line":"    need to ensure that the values are consistent across all your"},{"line_number":5,"context_line":"    compute nodes."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"3a57f1b5_24b6ce3d","line":5,"in_reply_to":"3a57f1b5_c1b7bef3","updated":"2016-02-11 09:06:29.000000000","message":"Good point Dan. Yeah the use of namespace is confusing.\n\nJohn, I feel we still somehow need to provide an explicit comment about asking to make sure the allocation ratios files are consistent across the cloud if we cut RC1 before we land the last patch.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"facfabd0bfe39ce0fb412e7da0dbe2334ec2c008","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - Disk allocation ratio is now defined on the compute node namespace. You"},{"line_number":4,"context_line":"    need to ensure that the values are consistent across all your"},{"line_number":5,"context_line":"    compute nodes."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"3a57f1b5_c1b7bef3","line":5,"in_reply_to":"5a5ae5dd_06c1862e","updated":"2016-02-10 22:58:51.000000000","message":"Also, I\u0027m not sure \"on compute node namespace\" is the right terminology here. Something like \"honored on the compute node instead of the scheduler node\" or something is what we want, right? The use of \"namespace\" implies it has moved to [compute] in the config or something.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1420a99e0bb75977440a5a58654b5ef0b542a769","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - Disk allocation ratio is now defined on the compute node namespace. You"},{"line_number":4,"context_line":"    need to ensure that the values are consistent across all your"},{"line_number":5,"context_line":"    compute nodes."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5a5ae5dd_c6784e92","line":5,"in_reply_to":"5a5ae5dd_0b466fbf","updated":"2016-02-09 17:00:22.000000000","message":"So I think you need to mention how the default config has changed, to allow for the transition to move the CONF to all the compute nodes.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"116cbf3b32b03421b4df7f3c48f342a8ac2cb50f","unresolved":false,"context_lines":[{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - Disk allocation ratio is now defined on the compute node namespace. You"},{"line_number":4,"context_line":"    need to ensure that the values are consistent across all your"},{"line_number":5,"context_line":"    compute nodes."}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5a5ae5dd_06c1862e","line":5,"in_reply_to":"5a5ae5dd_c6784e92","updated":"2016-02-09 17:05:47.000000000","message":"I don\u0027t think you need a reno note until the last patch, this one is misleading.","commit_id":"97219567c78dccfd6df1bbbcb0683db83de24aa9"}]}