I remembered I saw somewhere about how to upgrade, (step by step in updating from J to K or others) I think it's best and suitable way to use this kind of 'different version' talking to make compute host alive during system upgrade.
so I believe controller should be upgrade first the compute node to be update set by set that means Kilo conductor should works with Juno compute but on the contrary I didn't see a value for supporting it.... Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC From: Jay Pipes <jaypi...@gmail.com> To: openstack-dev@lists.openstack.org Date: 08/17/2015 05:01 PM Subject: Re: [openstack-dev] [nova] compute <-> conductor and version compatibility 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 nova-compute (Kilo). I tried > in comment #3 of [1] to rationalize if this is a valid setup or not > and I failed... > If someone with more experience and knowledge could help there and > clarify it also for other users in the future, that would be awesome. > > [1] https://bugs.launchpad.net/nova/+bug/1483321 No, that's not valid behaviour. You need to upgrade the controller infrastructure (conductor, API nodes, etc) before any compute nodes. Best, -jay __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev