Open Stack

Akshik, please include the address of the original mailing list in your replies.

> On 19 May 2016, at 22:17, Akshik dbk <akshik at outlook.com> wrote:
> 
> Hi Ihar,
> 
> Thanks for the response, 
> 
> yes, Fuel does not run in containers
> 
> correct me if I’m wrong, so upgrading neutron dependencies would have impact on other services as well?  
> 

If you colocate neutron (mitaka) services with other (kilo) services on the same node, and if they are not isolated in a container, they share runtime environment, including their python dependencies. I am not even sure your packaging system will allow you to install such a mixed environment. But if it will, all bets are off on whether it will work in any way since now kilo services will use (some) mitaka dependencies, which is definitely not supported by upstream.

> 
> From: Ihar Hrachyshka <ihrachys at redhat.com>
> Date: 20 May 2016 at 1:24:31 AM
> To: Akshik dbk <akshik at outlook.com>
> CC: openstack-operators at lists.openstack.org <openstack-operators at lists.openstack.org>
> Subject:  Re: [Openstack-operators] Neutron upgrade from Kilo to Mitaka 
> 
>> 
>> > On 19 May 2016, at 21:43, Akshik dbk <akshik at outlook.com> wrote: 
>> > 
>> >> Hi, 
>> >> 
>> >> I’m have a Fuel 7.0 based environment [kilo], wanted to upgrade the Neutron to Mitaka version. is it possible to upgrade Neutron alone to the Mitaka version. 
>> 
>> Developers don’t make any special effort to support mixed environments that span more than +1 release. It may or may not work. 
>> 
>> Even then the assumption is that your neutron services are using a runtime environment that is isolated from other (kilo) services. I think Fuel does not install services in containers, so they would need to run on separate nodes. 
>> 
>> Ihar