fuel-dev team mailing list archive

[Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>]

On Fri, Apr 11, 2014 at 2:11 PM, Aleksey Kasatkin <akasatkin@xxxxxxxxxxxx>wrote:

>
> Folks,
>
> There are several options to implement patching of OpenStack in UI/API:
>
> 1. Rollback to previously deployed version can be initiated automatically
> or using UI/API (with separate button "Rollback"). AFAIC, manual rollback
> will be suitable in situation where we need to find reasons of failure or
> cluster remains in operational state (failure is not fatal).
>
Ok

>  2. Upgrade/Downgrade options:
>
It is patching, not upgrade. Upgrade is when we upgrade to new OpenStack
release, or another major milestone, which requires DB migrations.

>     a. One button "Upgrade" and drop-down list with all versions which can
> be upgraded/downgraded to.
>
Patch, with the list of versions we can migrate to. As far as I know from
D.Ilyin, we will be able to downgrade only to the version which was before
the migration. BTW, how are we gonna track whether we can downgrade or not?
If we already downgraded, for example, you won't be able to downgrade more.

>     b. Two buttons: "Upgrade", "Downgrade" with separate lists of versions.
>
> Please share your thoughts and proposals here.
>
> Thanks,
> Aleksey Kasatkin
>
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Mike Scherbakov
#mihgen