)]}'
{"specs/ocata/ops-guide-upgrades.rst":[{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"51144519f3e54dde8fce30b37e59078275627b7e","unresolved":false,"context_lines":[{"line_number":24,"context_line":""},{"line_number":25,"context_line":"The nova, neutron, and keystone project teams have produced upgrade notes in"},{"line_number":26,"context_line":"the developer documentation that are beneficial to operators. The proposal is"},{"line_number":27,"context_line":"to include this information in the Operations Guide, along with swift and"},{"line_number":28,"context_line":"glance upgrade notes when they become available."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"The proposed structure for the Upgrades chapter in the Operations Guide"},{"line_number":31,"context_line":"would be as follows:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a629dbe_ab03a175","line":28,"range":{"start_line":27,"start_character":64,"end_line":28,"end_character":6},"updated":"2016-11-07 10:24:29.000000000","message":"I\u0027m not too sure if there is more options than just swift and glance too? Maybe check with Dolph? Could be wrong.","commit_id":"762decdcbf20b1e55bb5e473ee0d315cf7a9e8cf"},{"author":{"_account_id":6589,"name":"Jesse Keating","email":"jkeating@j2solutions.net","username":"jesse-keating"},"change_message_id":"2c2ebdd3e6b41bddcd076fc257c72478afb3f187","unresolved":false,"context_lines":[{"line_number":24,"context_line":""},{"line_number":25,"context_line":"The nova, neutron, and keystone project teams have produced upgrade notes in"},{"line_number":26,"context_line":"the developer documentation that are beneficial to operators. The proposal is"},{"line_number":27,"context_line":"to include this information in the Operations Guide, along with swift and"},{"line_number":28,"context_line":"glance upgrade notes when they become available."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"The proposed structure for the Upgrades chapter in the Operations Guide"},{"line_number":31,"context_line":"would be as follows:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a629dbe_dc1dd867","line":28,"range":{"start_line":27,"start_character":64,"end_line":28,"end_character":6},"in_reply_to":"9a629dbe_ab03a175","updated":"2016-11-08 00:32:00.000000000","message":"Ideally there would be upgrade notes for ALL the projects. SOME of the projects will have complicated steps providing limited impact upgrades, where as others may be more generic, but there should be content covering as many of the projects as possible","commit_id":"762decdcbf20b1e55bb5e473ee0d315cf7a9e8cf"},{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"81f62d865abcdd644380c5d9af80722dd9bf69d4","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Work items"},{"line_number":83,"context_line":"----------"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"* Add `keystone \u003chttp://docs.openstack.org/developer/keystone/upgrading.html\u003e`_"},{"line_number":86,"context_line":"  `nova \u003chttp://docs.openstack.org/developer/nova/upgrade.html\u003e`_ , and"},{"line_number":87,"context_line":"  `neutron \u003chttp://docs.openstack.org/developer/neutron/devref/upgrade.html\u003e`_"},{"line_number":88,"context_line":"  upgrade notes."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"* Add swift and glance upgrade notes when they become available."},{"line_number":91,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a629dbe_39260217","line":88,"range":{"start_line":85,"start_character":0,"end_line":88,"end_character":16},"updated":"2016-11-07 12:53:34.000000000","message":"Just recently I\u0027ve wrote similar reference for Cinder [1].\n\n[1] https://review.openstack.org/#/c/393395/","commit_id":"762decdcbf20b1e55bb5e473ee0d315cf7a9e8cf"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"db8319c6b8e24c3395c70f78402e083085594298","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Work items"},{"line_number":83,"context_line":"----------"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"* Add `keystone \u003chttp://docs.openstack.org/developer/keystone/upgrading.html\u003e`_"},{"line_number":86,"context_line":"  `nova \u003chttp://docs.openstack.org/developer/nova/upgrade.html\u003e`_ , and"},{"line_number":87,"context_line":"  `neutron \u003chttp://docs.openstack.org/developer/neutron/devref/upgrade.html\u003e`_"},{"line_number":88,"context_line":"  upgrade notes."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"* Add swift and glance upgrade notes when they become available."},{"line_number":91,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a629dbe_83816192","line":88,"range":{"start_line":85,"start_character":0,"end_line":88,"end_character":16},"updated":"2016-11-07 12:06:49.000000000","message":"Let\u0027s get docs liasons buy in from these projects that we move the files out - and that they remove the content from their repos.","commit_id":"762decdcbf20b1e55bb5e473ee0d315cf7a9e8cf"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":35,"context_line":"The proposed structure for the Upgrades chapter in the Operations Guide"},{"line_number":36,"context_line":"would be as follows:"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- Pre-upgrade considerations"},{"line_number":39,"context_line":"  - Upgrade planning"},{"line_number":40,"context_line":"  - Pre-upgrade testing environment"},{"line_number":41,"context_line":"  - Upgrade levels"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_d32fab3c","line":38,"updated":"2016-11-21 11:07:56.000000000","message":"Feels like these bits might better live inside the \"Upgrade a service\" section?","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":38,"context_line":"- Pre-upgrade considerations"},{"line_number":39,"context_line":"  - Upgrade planning"},{"line_number":40,"context_line":"  - Pre-upgrade testing environment"},{"line_number":41,"context_line":"  - Upgrade levels"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"- General upgrade process"},{"line_number":44,"context_line":"  - Prerequisites"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_f3ae6780","line":41,"updated":"2016-11-21 11:07:56.000000000","message":"For Nova, you really don\u0027t need to do this any more. The discussion is really around optionally opting into rolling upgrades by setting something like: compute_level\u003dAuto, and sending the SIG_HUP signal to all services once all services are running the new version.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  - Pre-upgrade testing environment"},{"line_number":41,"context_line":"  - Upgrade levels"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"- General upgrade process"},{"line_number":44,"context_line":"  - Prerequisites"},{"line_number":45,"context_line":"  - Perform a backup"},{"line_number":46,"context_line":"  - Manage repositories"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_9330d3ea","line":43,"updated":"2016-11-21 11:07:56.000000000","message":"I would rather we went for this Ops focused grouping:\n\n* non-impacting preparations\n* maintenance window (possibly impacting work)\n* non-impacting cleanup","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":44,"context_line":"  - Prerequisites"},{"line_number":45,"context_line":"  - Perform a backup"},{"line_number":46,"context_line":"  - Manage repositories"},{"line_number":47,"context_line":"  - Upgrade packages on each node"},{"line_number":48,"context_line":"  - Update services"},{"line_number":49,"context_line":"  - Final steps"},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_b3fdcf0a","line":47,"updated":"2016-11-21 11:07:56.000000000","message":"You really need the old and new versions of the software installed side by side on the same node, so switching over is a simple service restart.\n\nI think package upgrades are a \"special case\", where you can\u0027t do the ideal switch over.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"ca3ec1c5e6bedc10ad1731808a4e0631c015586a","unresolved":false,"context_lines":[{"line_number":44,"context_line":"  - Prerequisites"},{"line_number":45,"context_line":"  - Perform a backup"},{"line_number":46,"context_line":"  - Manage repositories"},{"line_number":47,"context_line":"  - Upgrade packages on each node"},{"line_number":48,"context_line":"  - Update services"},{"line_number":49,"context_line":"  - Final steps"},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a74a57a_1773cfb2","line":47,"in_reply_to":"7a77a97e_b3fdcf0a","updated":"2016-11-23 05:49:08.000000000","message":"ok, thanks for the info.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  - Update services"},{"line_number":49,"context_line":"  - Final steps"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"- Upgrade a service"},{"line_number":52,"context_line":"  - Upgrade the Networking service"},{"line_number":53,"context_line":"  - Upgrade the Identity service"},{"line_number":54,"context_line":"  - Upgrade the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_135cc3ec","line":51,"updated":"2016-11-21 11:07:56.000000000","message":"I think its worth having a section on the recommended upgrade order. I guess probably part of the general upgrade process?\n\nI think it is probably something like:\n\n* perform the non-impacting upgrade preparations for all services\n* performing (possibly) impacting maintenance for the services in the order: Identity, Object storage, Image, Block Storage, Networking, Nova.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"633d800137c3e4f39bbf9d781c3d5270f256a218","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  - Update services"},{"line_number":49,"context_line":"  - Final steps"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"- Upgrade a service"},{"line_number":52,"context_line":"  - Upgrade the Networking service"},{"line_number":53,"context_line":"  - Upgrade the Identity service"},{"line_number":54,"context_line":"  - Upgrade the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_932b7394","line":51,"in_reply_to":"7a77a97e_135cc3ec","updated":"2016-11-21 11:16:12.000000000","message":"I should note, I totally just made that list up. Not sure we have reach consensus on that list yet, but such a list needs to exist.\n\nIts probably worth saying that version N of services aims to support running with both version N-1 and version N of any dependent services, however that is not actually tested upstream. The hope is to test one specific \"integrated\" order for the upgrade. Testing all possible combinations people might pick just isn\u0027t feasible.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"ca3ec1c5e6bedc10ad1731808a4e0631c015586a","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  - Update services"},{"line_number":49,"context_line":"  - Final steps"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"- Upgrade a service"},{"line_number":52,"context_line":"  - Upgrade the Networking service"},{"line_number":53,"context_line":"  - Upgrade the Identity service"},{"line_number":54,"context_line":"  - Upgrade the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a74a57a_94035d0f","line":51,"in_reply_to":"7a77a97e_135cc3ec","updated":"2016-11-23 05:49:08.000000000","message":"See http://docs.openstack.org/ops-guide/ops-upgrades.html#update-services","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"ca3ec1c5e6bedc10ad1731808a4e0631c015586a","unresolved":false,"context_lines":[{"line_number":48,"context_line":"  - Update services"},{"line_number":49,"context_line":"  - Final steps"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"- Upgrade a service"},{"line_number":52,"context_line":"  - Upgrade the Networking service"},{"line_number":53,"context_line":"  - Upgrade the Identity service"},{"line_number":54,"context_line":"  - Upgrade the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a74a57a_f708132b","line":51,"in_reply_to":"7a77a97e_932b7394","updated":"2016-11-23 05:49:08.000000000","message":"Does http://docs.openstack.org/ops-guide/ops-upgrades.html#upgrade-levels cover it?","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"633d800137c3e4f39bbf9d781c3d5270f256a218","unresolved":false,"context_lines":[{"line_number":53,"context_line":"  - Upgrade the Identity service"},{"line_number":54,"context_line":"  - Upgrade the Compute service"},{"line_number":55,"context_line":"  - Upgrade the Block Storage service"},{"line_number":56,"context_line":"  - Upgrade the Object Storage service"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"- Roll back a failed upgrade"},{"line_number":59,"context_line":"  - Roll back an OpenStack environment"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_165cb1ec","line":56,"updated":"2016-11-21 11:16:12.000000000","message":"Actually, I think there are two upgrade processes/flows we should document:\n\n* quick upgrade (involves downtime, works well with packages, and still do DB migrations up front (where supported) to remove some downtime)\n* minimum downtime upgrade (requires more advanced orchestration, but has the most downtime)","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  - Upgrade the Block Storage service"},{"line_number":56,"context_line":"  - Upgrade the Object Storage service"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"- Roll back a failed upgrade"},{"line_number":59,"context_line":"  - Roll back an OpenStack environment"},{"line_number":60,"context_line":"  - Roll back the Identity service"},{"line_number":61,"context_line":"  - Roll back the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_33f8dfc4","line":58,"updated":"2016-11-21 11:07:56.000000000","message":"So its not really supported today. The rollback looses changes to the system that happened since your DB backup. So it really should be a last resort.\n\nI guess thats not true for all services (swift?), and I know there are plans to fix it / test a better approach.\n\nI guess I would put less emphasis on this section myself.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"5d17c850b44a665651daab59eb5e3a4276778a9f","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  - Upgrade the Block Storage service"},{"line_number":56,"context_line":"  - Upgrade the Object Storage service"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"- Roll back a failed upgrade"},{"line_number":59,"context_line":"  - Roll back an OpenStack environment"},{"line_number":60,"context_line":"  - Roll back the Identity service"},{"line_number":61,"context_line":"  - Roll back the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a74a57a_ce4f1e32","line":58,"in_reply_to":"5a74a57a_b74cdb77","updated":"2016-11-29 10:02:15.000000000","message":"Looking at what we have, its probably just a case of adding more big yellow warning messages around the likely data loss and the lack of testing around rollback.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"ca3ec1c5e6bedc10ad1731808a4e0631c015586a","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  - Upgrade the Block Storage service"},{"line_number":56,"context_line":"  - Upgrade the Object Storage service"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"- Roll back a failed upgrade"},{"line_number":59,"context_line":"  - Roll back an OpenStack environment"},{"line_number":60,"context_line":"  - Roll back the Identity service"},{"line_number":61,"context_line":"  - Roll back the Compute service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a74a57a_b74cdb77","line":58,"in_reply_to":"7a77a97e_33f8dfc4","updated":"2016-11-23 05:49:08.000000000","message":"So we should remove the section? See http://docs.openstack.org/ops-guide/ops-upgrades.html#rolling-back-a-failed-upgrade","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7da9aa6a9ef8e268feb1d8a4075234cb88cd25c5","unresolved":false,"context_lines":[{"line_number":60,"context_line":"  - Roll back the Identity service"},{"line_number":61,"context_line":"  - Roll back the Compute service"},{"line_number":62,"context_line":"  - Roll back the Block Storage service"},{"line_number":63,"context_line":"  - Roll back the Object Storage service"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Alternatives"},{"line_number":66,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_f35667cd","line":63,"updated":"2016-11-21 11:07:56.000000000","message":"You probably want Image in the above lists.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"633d800137c3e4f39bbf9d781c3d5270f256a218","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* Leave as is."},{"line_number":69,"context_line":"* Provide links to the developer documentation in the Operations Guide."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Implementation"},{"line_number":72,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":73,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a77a97e_f66c95d2","line":70,"updated":"2016-11-21 11:16:12.000000000","message":"I would recommend not having any version specific upgrade notes (beyond saying the first version that the documented procedure works on).","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"ca3ec1c5e6bedc10ad1731808a4e0631c015586a","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* Leave as is."},{"line_number":69,"context_line":"* Provide links to the developer documentation in the Operations Guide."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Implementation"},{"line_number":72,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":73,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a74a57a_9748bf5d","line":70,"in_reply_to":"7a77a97e_f66c95d2","updated":"2016-11-23 05:49:08.000000000","message":"Yeah, we removed version-specific content and made it more generic because it was difficult to maintain.","commit_id":"f28d220f1a505ffeec498bfbace503460f067336"}]}