)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":679,"name":"Kevin L. Mitchell","email":"klmitch@mit.edu","username":"klmitch"},"change_message_id":"272a3c712b3032817d55e84ab7c930333329cf60","unresolved":false,"context_lines":[{"line_number":17,"context_line":"side. As a stopgap measure, this patch introduces a --max-servers"},{"line_number":18,"context_line":"option to host-evacuate-live. With this option, the user can control"},{"line_number":19,"context_line":"the number of VMs that are live-migrated at the same time, thus"},{"line_number":20,"context_line":"allowing the user to avoid the dirty memory scenario described above."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Change-Id: I17bad5f3253d6657fc1e6610159fc8e3921e6ea4"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"da20952f_36185684","line":20,"updated":"2015-09-02 17:41:19.000000000","message":"Could you create a backlog blueprint[1] for nova to correct this issue properly?  That way we don\u0027t lose track of that necessary work.\n\n[1] http://specs.openstack.org/openstack/nova-specs/specs/backlog/","commit_id":"3d9c01b2d37e0ba5e4ea21a0697fdd83ace3d1ab"}]}