)]}'
{"pages/user-guide/0070-introduction.rst":[{"author":{"_account_id":8787,"name":"Dmitry Borodaenko","email":"angdraug@gmail.com","username":"angdraug"},"change_message_id":"b4e56cfae5fe9ffe83fcffba4cd0ea835bec10b8","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Note that you can manage an existing 5.0 environment"},{"line_number":14,"context_line":"along with new 5.0.1 environments from Fuel 5.0.1."},{"line_number":15,"context_line":"See :ref:`upgrade-ug` for instructions."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Before you do the procedures in this document,"},{"line_number":18,"context_line":"you should work through the information and procedures in the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"baada198_38898526","line":15,"updated":"2014-07-12 01:03:20.000000000","message":"Seems slightly out of place, I expected something along the lines of \"if you already have a deployed fuel master node based on v5.0, go to upgrade-ug; if you\u0027re deploying from scratch, stay here and read on\"","commit_id":"61d8dee3fa9de2173aa94aba8c016bd2b03bdffa"},{"author":{"_account_id":10014,"name":"Meg McRoberts","email":"DreidelLhasa@yahoo.com","username":"SstackScribe"},"change_message_id":"f01d42ea485d96cef8adbff6c996b7ccfeb8215a","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Note that you can manage an existing 5.0 environment"},{"line_number":14,"context_line":"along with new 5.0.1 environments from Fuel 5.0.1."},{"line_number":15,"context_line":"See :ref:`upgrade-ug` for instructions."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Before you do the procedures in this document,"},{"line_number":18,"context_line":"you should work through the information and procedures in the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"baada198_d8d889f1","line":15,"in_reply_to":"baada198_38898526","updated":"2014-07-12 01:18:43.000000000","message":"Done","commit_id":"61d8dee3fa9de2173aa94aba8c016bd2b03bdffa"}],"pages/user-guide/8000-upgrade.rst":[{"author":{"_account_id":8967,"name":"Miroslav Anashkin","email":"manashkin@mirantis.com","username":"manashkin"},"change_message_id":"8e4086e8bbc030a16bd818f0c4d821132ea5ed29","unresolved":false,"context_lines":[{"line_number":29,"context_line":"that manages an existing Mirantis OpenStack 5.0 cloud environment:"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"#. SHOULD WE ADVISE A BACKUP?"},{"line_number":32,"context_line":"   DO THEY NEED TO SHUT DOWN THE CLOUD ENVIRONMENT?"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"#. Download the upgrade tarball from"},{"line_number":35,"context_line":"   `\u003chttp://software.mirantis.com\u003e`."}],"source_content_type":"text/x-rst","patch_set":4,"id":"baada198_a6c7a163","line":32,"updated":"2014-07-09 18:17:09.000000000","message":"They don\u0027t need to shut down running OpenStack installations.\nThey only should not upgrade master node when there are installations in progress.","commit_id":"b036fd03e53c8ba86bb5d4b2690b0b2170e6ec25"},{"author":{"_account_id":10014,"name":"Meg McRoberts","email":"DreidelLhasa@yahoo.com","username":"SstackScribe"},"change_message_id":"15bbd51eb35f70e1638da0e084c3468ab40260cf","unresolved":false,"context_lines":[{"line_number":29,"context_line":"that manages an existing Mirantis OpenStack 5.0 cloud environment:"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"#. SHOULD WE ADVISE A BACKUP?"},{"line_number":32,"context_line":"   DO THEY NEED TO SHUT DOWN THE CLOUD ENVIRONMENT?"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"#. Download the upgrade tarball from"},{"line_number":35,"context_line":"   `\u003chttp://software.mirantis.com\u003e`."}],"source_content_type":"text/x-rst","patch_set":4,"id":"baada198_8afff400","line":32,"in_reply_to":"baada198_a6c7a163","updated":"2014-07-10 00:39:36.000000000","message":"Done","commit_id":"b036fd03e53c8ba86bb5d4b2690b0b2170e6ec25"},{"author":{"_account_id":8392,"name":"Aleksey Kasatkin","email":"akasatkin@mirantis.com","username":"aleksey"},"change_message_id":"4b06dd3e8fed619eddc291ba83d7c44426909b20","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    ::"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"       cd /var/tmp"},{"line_number":49,"context_line":"       tar -xf xxx.tar"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. Run upgrade script from that same directory:"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"baada198_3bc65c4a","line":49,"updated":"2014-07-09 09:19:55.000000000","message":"No necessity to copy tarball. \n\nFrom tarball directory:\n\ntar -xf xxx.tar -C /var/tmp\n\ncd /var/tmp\n\n./upgrade.sh","commit_id":"b036fd03e53c8ba86bb5d4b2690b0b2170e6ec25"},{"author":{"_account_id":10014,"name":"Meg McRoberts","email":"DreidelLhasa@yahoo.com","username":"SstackScribe"},"change_message_id":"15bbd51eb35f70e1638da0e084c3468ab40260cf","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    ::"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"       cd /var/tmp"},{"line_number":49,"context_line":"       tar -xf xxx.tar"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. Run upgrade script from that same directory:"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"baada198_4a4b1c59","line":49,"in_reply_to":"baada198_3bc65c4a","updated":"2014-07-10 00:39:36.000000000","message":"I reworded all of this a bit.  They can do what they want but doesn\u0027t it make sense to put the tarball under /var?  Of course, people can do what they want to but the \"simple\" instructions seem to be \"put tarball in /var/tmp\", cd to /var/tmp, etc...","commit_id":"b036fd03e53c8ba86bb5d4b2690b0b2170e6ec25"},{"author":{"_account_id":8392,"name":"Aleksey Kasatkin","email":"akasatkin@mirantis.com","username":"aleksey"},"change_message_id":"24c0a9c5c5d5d6f510e76ddf2eeafd0877b25b8a","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    ::"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"       cd /var/tmp"},{"line_number":49,"context_line":"       tar -xf xxx.tar"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. Run upgrade script from that same directory:"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"baada198_95238ca6","line":49,"in_reply_to":"baada198_4a4b1c59","updated":"2014-07-10 07:01:00.000000000","message":"Done","commit_id":"b036fd03e53c8ba86bb5d4b2690b0b2170e6ec25"},{"author":{"_account_id":8392,"name":"Aleksey Kasatkin","email":"akasatkin@mirantis.com","username":"aleksey"},"change_message_id":"cc0367b07e8552be174707dc018d3c2cc881f06a","unresolved":false,"context_lines":[{"line_number":64,"context_line":"the following message will appear on the Fuel UI:"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"   New release available: Icehouse on CentOS 6.5 (2014.1.1-5.0.1)"},{"line_number":67,"context_line":"   [WILL THERE BE AN UBUNTU MESSAGE?  FUEL MASTER ONLY RUNS CentOS...]"}],"source_content_type":"text/x-rst","patch_set":5,"id":"baada198_3574809b","line":67,"updated":"2014-07-10 07:00:55.000000000","message":"There will be corresponding Ubuntu message. \"Releases\" are about target deployments not master node deployment.","commit_id":"cb5d88c3161ba6964f7886268f7022acdadeec2f"},{"author":{"_account_id":10014,"name":"Meg McRoberts","email":"DreidelLhasa@yahoo.com","username":"SstackScribe"},"change_message_id":"310bba50530ea572e2cb031875f843c2da158134","unresolved":false,"context_lines":[{"line_number":64,"context_line":"the following message will appear on the Fuel UI:"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"   New release available: Icehouse on CentOS 6.5 (2014.1.1-5.0.1)"},{"line_number":67,"context_line":"   [WILL THERE BE AN UBUNTU MESSAGE?  FUEL MASTER ONLY RUNS CentOS...]"}],"source_content_type":"text/x-rst","patch_set":5,"id":"baada198_c6a9dcde","line":67,"in_reply_to":"baada198_3574809b","updated":"2014-07-10 08:44:17.000000000","message":"Thanks for the clarification -- it\u0027s fixed.","commit_id":"cb5d88c3161ba6964f7886268f7022acdadeec2f"},{"author":{"_account_id":8749,"name":"Evgeniy L","email":"eli@mirantis.com","username":"evgeniyl"},"change_message_id":"f935180b99b99c44a3dcc1ee19c3a3083eab1016","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    ::"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"       ./upgrade.sh"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The upgrade process can take 30-60 minutes."},{"line_number":63,"context_line":"When it is complete,"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_865d247c","line":60,"updated":"2014-07-10 09:05:01.000000000","message":"Despite the fact that we tested cases with interruption and user will be able to run script again, can we add some warning, with suggestion not to interrupt upgrade script? We have operations like images uploading which take some time and user might think that the script hanged and press Ctrl+C or something like that.","commit_id":"a489f57bf0aaaa0a6d6e2244eb3e685665dae1fd"},{"author":{"_account_id":8749,"name":"Evgeniy L","email":"eli@mirantis.com","username":"evgeniyl"},"change_message_id":"aafc591ce6b1f475957c17d4d232cac1075514e7","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"    ::"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"       ./upgrade.sh"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The upgrade process can take 30-60 minutes."},{"line_number":63,"context_line":"Note that some operations such as uploading images take some time,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"baada198_f6ed9cb8","line":60,"updated":"2014-07-10 16:47:05.000000000","message":"Will duplicate comment from patch 6\n\nDespite the fact that we tested cases with interruption and user will be able to run script again, can we add some warning, with suggestion not to interrupt upgrade script? We have operations like images uploading which take some time and user might think that the script hanged and press Ctrl+C or something like that.","commit_id":"3d0ee4c2a97c3ce89619a5d3c8340261556e159f"},{"author":{"_account_id":8392,"name":"Aleksey Kasatkin","email":"akasatkin@mirantis.com","username":"aleksey"},"change_message_id":"e94aa32e0592122b7435feea137bf6f4b1ba5de2","unresolved":false,"context_lines":[{"line_number":65,"context_line":"thinking that it has hung."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"When the upgrade is complete,"},{"line_number":68,"context_line":"one of the following messages will appear on the Fuel UI:"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"   New release available: Icehouse on Ubuntu 12.04.4 (2014.1.1-5.0.1)"},{"line_number":71,"context_line":"   New release available: Icehouse on CentOS 6.5 (2014.1.1-5.0.1)"}],"source_content_type":"text/x-rst","patch_set":7,"id":"baada198_efaa3019","line":68,"updated":"2014-07-10 12:29:20.000000000","message":"Both messages should appear. Fuel 5.0 have 2 releases (one for CentOS and one for Ubuntu). After Fuel upgrade user will be able to use updated versions of each of these releases (there will be 2 releases for the each of 2 OSes after upgrade).","commit_id":"3d0ee4c2a97c3ce89619a5d3c8340261556e159f"},{"author":{"_account_id":8787,"name":"Dmitry Borodaenko","email":"angdraug@gmail.com","username":"angdraug"},"change_message_id":"b4e56cfae5fe9ffe83fcffba4cd0ea835bec10b8","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Fuel 5.0.1 provides the first phase of the in-place upgrades"},{"line_number":7,"context_line":"for Mirantis OpenStack."},{"line_number":8,"context_line":"If you have a functional Fuel 5.0 cloud environment,"},{"line_number":9,"context_line":"you can install the 5.0.1 onto the Fuel Master Node."},{"line_number":10,"context_line":"After you do this, your new Fuel 5.0.1 Fuel console"}],"source_content_type":"text/x-rst","patch_set":9,"id":"baada198_38a265ae","line":7,"updated":"2014-07-12 01:03:20.000000000","message":"The above two lines do not have enough context to be useful, you only explain the other three phases further down. I think you can just drop this sentence.","commit_id":"61d8dee3fa9de2173aa94aba8c016bd2b03bdffa"},{"author":{"_account_id":10014,"name":"Meg McRoberts","email":"DreidelLhasa@yahoo.com","username":"SstackScribe"},"change_message_id":"f01d42ea485d96cef8adbff6c996b7ccfeb8215a","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Fuel 5.0.1 provides the first phase of the in-place upgrades"},{"line_number":7,"context_line":"for Mirantis OpenStack."},{"line_number":8,"context_line":"If you have a functional Fuel 5.0 cloud environment,"},{"line_number":9,"context_line":"you can install the 5.0.1 onto the Fuel Master Node."},{"line_number":10,"context_line":"After you do this, your new Fuel 5.0.1 Fuel console"}],"source_content_type":"text/x-rst","patch_set":9,"id":"baada198_98ea9172","line":7,"in_reply_to":"baada198_38a265ae","updated":"2014-07-12 01:18:43.000000000","message":"Done","commit_id":"61d8dee3fa9de2173aa94aba8c016bd2b03bdffa"}]}