)]}'
{"doc/source/admin/configuring-migrations.rst":[{"author":{"_account_id":25562,"name":"Chen","email":"dstbtgagt@foxmail.com","username":"chenn2"},"change_message_id":"fd360bba78a94b3fd786d0dcf445349844b01d4b","unresolved":false,"context_lines":[{"line_number":231,"context_line":"   example, shared-storage live migration of an instance with 8GiB memory will"},{"line_number":232,"context_line":"   time out after 6400 seconds."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"#. **Live migration progress timeout**"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"   The Compute service also aborts a live migration when it detects that memory"},{"line_number":237,"context_line":"   copy is not making progress for a certain time. You can set this time, in"},{"line_number":238,"context_line":"   seconds, through the configurable parameter"},{"line_number":239,"context_line":"   ``live_migration_progress_timeout``."},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   In Ocata, the default value of ``live_migration_progress_timeout`` is 0,"},{"line_number":242,"context_line":"   which disables progress timeouts. You should not change this value, since"},{"line_number":243,"context_line":"   the algorithm that detects memory copy progress has been determined to be"},{"line_number":244,"context_line":"   unreliable. It may be re-enabled in future releases."},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"#. **Instance downtime**"},{"line_number":247,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_c9b10147","side":"PARENT","line":244,"range":{"start_line":234,"start_character":0,"end_line":244,"end_character":55},"updated":"2018-09-10 14:17:56.000000000","message":"Sorry but I found it somewhat awkward that out of the 3 places only here the description for live_migration_progress_timeout is removed. Why can\u0027t we just attach the bug reference instead just like the other two?","commit_id":"3d31e6c95afe3dff01af037348c0c18e896970db"},{"author":{"_account_id":25562,"name":"Chen","email":"dstbtgagt@foxmail.com","username":"chenn2"},"change_message_id":"98f84d14eed535a0fedc235886afd244c4e77de0","unresolved":false,"context_lines":[{"line_number":231,"context_line":"   example, shared-storage live migration of an instance with 8GiB memory will"},{"line_number":232,"context_line":"   time out after 6400 seconds."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"#. **Live migration progress timeout**"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"   The Compute service also aborts a live migration when it detects that memory"},{"line_number":237,"context_line":"   copy is not making progress for a certain time. You can set this time, in"},{"line_number":238,"context_line":"   seconds, through the configurable parameter"},{"line_number":239,"context_line":"   ``live_migration_progress_timeout``."},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   In Ocata, the default value of ``live_migration_progress_timeout`` is 0,"},{"line_number":242,"context_line":"   which disables progress timeouts. You should not change this value, since"},{"line_number":243,"context_line":"   the algorithm that detects memory copy progress has been determined to be"},{"line_number":244,"context_line":"   unreliable. It may be re-enabled in future releases."},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"#. **Instance downtime**"},{"line_number":247,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_a097e89c","side":"PARENT","line":244,"range":{"start_line":234,"start_character":0,"end_line":244,"end_character":55},"in_reply_to":"3f79a3b5_af24bbb3","updated":"2018-09-11 01:52:03.000000000","message":"Fair enough.","commit_id":"3d31e6c95afe3dff01af037348c0c18e896970db"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"1746112e21fdb280b367ec1ee6d7e70084279e51","unresolved":false,"context_lines":[{"line_number":231,"context_line":"   example, shared-storage live migration of an instance with 8GiB memory will"},{"line_number":232,"context_line":"   time out after 6400 seconds."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"#. **Live migration progress timeout**"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"   The Compute service also aborts a live migration when it detects that memory"},{"line_number":237,"context_line":"   copy is not making progress for a certain time. You can set this time, in"},{"line_number":238,"context_line":"   seconds, through the configurable parameter"},{"line_number":239,"context_line":"   ``live_migration_progress_timeout``."},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   In Ocata, the default value of ``live_migration_progress_timeout`` is 0,"},{"line_number":242,"context_line":"   which disables progress timeouts. You should not change this value, since"},{"line_number":243,"context_line":"   the algorithm that detects memory copy progress has been determined to be"},{"line_number":244,"context_line":"   unreliable. It may be re-enabled in future releases."},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"#. **Instance downtime**"},{"line_number":247,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_af24bbb3","side":"PARENT","line":244,"range":{"start_line":234,"start_character":0,"end_line":244,"end_character":55},"in_reply_to":"3f79a3b5_c9b10147","updated":"2018-09-10 22:28:13.000000000","message":"As I said before, this doc, to me, is more about what is available if you\u0027re looking to setup new configuration for live migration, and this says \"You should not change this value\" so it\u0027s weird to even mention something you shouldn\u0027t use. I left the other mention in the docs because it\u0027s more of a troubleshooting doc - so *if* you need to mess with that to troubleshoot, you could find it there with the bug reference, but I don\u0027t think it\u0027s something we want to mention here for initial configuration and introduce confusion, i.e. information overload.","commit_id":"3d31e6c95afe3dff01af037348c0c18e896970db"}],"doc/source/admin/live-migration-usage.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"6ec8c8b77b31ccbd83cc0d878495342ab0e8f0f0","unresolved":false,"context_lines":[{"line_number":239,"context_line":"   live migration not completed after 1800 sec"},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"The Compute service also cancels migrations when the memory copy seems to make"},{"line_number":242,"context_line":"no progress. This feature is `disabled by default`_, but it can be enabled"},{"line_number":243,"context_line":"using the configuration parameter"},{"line_number":244,"context_line":":oslo.config:option:`libvirt.live_migration_progress_timeout`. Should"},{"line_number":245,"context_line":"this be the case, you may find the following message in the log:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_176def30","line":242,"range":{"start_line":242,"start_character":53,"end_line":242,"end_character":74},"updated":"2018-09-07 21:35:11.000000000","message":"so why aren\u0027t we removing this too?","commit_id":"e76c572c48d6753613abec22f4d0d79257999828"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"12d1606194440995e3193b4bfd786264053a0ec2","unresolved":false,"context_lines":[{"line_number":239,"context_line":"   live migration not completed after 1800 sec"},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"The Compute service also cancels migrations when the memory copy seems to make"},{"line_number":242,"context_line":"no progress. This feature is `disabled by default`_, but it can be enabled"},{"line_number":243,"context_line":"using the configuration parameter"},{"line_number":244,"context_line":":oslo.config:option:`libvirt.live_migration_progress_timeout`. Should"},{"line_number":245,"context_line":"this be the case, you may find the following message in the log:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_2df45ece","line":242,"range":{"start_line":242,"start_character":53,"end_line":242,"end_character":74},"in_reply_to":"3f79a3b5_176def30","updated":"2018-09-07 23:22:14.000000000","message":"I thought about it, sat on the fence a bit, and figure this is more of a troubleshooting type doc, so thought it was OK. The config option itself says it\u0027s deprecated and why, and this doc says it\u0027s disabled by default. So idk, I just left it as a last resort type option.","commit_id":"e76c572c48d6753613abec22f4d0d79257999828"}],"nova/conf/libvirt.py":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"6ec8c8b77b31ccbd83cc0d878495342ab0e8f0f0","unresolved":false,"context_lines":[{"line_number":398,"context_line":"               default\u003d0,"},{"line_number":399,"context_line":"               deprecated_for_removal\u003dTrue,"},{"line_number":400,"context_line":"               deprecated_reason\u003d\"\"\""},{"line_number":401,"context_line":"Serious bugs found in this feature, see "},{"line_number":402,"context_line":"https://bugs.launchpad.net/nova/+bug/1644248 for details."},{"line_number":403,"context_line":"\"\"\","},{"line_number":404,"context_line":"               mutable\u003dTrue,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3f79a3b5_17288fdf","line":401,"range":{"start_line":401,"start_character":39,"end_line":401,"end_character":40},"updated":"2018-09-07 21:35:11.000000000","message":"x","commit_id":"e76c572c48d6753613abec22f4d0d79257999828"}]}