)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"58bc9124e3a784ed6eff37816b1b023ca3c31f10","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Ann Kamyshnikova \u003cakamyshnikova@mirantis.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2015-12-02 11:16:54 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Kilo initial migration"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Juno will depricated with Mitaka release, so juno_initial migration"},{"line_number":10,"context_line":"should be replaced with kilo_initilal migration in Mitaka."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"9a8ffd7b_3fad579b","line":7,"updated":"2015-12-02 11:23:56.000000000","message":"I know we did it before. But can someone clarify why we actually do it? If anything, it breaks flows for those who decide to upgrade in multiple cycle steps.\n\nIs there any benefit in having them squashed?","commit_id":"376aa92785081671dbfa9d6f356adde0e2678cdf"},{"author":{"_account_id":7249,"name":"Ann Taraday","email":"akamyshnikova@mirantis.com","username":"AKamyshnikova"},"change_message_id":"5970a8d48f5364f4495aabef50b4930986134abb","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Ann Kamyshnikova \u003cakamyshnikova@mirantis.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2015-12-02 11:16:54 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Kilo initial migration"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Juno will depricated with Mitaka release, so juno_initial migration"},{"line_number":10,"context_line":"should be replaced with kilo_initilal migration in Mitaka."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"1a7b0d38_56e4e60b","line":7,"in_reply_to":"5a710552_9d749336","updated":"2015-12-25 08:18:16.000000000","message":"I checked time of running upgrade head command without and with this patch on my local machine on MySQL 188.579477072 vs 137.295358896 seconds.","commit_id":"376aa92785081671dbfa9d6f356adde0e2678cdf"},{"author":{"_account_id":7249,"name":"Ann Taraday","email":"akamyshnikova@mirantis.com","username":"AKamyshnikova"},"change_message_id":"429336f0e032d2866d8708c474f116bf00162e27","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Ann Kamyshnikova \u003cakamyshnikova@mirantis.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2015-12-02 11:16:54 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Kilo initial migration"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Juno will depricated with Mitaka release, so juno_initial migration"},{"line_number":10,"context_line":"should be replaced with kilo_initilal migration in Mitaka."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"9a8ffd7b_536a7db4","line":7,"in_reply_to":"9a8ffd7b_3fad579b","updated":"2015-12-02 17:47:50.000000000","message":"I think one of the point here is that we reduce number of complex migrations that have some data migration and etc. I think this is good for our online migration support, what do you think?","commit_id":"376aa92785081671dbfa9d6f356adde0e2678cdf"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"e678f7746211e6c7a6a0f5107ffdc7a9c1ead50a","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Ann Kamyshnikova \u003cakamyshnikova@mirantis.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2015-12-02 11:16:54 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Kilo initial migration"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Juno will depricated with Mitaka release, so juno_initial migration"},{"line_number":10,"context_line":"should be replaced with kilo_initilal migration in Mitaka."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"5a710552_9d749336","line":7,"in_reply_to":"9a8ffd7b_536a7db4","updated":"2015-12-16 15:56:38.000000000","message":"online schema migrations benefit only those who upgrade from previous releases. Those scripts you squash are not expected to be executed for existing setups, but for new setups only.\n\nDo we try to optimize time of execution for initial neutron db sync?","commit_id":"376aa92785081671dbfa9d6f356adde0e2678cdf"},{"author":{"_account_id":14605,"name":"vikram.choudhary","email":"vikschw@gmail.com","username":"vikram.choudhary"},"change_message_id":"1e7ca3e644bc7d701fa272f527c070ff1a4081d1","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Kilo initial migration"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Juno will depricated with Mitaka release, so juno_initial migration"},{"line_number":10,"context_line":"should be replaced with kilo_initilal migration in Mitaka."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Optimized execution time of \"upgrade head\" command."},{"line_number":13,"context_line":"Test on my local machine on MySQL shows about 28% reduce (from 188"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"1a7b0d38_6476f0a5","line":10,"updated":"2015-12-27 04:54:09.000000000","message":"Could plz do some write-up on what is being changed for improving the performance.\n\nDo we really want to do the changes in vendor specific files? Anyways those will be moving out.","commit_id":"82e68447b74960945faede83508a6ed2e9ac2ceb"},{"author":{"_account_id":7249,"name":"Ann Taraday","email":"akamyshnikova@mirantis.com","username":"AKamyshnikova"},"change_message_id":"1f8e682c1bdc58e4c7e8f53caaa7f7508bf36af8","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Kilo initial migration"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Juno will depricated with Mitaka release, so juno_initial migration"},{"line_number":10,"context_line":"should be replaced with kilo_initilal migration in Mitaka."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Optimized execution time of \"upgrade head\" command."},{"line_number":13,"context_line":"Test on my local machine on MySQL shows about 28% reduce (from 188"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"1a7b0d38_51f02667","line":10,"in_reply_to":"1a7b0d38_6476f0a5","updated":"2015-12-29 10:57:58.000000000","message":"I have not done anything *special* for improving the performance, I just move relevant changes in init_opts, so I\u0027m not sure that this needs special description. \n\nNot sure I understand you second concern. Database state should be the same, I just changing the way how migrations are applied, so even vendor plugins are moving kilo state needs to be the same.","commit_id":"82e68447b74960945faede83508a6ed2e9ac2ceb"}]}