I wrote up Aleksey's instructions -- please review. I know this needs work but the release is imminent so we should start looking at this.
https://review.openstack.org/105324 Specific concerns: - I need the name of the tarball -- if it's gzip'ed, I'll need to modify the instructions - Please verify that I have the mount instructions correct for CentOS - I do not say anything about how to do this using a remote control utility such as ipmitool -- should I? If so, what should I say? Thanks much! meg On Fri, Jul 4, 2014 at 4:17 AM, Aleksey Kasatkin <akasat...@mirantis.com> wrote: > > It seems that public link to tarball is not defined yet. > All operations will be done via command shell. > > Current commands' sequence is: > 1. Download tarball to master node to "/var/..." (e.g. to "/var/tmp") It's > because there may be not enough disk space when you run it from "/root/" . > 2. Extract tarball contents to the same directory: "tar -xf > {tarball_name}" . > 3. Run upgrade script from that directory: "./upgrade.sh" . > > That's it. Upgrade process can get about 30-60 minutes. > > The message like "2014-07-04 08:28:02 INFO 8153 (openstack) upgrade is > done!" will appear when upgrade is finished successfully. > Notifications will appear in UI then: > > - > New release avaialble: Icehouse on Ubuntu 12.04.4 (2014.1.1-5.0.1) > - > New release avaialble: Icehouse on CentOS 6.5 (2014.1.1-5.0.1) > > It seems that upgrade algorithm will be the same in production. > > > > Aleksey Kasatkin > > > > On Fri, Jul 4, 2014 at 12:48 PM, Meg McRoberts <mmcrobe...@mirantis.com> > wrote: > >> Thank for this, Aleksey. I think I get it -- I will rewrite the >> descriptions in the Release Notes >> and you can review them. >> >> So where does one get this upgrade tarball and how does one install it? >> Will the Fuel UI handle >> any of this or is it shell commands only? >> >> meg >> >> >> On Fri, Jul 4, 2014 at 12:11 AM, Aleksey Kasatkin <akasat...@mirantis.com >> > wrote: >> >>> >>> Hi, >>> >>> I'm participating in development of this feature. >>> >>> *>>> 4. User then upgrades to 5.0.1 from the Mirantis OpenStack 5.0.1 >>> ISO* >>> >>> As far as I know, the only way to upgrade Fuel Master Node from 5.0 to >>> 5.0.1 will be running upgrade from an upgrade tarball (user will be able to >>> manage the previously deployed environments then). >>> User will be able to get clean installation of Fuel Master Node using >>> 5.0.1 ISO (user will not be able to manage the previously deployed >>> environments with this Fuel Master Node then). >>> >>> >>> Aleksey Kasatkin >>> >>> >>> >>> On Thu, Jul 3, 2014 at 2:31 AM, Meg McRoberts <mmcrobe...@mirantis.com> >>> wrote: >>> >>>> Thanks for the clarification, David. This means that the feature >>>> description in the 5.0 Release Notes is wrong -- I'll work on it. >>>> >>>> meg >>>> >>>> >>>> On Wed, Jul 2, 2014 at 7:16 AM, David Easter <deas...@mirantis.com> >>>> wrote: >>>> >>>>> Just to clarify, the current upgrade capability is limited to >>>>> upgrading the Fuel Master Node itself and not the previously deployed >>>>> environments. However, it is expected that an upgraded Fuel Master Node >>>>> will be able to continue managing previously deployed environments. Basic >>>>> use case would be: >>>>> >>>>> 1. User installs Fuel from the Mirantis OpenStack 5.0 ISO >>>>> 2. User deploys an OpenStack environment using the provided >>>>> hardened packages in the ISO (Icehouse 2014.1) >>>>> 3. The environment successfully deploys and is up and running >>>>> properly >>>>> 4. User then upgrades to 5.0.1 from the Mirantis OpenStack 5.0.1 >>>>> ISO >>>>> 5. The Fuel Master Node is now version 5.0.1 >>>>> 6. This 5.0.1 Fuel Master Node must continue to provide the >>>>> ability to manage the previously deployed 5.0 environment, including >>>>> log >>>>> management, health check, add and remove nodes, etc. >>>>> 7. This 5.0.1 Fuel Master Node also deploys the newer hardened >>>>> packages found in the Mirantis OpenStack 5.0.1 ISO (Icehouse 2014.1.1) >>>>> into >>>>> new environments >>>>> >>>>> In 5.0.1, it is not expected that the Fuel Master Node will enable the >>>>> previously deployed 5.0 environment to be updated to 5.0.1. Patching of >>>>> existing environments is tentatively expected in the 5.1 milestone and >>>>> upgrading of the environment (e.g. from Icehouse to Juno) is tentatively >>>>> expected in the 6.x milestones. >>>>> >>>>> Thanks, >>>>> - David J. Easter >>>>> Director of Product Management, Mirantis, Inc. >>>>> >>>>> http://openstacksv.com/ >>>>> >>>>> From: Meg McRoberts <mmcrobe...@mirantis.com> >>>>> Date: Wednesday, July 2, 2014 at 2:17 AM >>>>> To: Evgeniy L <e...@mirantis.com> >>>>> Cc: "fuel-dev@lists.launchpad.net" <fuel-dev@lists.launchpad.net> >>>>> Subject: Re: [Fuel-dev] Fuel upgrade procedures >>>>> >>>>> Hi, Evgeniy, >>>>> Thanks for responding. Yes, I need instructions for upgrading to >>>>> 5.0.1. I believe we have two >>>>> scenarios: one where one upgrades ones MOSt environment and one where >>>>> one upgrades >>>>> Fuel but continues to run the MOSt 5.0 environment, perhaps alongside >>>>> new 5.0.1 environments. >>>>> >>>>> Vitaly, if you can provide screen shots, that would help a lot. >>>>> >>>>> Scratch up the info in whatever way is easiest for you and I'll take >>>>> it from there. >>>>> >>>>> meg >>>>> >>>>> >>>>> On Wed, Jul 2, 2014 at 1:08 AM, Evgeniy L <e...@mirantis.com> wrote: >>>>> >>>>>> Hi Meg, >>>>>> >>>>>> I one of the developers who are working on this feature, what >>>>>> information do you need? Do you need some instruction how to run upgrade >>>>>> procedure? >>>>>> >>>>>> Also Vitaly Kramskikh is our UI developer, I think he can provide >>>>>> some screenshots. >>>>>> >>>>>> >>>>>> On Tue, Jul 1, 2014 at 3:35 AM, Meg McRoberts < >>>>>> mmcrobe...@mirantis.com> wrote: >>>>>> >>>>>>> 5.0.1 is our first Fuel release that allows customers to (a) upgrade >>>>>>> from the >>>>>>> previous release and (b) run Fuel to support environments using >>>>>>> different >>>>>>> versions. At least, this is the hope and the promise in the 5.0 >>>>>>> Release Notes. >>>>>>> >>>>>>> I need information about how to do this for the 5.0.1 docs -- who >>>>>>> can help? >>>>>>> >>>>>>> meg >>>>>>> >>>>>>> -- >>>>>>> Mailing list: https://launchpad.net/~fuel-dev >>>>>>> Post to : fuel-dev@lists.launchpad.net >>>>>>> Unsubscribe : https://launchpad.net/~fuel-dev >>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>> >>>>>>> >>>>>> >>>>> -- Mailing list: https://launchpad.net/~fuel-dev Post to : >>>>> fuel-dev@lists.launchpad.net Unsubscribe : >>>>> https://launchpad.net/~fuel-dev More help : >>>>> https://help.launchpad.net/ListHelp >>>>> >>>> >>>> >>>> -- >>>> Mailing list: https://launchpad.net/~fuel-dev >>>> Post to : fuel-dev@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~fuel-dev >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> >>> >> >
-- Mailing list: https://launchpad.net/~fuel-dev Post to : fuel-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
