)]}'
{"doc/source/upgrading.rst":[{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":83,"context_line":"If you run a multi-node Keystone cluster that uses a replicated database, like"},{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case upgrade outlined above. In these steps"},{"line_number":87,"context_line":"the nodes will be divided into \"first\" and \"other\" nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_e29f3001","line":86,"range":{"start_line":86,"start_character":21,"end_line":86,"end_character":53},"updated":"2016-08-27 04:25:07.000000000","message":"base case (`Upgrading with downtime`_) outlined above.","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":83,"context_line":"If you run a multi-node Keystone cluster that uses a replicated database, like"},{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case upgrade outlined above. In these steps"},{"line_number":87,"context_line":"the nodes will be divided into \"first\" and \"other\" nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_29aefe80","line":86,"range":{"start_line":86,"start_character":21,"end_line":86,"end_character":53},"in_reply_to":"fa7ab95a_e29f3001","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case upgrade outlined above. In these steps"},{"line_number":87,"context_line":"the nodes will be divided into \"first\" and \"other\" nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_a260c836","line":87,"range":{"start_line":87,"start_character":44,"end_line":87,"end_character":49},"updated":"2016-08-27 04:25:07.000000000","message":"same","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case upgrade outlined above. In these steps"},{"line_number":87,"context_line":"the nodes will be divided into \"first\" and \"other\" nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_8273c414","line":87,"range":{"start_line":87,"start_character":31,"end_line":87,"end_character":38},"updated":"2016-08-27 04:25:07.000000000","message":"use backticks for emphasis, a single backtick results in italics, two backticks result in code style, i\u0027d use single backticks here","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case upgrade outlined above. In these steps"},{"line_number":87,"context_line":"the nodes will be divided into \"first\" and \"other\" nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_89c9ca5b","line":87,"range":{"start_line":87,"start_character":31,"end_line":87,"end_character":38},"in_reply_to":"fa7ab95a_8273c414","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case upgrade outlined above. In these steps"},{"line_number":87,"context_line":"the nodes will be divided into \"first\" and \"other\" nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_c9bf52a8","line":87,"range":{"start_line":87,"start_character":44,"end_line":87,"end_character":49},"in_reply_to":"fa7ab95a_a260c836","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":91,"name":"Alvaro","email":"aloga@ifca.unican.es","username":"aloga"},"change_message_id":"088430b621e9673defeae857f7e167b75118612d","unresolved":false,"context_lines":[{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"#. Disable Keystone on all nodes but the first node. This can be done via a"},{"line_number":93,"context_line":"   variety of mechanisms that will depend on the deployment. If you are unable"},{"line_number":94,"context_line":"   to disable a service or place a service into maintenance mode in your load"},{"line_number":95,"context_line":"   balancer, you can stop the Keystone processes."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_e197f845","line":92,"range":{"start_line":92,"start_character":41,"end_line":92,"end_character":46},"updated":"2016-09-07 07:24:34.000000000","message":"this should be emphasized as in L87","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"#. Disable Keystone on all nodes but the first node. This can be done via a"},{"line_number":93,"context_line":"   variety of mechanisms that will depend on the deployment. If you are unable"},{"line_number":94,"context_line":"   to disable a service or place a service into maintenance mode in your load"},{"line_number":95,"context_line":"   balancer, you can stop the Keystone processes."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_e9ded60f","line":92,"range":{"start_line":92,"start_character":41,"end_line":92,"end_character":46},"in_reply_to":"9a89bdaa_e197f845","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":91,"name":"Alvaro","email":"aloga@ifca.unican.es","username":"aloga"},"change_message_id":"088430b621e9673defeae857f7e167b75118612d","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   to disable a service or place a service into maintenance mode in your load"},{"line_number":95,"context_line":"   balancer, you can stop the Keystone processes."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"#. Stop the database service on one of the other nodes in the cluster. This"},{"line_number":98,"context_line":"   will isolate the old dataset on a single node in the cluster. In the event"},{"line_number":99,"context_line":"   of a failed update this data can be used to rebuild the cluster without"},{"line_number":100,"context_line":"   having to restore from backup."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_219e4063","line":97,"range":{"start_line":97,"start_character":43,"end_line":97,"end_character":48},"updated":"2016-09-07 07:24:34.000000000","message":"this should be emphasized as in L87","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   to disable a service or place a service into maintenance mode in your load"},{"line_number":95,"context_line":"   balancer, you can stop the Keystone processes."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"#. Stop the database service on one of the other nodes in the cluster. This"},{"line_number":98,"context_line":"   will isolate the old dataset on a single node in the cluster. In the event"},{"line_number":99,"context_line":"   of a failed update this data can be used to rebuild the cluster without"},{"line_number":100,"context_line":"   having to restore from backup."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_09e4dade","line":97,"range":{"start_line":97,"start_character":43,"end_line":97,"end_character":48},"in_reply_to":"9a89bdaa_219e4063","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":91,"name":"Alvaro","email":"aloga@ifca.unican.es","username":"aloga"},"change_message_id":"088430b621e9673defeae857f7e167b75118612d","unresolved":false,"context_lines":[{"line_number":99,"context_line":"   of a failed update this data can be used to rebuild the cluster without"},{"line_number":100,"context_line":"   having to restore from backup."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Update the configuration files on the first node."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_818f0c29","line":102,"range":{"start_line":102,"start_character":41,"end_line":102,"end_character":46},"updated":"2016-09-07 07:24:34.000000000","message":"this should be emphasized as in L87","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":99,"context_line":"   of a failed update this data can be used to rebuild the cluster without"},{"line_number":100,"context_line":"   having to restore from backup."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Update the configuration files on the first node."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_49ea62ad","line":102,"range":{"start_line":102,"start_character":41,"end_line":102,"end_character":46},"in_reply_to":"9a89bdaa_818f0c29","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Update the configuration files on the first node."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"#. Run ``keystone-manage db_sync`` on the first node. As soon as this finishes,"},{"line_number":107,"context_line":"   Keystone is now working again on a single node in the cluster."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_02ba546e","line":104,"range":{"start_line":104,"start_character":3,"end_line":104,"end_character":37},"updated":"2016-08-27 04:25:07.000000000","message":"i want more detail here, but i guess that\u0027s deployment specific, whether you use packages or something else, darn","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":91,"name":"Alvaro","email":"aloga@ifca.unican.es","username":"aloga"},"change_message_id":"088430b621e9673defeae857f7e167b75118612d","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Update the configuration files on the first node."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"#. Run ``keystone-manage db_sync`` on the first node. As soon as this finishes,"},{"line_number":107,"context_line":"   Keystone is now working again on a single node in the cluster."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_e17e1818","line":104,"range":{"start_line":104,"start_character":27,"end_line":104,"end_character":32},"updated":"2016-09-07 07:24:34.000000000","message":"this should be emphasized as in L87","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"#. Update the configuration files on the first node."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"#. Run ``keystone-manage db_sync`` on the first node. As soon as this finishes,"},{"line_number":107,"context_line":"   Keystone is now working again on a single node in the cluster."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_a9d92e24","line":104,"range":{"start_line":104,"start_character":27,"end_line":104,"end_character":32},"in_reply_to":"9a89bdaa_e17e1818","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":91,"name":"Alvaro","email":"aloga@ifca.unican.es","username":"aloga"},"change_message_id":"088430b621e9673defeae857f7e167b75118612d","unresolved":false,"context_lines":[{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"#. Run ``keystone-manage db_sync`` on the first node. As soon as this finishes,"},{"line_number":107,"context_line":"   Keystone is now working again on a single node in the cluster."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"#. Keystone is now upgraded on a single node. Your load balancers will be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_81a8ec8e","line":106,"range":{"start_line":106,"start_character":42,"end_line":106,"end_character":47},"updated":"2016-09-07 07:24:34.000000000","message":"this should be emphasided as in L87","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":103,"context_line":""},{"line_number":104,"context_line":"#. Upgrade Keystone on the first node. Keystone is now down for your cloud."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"#. Run ``keystone-manage db_sync`` on the first node. As soon as this finishes,"},{"line_number":107,"context_line":"   Keystone is now working again on a single node in the cluster."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"#. Keystone is now upgraded on a single node. Your load balancers will be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_c9d672f0","line":106,"range":{"start_line":106,"start_character":42,"end_line":106,"end_character":47},"in_reply_to":"9a89bdaa_81a8ec8e","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":108,"context_line":""},{"line_number":109,"context_line":"#. Keystone is now upgraded on a single node. Your load balancers will be"},{"line_number":110,"context_line":"   sending all traffic to this single node. This is your chance to run"},{"line_number":111,"context_line":"   tests and ensure Keystone is not broken. If Keystone is broken, see"},{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_027174e0","line":111,"range":{"start_line":111,"start_character":3,"end_line":111,"end_character":8},"updated":"2016-08-27 04:25:07.000000000","message":"i guess this is also deployment specific, can you elaborate on the types of tests you run? are they maintained in house?","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":109,"context_line":"#. Keystone is now upgraded on a single node. Your load balancers will be"},{"line_number":110,"context_line":"   sending all traffic to this single node. This is your chance to run"},{"line_number":111,"context_line":"   tests and ensure Keystone is not broken. If Keystone is broken, see"},{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_c2f14c6c","line":112,"range":{"start_line":112,"start_character":9,"end_line":112,"end_character":48},"updated":"2016-08-27 04:25:07.000000000","message":"section titles can be used automatically for links, write this as:\n\n  see the `Rollback after a failed upgrade`_ section below","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":109,"context_line":"#. Keystone is now upgraded on a single node. Your load balancers will be"},{"line_number":110,"context_line":"   sending all traffic to this single node. This is your chance to run"},{"line_number":111,"context_line":"   tests and ensure Keystone is not broken. If Keystone is broken, see"},{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_090bfa8e","line":112,"range":{"start_line":112,"start_character":9,"end_line":112,"end_character":48},"in_reply_to":"fa7ab95a_c2f14c6c","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":91,"name":"Alvaro","email":"aloga@ifca.unican.es","username":"aloga"},"change_message_id":"088430b621e9673defeae857f7e167b75118612d","unresolved":false,"context_lines":[{"line_number":111,"context_line":"   tests and ensure Keystone is not broken. If Keystone is broken, see"},{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"},{"line_number":116,"context_line":"   does not need to be run again."},{"line_number":117,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_41c4245e","line":114,"range":{"start_line":114,"start_character":54,"end_line":114,"end_character":62},"updated":"2016-09-07 07:24:34.000000000","message":"this should be emphasided as in L87","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":111,"context_line":"   tests and ensure Keystone is not broken. If Keystone is broken, see"},{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"},{"line_number":116,"context_line":"   does not need to be run again."},{"line_number":117,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_09321a5f","line":114,"range":{"start_line":114,"start_character":54,"end_line":114,"end_character":62},"in_reply_to":"9a89bdaa_41c4245e","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"f74f7d711b432ad462dcb22045c34ca531ac185a","unresolved":false,"context_lines":[{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"},{"line_number":116,"context_line":"   does not need to be run again."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"#. On the node where you stopped the database service, be sure to restart"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_2e274913","line":115,"range":{"start_line":115,"start_character":68,"end_line":115,"end_character":75},"updated":"2016-08-27 00:05:38.000000000","message":"db_sync","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"},{"line_number":116,"context_line":"   does not need to be run again."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"#. On the node where you stopped the database service, be sure to restart"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_82f8244b","line":115,"range":{"start_line":115,"start_character":68,"end_line":115,"end_character":75},"in_reply_to":"fa7ab95a_2e274913","updated":"2016-08-27 04:25:07.000000000","message":"``db_sync``","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":112,"context_line":"   the **Rollback after a failed upgrade section** below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the \"other\" nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The db sync"},{"line_number":116,"context_line":"   does not need to be run again."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"#. On the node where you stopped the database service, be sure to restart"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_e92c1604","line":115,"range":{"start_line":115,"start_character":68,"end_line":115,"end_character":75},"in_reply_to":"fa7ab95a_82f8244b","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":120,"context_line":""},{"line_number":121,"context_line":"Using this model, the outage window is minimized because the only time"},{"line_number":122,"context_line":"when your cluster is totally offline is between loading the newer version"},{"line_number":123,"context_line":"of Keystone and running the db sync command. Typically the outage with"},{"line_number":124,"context_line":"this method can be measured in tens of seconds especially if automation is"},{"line_number":125,"context_line":"used."},{"line_number":126,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_42fe1c39","line":123,"range":{"start_line":123,"start_character":28,"end_line":123,"end_character":35},"updated":"2016-08-27 04:25:07.000000000","message":"``db_sync``","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":120,"context_line":""},{"line_number":121,"context_line":"Using this model, the outage window is minimized because the only time"},{"line_number":122,"context_line":"when your cluster is totally offline is between loading the newer version"},{"line_number":123,"context_line":"of Keystone and running the db sync command. Typically the outage with"},{"line_number":124,"context_line":"this method can be measured in tens of seconds especially if automation is"},{"line_number":125,"context_line":"used."},{"line_number":126,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_29335e63","line":123,"range":{"start_line":123,"start_character":28,"end_line":123,"end_character":35},"in_reply_to":"fa7ab95a_42fe1c39","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"f74f7d711b432ad462dcb22045c34ca531ac185a","unresolved":false,"context_lines":[{"line_number":131,"context_line":"has been upgraded. This makes the recovery simpler and quicker. If issues are"},{"line_number":132,"context_line":"not discovered until the entire cluster is upgraded, a full shutdown and"},{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"},{"line_number":134,"context_line":"fixing a single node with an old copy of the database still available This"},{"line_number":135,"context_line":"process will be dependent on your architecture and it is highly recommended"},{"line_number":136,"context_line":"that you\u0027ve practiced this in a dev environment before trying to use it for the"},{"line_number":137,"context_line":"first time."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_6e2151fb","line":134,"range":{"start_line":134,"start_character":60,"end_line":134,"end_character":69},"updated":"2016-08-27 00:05:38.000000000","message":"available.","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":131,"context_line":"has been upgraded. This makes the recovery simpler and quicker. If issues are"},{"line_number":132,"context_line":"not discovered until the entire cluster is upgraded, a full shutdown and"},{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"},{"line_number":134,"context_line":"fixing a single node with an old copy of the database still available This"},{"line_number":135,"context_line":"process will be dependent on your architecture and it is highly recommended"},{"line_number":136,"context_line":"that you\u0027ve practiced this in a dev environment before trying to use it for the"},{"line_number":137,"context_line":"first time."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_a9476eba","line":134,"range":{"start_line":134,"start_character":60,"end_line":134,"end_character":69},"in_reply_to":"fa7ab95a_6e2151fb","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"f74f7d711b432ad462dcb22045c34ca531ac185a","unresolved":false,"context_lines":[{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"},{"line_number":134,"context_line":"fixing a single node with an old copy of the database still available This"},{"line_number":135,"context_line":"process will be dependent on your architecture and it is highly recommended"},{"line_number":136,"context_line":"that you\u0027ve practiced this in a dev environment before trying to use it for the"},{"line_number":137,"context_line":"first time."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"#. Isolate the bad node. Shutdown Keystone and the database services"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_8e4a15ab","line":136,"range":{"start_line":136,"start_character":32,"end_line":136,"end_character":35},"updated":"2016-08-27 00:05:38.000000000","message":"development","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"},{"line_number":134,"context_line":"fixing a single node with an old copy of the database still available This"},{"line_number":135,"context_line":"process will be dependent on your architecture and it is highly recommended"},{"line_number":136,"context_line":"that you\u0027ve practiced this in a dev environment before trying to use it for the"},{"line_number":137,"context_line":"first time."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"#. Isolate the bad node. Shutdown Keystone and the database services"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_c944b2b8","line":136,"range":{"start_line":136,"start_character":32,"end_line":136,"end_character":35},"in_reply_to":"fa7ab95a_8e4a15ab","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"af6c196c4caf44522299d321e5b0f586a6653e9a","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"#. Downgrade the code and config files on the bad node."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"This process should be doable in a matter of minutes and will"},{"line_number":154,"context_line":"minimize cloud downtime if it is required."},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"Upgrading without downtime"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_a29528e5","line":153,"updated":"2016-08-27 04:25:07.000000000","message":"you can squeeze more characters on this line","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"532fa177ff32682379664316a287291ac1e877b5","unresolved":false,"context_lines":[{"line_number":150,"context_line":""},{"line_number":151,"context_line":"#. Downgrade the code and config files on the bad node."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"This process should be doable in a matter of minutes and will"},{"line_number":154,"context_line":"minimize cloud downtime if it is required."},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"Upgrading without downtime"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a89bdaa_e91336b6","line":153,"in_reply_to":"fa7ab95a_a29528e5","updated":"2016-09-07 17:49:52.000000000","message":"Done","commit_id":"6f862acc2546810e1d8858a4738c35b7c2e79b89"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"09c1abbe90208587a1e20cf18787d393c88b9d40","unresolved":false,"context_lines":[{"line_number":109,"context_line":"#. Keystone is now upgraded on a single node. Your load balancers will be"},{"line_number":110,"context_line":"   sending all traffic to this single node. This is your chance to run"},{"line_number":111,"context_line":"   tests and ensure Keystone is not broken. If Keystone is broken, see"},{"line_number":112,"context_line":"   the `Rollback after a failed upgrade`_ section below."},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"#. Once tests are completed, begin the upgrade on the ``other`` nodes. This"},{"line_number":115,"context_line":"   entails updating configuration files and upgrading the code. The"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a89bdaa_c9c1d7e5","line":112,"range":{"start_line":112,"start_character":40,"end_line":112,"end_character":41},"updated":"2016-09-08 16:13:12.000000000","message":"nit: extra underline char","commit_id":"9b3524f8895426f5b646f590992e82a70e5bef74"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"09c1abbe90208587a1e20cf18787d393c88b9d40","unresolved":false,"context_lines":[{"line_number":127,"context_line":"Rollback after a failed upgrade"},{"line_number":128,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"If the upgrade fails then tests will have caught it while only a single node"},{"line_number":131,"context_line":"has been upgraded. This makes the recovery simpler and quicker. If issues are"},{"line_number":132,"context_line":"not discovered until the entire cluster is upgraded, a full shutdown and"},{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a89bdaa_c9363702","line":130,"range":{"start_line":130,"start_character":20,"end_line":130,"end_character":21},"updated":"2016-09-08 16:13:12.000000000","message":",","commit_id":"9b3524f8895426f5b646f590992e82a70e5bef74"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"09c1abbe90208587a1e20cf18787d393c88b9d40","unresolved":false,"context_lines":[{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"},{"line_number":134,"context_line":"fixing a single node with an old copy of the database still available. This"},{"line_number":135,"context_line":"process will be dependent on your architecture and it is highly recommended"},{"line_number":136,"context_line":"that you\u0027ve practiced this in a development  environment before trying to use"},{"line_number":137,"context_line":"it for the first time."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"#. Isolate the bad node. Shutdown Keystone and the database services"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a89bdaa_29616305","line":136,"range":{"start_line":136,"start_character":44,"end_line":136,"end_character":45},"updated":"2016-09-08 16:13:12.000000000","message":"extra space","commit_id":"9b3524f8895426f5b646f590992e82a70e5bef74"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"3c8e4bf2904f1fb7a85c2c493a458127a06f3a79","unresolved":false,"context_lines":[{"line_number":34,"context_line":"Plan your upgrade:"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"* Read and ensure you understand the `release notes"},{"line_number":37,"context_line":"  \u003chttp://docs.openstack.org/releasenotes/keystone/\u003e`_ for the next release."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"* Resolve any outstanding deprecation warnings in your logs. Some deprecation"},{"line_number":40,"context_line":"  cycles are as short as a single release, so it\u0027s possible to break a"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9a89bdaa_2ac79196","line":37,"range":{"start_line":37,"start_character":2,"end_line":37,"end_character":54},"updated":"2016-09-08 16:48:15.000000000","message":"i didn\u0027t want to waste infra resources on a trivial change, especially when we\u0027re fixing other stuff in the same file","commit_id":"61ae52254c159c66a6b471835f689d24eba453fc"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b085ae28b5cc77d28ac2c220f50f6a8defd4785b","unresolved":false,"context_lines":[{"line_number":77,"context_line":""},{"line_number":78,"context_line":"#. Start all keystone processes."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Upgrading a Keystone cluster with minimal downtime"},{"line_number":81,"context_line":"--------------------------------------------------"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"If you run a multi-node Keystone cluster that uses a replicated database, like"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9a89bdaa_d2425767","line":80,"updated":"2016-09-08 19:00:13.000000000","message":"s/Keystone/keystone/ to be consistent with the rest of the keystone usage in this document","commit_id":"61ae52254c159c66a6b471835f689d24eba453fc"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b085ae28b5cc77d28ac2c220f50f6a8defd4785b","unresolved":false,"context_lines":[{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case (`Upgrading with downtime`_) outlined above."},{"line_number":87,"context_line":"In these steps the nodes will be divided into ``first`` and ``other`` nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of Keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9a89bdaa_0d3d82c3","line":87,"updated":"2016-09-08 19:00:13.000000000","message":"I wonder if we should break ``first`` and ``other`` into hypothetical ``keystone-1``, ``keystone-2``, and ``keystone-3``? \n\n`````` for the sake of more backticks ```````","commit_id":"61ae52254c159c66a6b471835f689d24eba453fc"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b085ae28b5cc77d28ac2c220f50f6a8defd4785b","unresolved":false,"context_lines":[{"line_number":127,"context_line":"Rollback after a failed upgrade"},{"line_number":128,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"If the upgrade fails, then tests will have caught it while only a single node"},{"line_number":131,"context_line":"has been upgraded. This makes the recovery simpler and quicker. If issues are"},{"line_number":132,"context_line":"not discovered until the entire cluster is upgraded, a full shutdown and"},{"line_number":133,"context_line":"restore from backup will be required. That will take much longer than just"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9a89bdaa_ed585e33","line":130,"updated":"2016-09-08 19:00:13.000000000","message":"Which tests? Or do we mean to say \"you should run tests here to ensure the upgrade didn\u0027t fail\"?","commit_id":"61ae52254c159c66a6b471835f689d24eba453fc"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"207dc8f52be838bcfba57e2f2507910aed15f0dd","unresolved":false,"context_lines":[{"line_number":77,"context_line":""},{"line_number":78,"context_line":"#. Start all keystone processes."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Upgrading a keystone cluster with minimal downtime"},{"line_number":81,"context_line":"--------------------------------------------------"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"If you run a multi-node keystone cluster that uses a replicated database, like"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9a89bdaa_82e31c33","line":80,"updated":"2016-09-08 20:35:43.000000000","message":"s/a keystone cluster// \n\nSince at this point in the document it\u0027s inferred.","commit_id":"1fec0d283a09a540467136b457fa07ba69e7cee3"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"207dc8f52be838bcfba57e2f2507910aed15f0dd","unresolved":false,"context_lines":[{"line_number":84,"context_line":"a Galera cluster, it is possible to upgrade with minimal downtime. This method"},{"line_number":85,"context_line":"also optimizes recovery time from a failed upgrade. This section assumes"},{"line_number":86,"context_line":"familiarity with the base case (`Upgrading with downtime`_) outlined above."},{"line_number":87,"context_line":"In these steps the nodes will be divided into ``first`` and ``other`` nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9a89bdaa_e2a308ff","line":87,"updated":"2016-09-08 20:35:43.000000000","message":"I assume ``other`` can be multiple?","commit_id":"1fec0d283a09a540467136b457fa07ba69e7cee3"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"00909543a7e47c823e229ff9ae863fe216314da9","unresolved":false,"context_lines":[{"line_number":86,"context_line":"familiarity with the base case (`Upgrading with downtime`_) outlined above."},{"line_number":87,"context_line":"In these steps the nodes will be divided into ``first`` and ``other`` nodes."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"#. Backup your database. There is no way to rollback the upgrade of keystone"},{"line_number":90,"context_line":"   and this is your worst-case fallback option."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"#. Disable keystone on all nodes but the ``first`` node. This can be done via a"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a89bdaa_28122f59","line":89,"updated":"2016-09-08 21:12:10.000000000","message":"nit: \"no way to rollback\" is not totally true in this process, especially since you\u0027ve got a better solution in L97","commit_id":"9418f2609ffe679d10b266b91381c46dcc354de3"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"00909543a7e47c823e229ff9ae863fe216314da9","unresolved":false,"context_lines":[{"line_number":94,"context_line":"   to disable a service or place a service into maintenance mode in your load"},{"line_number":95,"context_line":"   balancer, you can stop the keystone processes."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"#. Stop the database service on one of the ``other`` nodes in the cluster. This"},{"line_number":98,"context_line":"   will isolate the old dataset on a single node in the cluster. In the event"},{"line_number":99,"context_line":"   of a failed update this data can be used to rebuild the cluster without"},{"line_number":100,"context_line":"   having to restore from backup."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a89bdaa_2576dad8","line":97,"updated":"2016-09-08 21:12:10.000000000","message":"nit: I don\u0027t think \"first\" and \"other\" should be literals (they\u0027re not literals in the rest of the doc).","commit_id":"9418f2609ffe679d10b266b91381c46dcc354de3"}]}