)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"e1825969f1c13f4cf354d344399e9609d4380887","unresolved":false,"context_lines":[{"line_number":13,"context_line":"set of patches for the (more complex) status-based RW rolling"},{"line_number":14,"context_line":"upgrade process (which could, of course, be simplified if we go"},{"line_number":15,"context_line":"ahead with the trigger version). For now, the underlying cycle"},{"line_number":16,"context_line":"is patcheds so that keystone-manage supports the new proposed"},{"line_number":17,"context_line":"--expand, --migrate, --contract."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"So far, the following has been implemented:"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"9ad45d7e_27ecfb8e","line":17,"range":{"start_line":16,"start_character":12,"end_line":17,"end_character":32},"updated":"2016-08-12 16:55:33.000000000","message":"And we\u0027ll have a corresponding repo (expand_repo, migrate_repo, contract_repo) for each of these, correct?","commit_id":"42f90f1f9e7496184810f9778765234fbfa0a517"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"ca3ef2bc5400ada6a2ef2f4ed199af1aba841468","unresolved":false,"context_lines":[{"line_number":13,"context_line":"set of patches for the (more complex) status-based RW rolling"},{"line_number":14,"context_line":"upgrade process (which could, of course, be simplified if we go"},{"line_number":15,"context_line":"ahead with the trigger version). For now, the underlying cycle"},{"line_number":16,"context_line":"is patcheds so that keystone-manage supports the new proposed"},{"line_number":17,"context_line":"--expand, --migrate, --contract."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"So far, the following has been implemented:"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"7ac969e8_15093e32","line":17,"range":{"start_line":16,"start_character":12,"end_line":17,"end_character":32},"in_reply_to":"9ad45d7e_0fcbc41f","updated":"2016-08-12 23:45:35.000000000","message":"Yes, I agree with the separate repos. I think we need at least two: one before the code update and one after. You can\u0027t for instance run the contractions while there is still old code executing.","commit_id":"42f90f1f9e7496184810f9778765234fbfa0a517"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"609aa35404e2c11354e1a7210b1ed192598ba62c","unresolved":false,"context_lines":[{"line_number":13,"context_line":"set of patches for the (more complex) status-based RW rolling"},{"line_number":14,"context_line":"upgrade process (which could, of course, be simplified if we go"},{"line_number":15,"context_line":"ahead with the trigger version). For now, the underlying cycle"},{"line_number":16,"context_line":"is patcheds so that keystone-manage supports the new proposed"},{"line_number":17,"context_line":"--expand, --migrate, --contract."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"So far, the following has been implemented:"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"9ad45d7e_38cb7120","line":17,"range":{"start_line":16,"start_character":12,"end_line":17,"end_character":32},"in_reply_to":"9ad45d7e_27ecfb8e","updated":"2016-08-12 19:27:22.000000000","message":"No I don\u0027t think so. The migrate portion might need to be run multiple times (e.g. migrate in batches), so I don\u0027t think a migration rep makes sense.","commit_id":"42f90f1f9e7496184810f9778765234fbfa0a517"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"96a2b234d6286c95544eef17a69f7beeaf5a43d4","unresolved":false,"context_lines":[{"line_number":13,"context_line":"set of patches for the (more complex) status-based RW rolling"},{"line_number":14,"context_line":"upgrade process (which could, of course, be simplified if we go"},{"line_number":15,"context_line":"ahead with the trigger version). For now, the underlying cycle"},{"line_number":16,"context_line":"is patcheds so that keystone-manage supports the new proposed"},{"line_number":17,"context_line":"--expand, --migrate, --contract."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"So far, the following has been implemented:"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"9ad45d7e_0fcbc41f","line":17,"range":{"start_line":16,"start_character":12,"end_line":17,"end_character":32},"in_reply_to":"9ad45d7e_38cb7120","updated":"2016-08-12 20:02:54.000000000","message":"If we run the migrate in batches and it takes a long time, I think that is still okay, right?  It just means that you wouldn\u0027t run the contract scripts until migrate is finished, but everything is up.  \n\nHaving the 3 repos allows you to group your scripts.  So if I\u0027m making a db change, I\u0027ll add a script in each repo, all with the same version number.  Otherwise, I think it will be difficult to keep developer scripts in sequence between patches.","commit_id":"42f90f1f9e7496184810f9778765234fbfa0a517"}]}