On 8/17/2015 10:19 AM, Dan Smith wrote:
Is this documented somewhere?
I did a bit of digging and couldn't find anywhere that explicitly
required that for the J->K upgrade. Certainly it was documented for the
I->J upgrade.
It's our model, so I don't think we need to document it for each cycl
> Is this documented somewhere?
>
> I did a bit of digging and couldn't find anywhere that explicitly
> required that for the J->K upgrade. Certainly it was documented for the
> I->J upgrade.
It's our model, so I don't think we need to document it for each cycle
since we don't expect it to chang
On 08/17/2015 08:59 AM, Jay Pipes wrote:
On 08/17/2015 10:41 AM, Markus Zoeller wrote:
I have the impression that more and more people try to run OpenStack
in a "mixed-releases-mode" and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of
> No, that's not valid behaviour. You need to upgrade the controller
> infrastructure (conductor, API nodes, etc) before any compute nodes.
Yep.
--Dan
signature.asc
Description: OpenPGP digital signature
__
OpenStack Devel
bm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
From: Jay Pipes
To: openstack-dev@lists.openstack.org
Date: 08/17/2015 05:01 PM
Subject: Re: [openstack-dev] [nova] compute <-> conductor and version
On 08/17/2015 10:41 AM, Markus Zoeller wrote:
I have the impression that more and more people try to run OpenStack
in a "mixed-releases-mode" and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of [1] runs a nova-conductor (Juno) with a n
I have the impression that more and more people try to run OpenStack
in a "mixed-releases-mode" and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of [1] runs a nova-conductor (Juno) with a nova-compute (Kilo). I tried
in comment #3 of [1]
