)]}'
{"doc/source/reference/upgrade-checks.rst":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"020b2dadefc86a7d46a33fe5219f101807dc1bf5","unresolved":false,"context_lines":[{"line_number":48,"context_line":"* Candidates for automated upgrade checks are things in a projects upgrade"},{"line_number":49,"context_line":"  release notes which can be verified via the database. For example, when"},{"line_number":50,"context_line":"  upgrading to Cells v2 in Ocata, one required step was creating"},{"line_number":51,"context_line":"  \"cell mappings\" for ``cell0`` and the initial cell where the initial cell"},{"line_number":52,"context_line":"  was the existing ``nova`` database. This can easily be verified by checking"},{"line_number":53,"context_line":"  the contents of the ``cell_mappings`` table in the ``nova_api`` database."},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_82ea180c","line":51,"range":{"start_line":51,"start_character":40,"end_line":51,"end_character":75},"updated":"2018-08-27 21:37:08.000000000","message":"What is this saying?","commit_id":"900b0e789c52e492c2c04e4a6b3eebbe5900bd42"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"932065d0ca1185973f453b760d3e9f667b4e3637","unresolved":false,"context_lines":[{"line_number":48,"context_line":"* Candidates for automated upgrade checks are things in a projects upgrade"},{"line_number":49,"context_line":"  release notes which can be verified via the database. For example, when"},{"line_number":50,"context_line":"  upgrading to Cells v2 in Ocata, one required step was creating"},{"line_number":51,"context_line":"  \"cell mappings\" for ``cell0`` and the initial cell where the initial cell"},{"line_number":52,"context_line":"  was the existing ``nova`` database. This can easily be verified by checking"},{"line_number":53,"context_line":"  the contents of the ``cell_mappings`` table in the ``nova_api`` database."},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_22c8e452","line":51,"range":{"start_line":51,"start_character":40,"end_line":51,"end_character":75},"in_reply_to":"3f79a3b5_82ea180c","updated":"2018-08-27 21:45:07.000000000","message":"Trying to say, in that check, you have to have cell0 and cell1 where cell1 uses the existing nova db from before cells v2. Cell0 would have a fresh db with the same schema as the \u0027nova\u0027 db, but it\u0027s empty when you upgrade / rollout with cells v2.\n\nMaybe I should re-word as:\n\n\"\"\"\nFor example, when upgrading to Cells v2 in Ocata, one required step was creating \"cell mappings\" for ``cell0`` and ``cell1`` where ``cell1`` uses the existing ``nova`` database for existing deployments.\n\"\"\"\n\n?\n\nOr I could just remove all of the stuff after cell1:\n\n\"\"\"\nFor example, when upgrading to Cells v2 in Ocata, one required step was creating \"cell mappings\" for ``cell0`` and ``cell1``.\n\"\"\"\n\nIt might not matter here, but it assumes then that people know the difference between cell0 and cell1 - but again that might not matter for these docs.","commit_id":"900b0e789c52e492c2c04e4a6b3eebbe5900bd42"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"020b2dadefc86a7d46a33fe5219f101807dc1bf5","unresolved":false,"context_lines":[{"line_number":143,"context_line":""},{"line_number":144,"context_line":".. code-block:: console"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"  $ nova-status upgrade check"},{"line_number":147,"context_line":"  +----------------------------------------------------+"},{"line_number":148,"context_line":"  | Upgrade Check Results                              |"},{"line_number":149,"context_line":"  +----------------------------------------------------+"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_a2d71423","line":146,"updated":"2018-08-27 21:37:08.000000000","message":"There was some mention on the goal of wanting this in a more parsable output format. Probably too late to really want to do that now for nova, and since we want to be consistent across all projects, too late to do that elsewhere as well. But thought I should mention it since it was brought up.","commit_id":"900b0e789c52e492c2c04e4a6b3eebbe5900bd42"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"932065d0ca1185973f453b760d3e9f667b4e3637","unresolved":false,"context_lines":[{"line_number":143,"context_line":""},{"line_number":144,"context_line":".. code-block:: console"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"  $ nova-status upgrade check"},{"line_number":147,"context_line":"  +----------------------------------------------------+"},{"line_number":148,"context_line":"  | Upgrade Check Results                              |"},{"line_number":149,"context_line":"  +----------------------------------------------------+"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_c24570b5","line":146,"in_reply_to":"3f79a3b5_a2d71423","updated":"2018-08-27 21:45:07.000000000","message":"Hmm, was that the thing mnaser brought up about machine-readable output so deployment tooling could parse each individual detail and try to remedy on the fly? I\u0027m not sure how much we want to rely on that kind of API in a CLI, nor how useful it would be since once your deployment tooling has the stuff in place to pass the check, you don\u0027t really need to write tooling for how to fix it. In other words, if the deployment tooling fails a check, there is a bug in the deployment tool.","commit_id":"900b0e789c52e492c2c04e4a6b3eebbe5900bd42"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"ac6ab81550da481992d69e3eaf5af05a224ad374","unresolved":false,"context_lines":[{"line_number":7,"context_line":"especially when it comes to major changes during upgrades that require operator"},{"line_number":8,"context_line":"intervention."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"This guide covers the background on novas upgrade check tooling, how it is"},{"line_number":11,"context_line":"used, and what to look for in writing new checks."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Background"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_4acddc2e","line":10,"range":{"start_line":10,"start_character":36,"end_line":10,"end_character":41},"updated":"2018-09-10 19:18:16.000000000","message":"nova\u0027s","commit_id":"5e4558853d8ffdd22a89a2e9a9f602641848047d"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"ac6ab81550da481992d69e3eaf5af05a224ad374","unresolved":false,"context_lines":[{"line_number":95,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"There is no graph logic for checks, meaning each check is meant to be run"},{"line_number":98,"context_line":"independently of other checks in the same set. So check 4 is not conditional"},{"line_number":99,"context_line":"on the result of check 2, for example."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The base framework is fairly simple as can be seen from the `initial change`_."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_a50621cd","line":98,"range":{"start_line":98,"start_character":50,"end_line":98,"end_character":57},"updated":"2018-09-10 19:18:16.000000000","message":"What does this check \"4\" mean?","commit_id":"5e4558853d8ffdd22a89a2e9a9f602641848047d"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"2483aaaa512084dc14491d12cc16a1c651437a6b","unresolved":false,"context_lines":[{"line_number":95,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"There is no graph logic for checks, meaning each check is meant to be run"},{"line_number":98,"context_line":"independently of other checks in the same set. So check 4 is not conditional"},{"line_number":99,"context_line":"on the result of check 2, for example."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The base framework is fairly simple as can be seen from the `initial change`_."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_dc5cec7e","line":98,"range":{"start_line":98,"start_character":50,"end_line":98,"end_character":57},"in_reply_to":"3f79a3b5_a50621cd","updated":"2018-09-15 15:39:24.000000000","message":"It\u0027s an example. Let\u0027s say a project has 5 checks total. They are run in serial but that doesn\u0027t mean check 4 in the list depends on the results of check 2 in the list. I\u0027ll try to re-word this.","commit_id":"5e4558853d8ffdd22a89a2e9a9f602641848047d"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"28828f1a884f4aaed611bd06b128651cee0c4906","unresolved":false,"context_lines":[{"line_number":95,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"There is no graph logic for checks, meaning each check is meant to be run"},{"line_number":98,"context_line":"independently of other checks in the same set. So check 4 is not conditional"},{"line_number":99,"context_line":"on the result of check 2, for example."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The base framework is fairly simple as can be seen from the `initial change`_."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_bdcf8e55","line":98,"range":{"start_line":98,"start_character":50,"end_line":98,"end_character":57},"in_reply_to":"3f79a3b5_dc5cec7e","updated":"2018-09-17 21:00:48.000000000","message":"Ah, I see. New one is good for me.","commit_id":"5e4558853d8ffdd22a89a2e9a9f602641848047d"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"ac6ab81550da481992d69e3eaf5af05a224ad374","unresolved":false,"context_lines":[{"line_number":96,"context_line":""},{"line_number":97,"context_line":"There is no graph logic for checks, meaning each check is meant to be run"},{"line_number":98,"context_line":"independently of other checks in the same set. So check 4 is not conditional"},{"line_number":99,"context_line":"on the result of check 2, for example."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The base framework is fairly simple as can be seen from the `initial change`_."},{"line_number":102,"context_line":"Each check is registered in the ``_upgrade_checks`` variable and the ``check``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_450b8dd4","line":99,"range":{"start_line":99,"start_character":17,"end_line":99,"end_character":24},"updated":"2018-09-10 19:18:16.000000000","message":"ditto","commit_id":"5e4558853d8ffdd22a89a2e9a9f602641848047d"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"0fbe7fe45f4e42a2f4c2d6ff746ffa48ee05e4d8","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  means having :oslo.config:group:`api_database`,"},{"line_number":46,"context_line":"  :oslo.config:group:`placement`, etc sections configured."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Candidates for automated upgrade checks are things in a projects upgrade"},{"line_number":49,"context_line":"  release notes which can be verified via the database. For example, when"},{"line_number":50,"context_line":"  upgrading to Cells v2 in Ocata, one required step was creating"},{"line_number":51,"context_line":"  \"cell mappings\" for ``cell0`` and ``cell1``. This can easily be verified by"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_89bca6b5","line":48,"range":{"start_line":48,"start_character":58,"end_line":48,"end_character":66},"updated":"2018-09-19 18:49:32.000000000","message":"project\u0027s","commit_id":"dc0259f97ae91490735e5b89701079ba4f2e595a"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"0fbe7fe45f4e42a2f4c2d6ff746ffa48ee05e4d8","unresolved":false,"context_lines":[{"line_number":183,"context_line":"stable branches. For example, a check was added for `bug 1759316`_ in Rocky"},{"line_number":184,"context_line":"which was also backported to stable/queens in case anyone upgrading from Pike"},{"line_number":185,"context_line":"to Queens would hit the same issue. Backportable checks are generally only"},{"line_number":186,"context_line":"made for latent bugs since someone that has already passed checks and upgraded"},{"line_number":187,"context_line":"to a given stable branch should not start failing after a patch release on that"},{"line_number":188,"context_line":"same branch. For this reason, any check being backported should have a release"},{"line_number":189,"context_line":"note with it."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_49176ea4","line":186,"range":{"start_line":186,"start_character":35,"end_line":186,"end_character":39},"updated":"2018-09-19 18:49:32.000000000","message":"who","commit_id":"dc0259f97ae91490735e5b89701079ba4f2e595a"}]}