We're running mixed Juno and Kilo, and upgrading one component at a time.
Two issues with that so far:
1. The puppet modules don't play nice together (Juno/Kilo) - there was some
serious re-factor done between those releases and they don't work at all
together. I hacked the Juno modules to write K
We do run Cinder on dedicated controllers, though, so no mix of Kilo and Juno
services on
the controllers.
Cheers,
Arne
On 18 Nov 2015, at 13:19, Belmiro Moreira
mailto:moreira.belmiro.email.li...@gmail.com>>
wrote:
Hi Saverio,
we always upgrade one component at a time.
Cinder was one of th
Belmiro are you running cinder-api and cinder-volume on a controller
node with other Juno services, or cinder was on a dedicated server or
container ?
thanks
Saverio
2015-11-18 13:19 GMT+01:00 Belmiro Moreira
:
> Hi Saverio,
> we always upgrade one component at a time.
> Cinder was one of the f
Hi Saverio,
we always upgrade one component at a time.
Cinder was one of the first components that we upgraded to kilo,
meaning that other components (glance, nova, ...) were running Juno.
We didn't have any problem with this setup.
Belmiro
CERN
On Tue, Nov 17, 2015 at 6:01 PM, Saverio Proto wr
If you are doing this on the same server you are going to have many many issues
with olso.* libs being incompatible between releases (not just juno -> kilo but
all releases). I don't have specific knowledge around cinder, however on
separate machines/vm's we have run mismatched versions of othe
Hello there,
I need to quickly find a workaround to be able to use ceph object map
features for cinder volumes with rbd backend.
However, upgrading everything from Juno to Kilo will require a lot of
time for testing and updating all my puppet modules.
Do you think it is feasible to start updatin