Open Stack

On 04/16/2014 06:00 PM, Fuente, Pablo A wrote:
> Hi guys,
> 
> I would like to open a discussion related to OpenStack upgrades ( I mean
> moving from one version to another, for example Havana to Icehouse).
> 
> As you probably know, this is a big issue, since there is no silver
> bullet to do it. For that reason, I am thinking  in an option to provide
> more input prior to do an upgrade.
> 
> The idea is to generate an interoperability matrix, where devops can see
> if an specific commit works with all the available OpenStack versions,
> distinguishing among the different components. For example, you could
> see if  the Nova X commit is or not backward compatible with the
> Grizzly/Havana/Icehouse versions of Keystone/Neutron/Cinder/...
> 
> Do you think this matrix would be useful in the upgrade tasks? 

i think if you do it for each commit will be more useful for clouds that
follow trunk that ones that upgrade each release.

if i'm going to upgrade from havana to icehouse i won't look at each
commit, just the final result, like
'i can/can't use Havana's nova with Icehouse's keystone' that data could
be extracted from that big matrix (lot of commits btw each release for
each component)


it sounds extremely useful for people thinking on moving it's cloud to a
CD model :)


how will you generate that matrix? adding tags to commits or running
fine-grained tempest-like tests?


-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333