Re: [openstack-dev] [cinder] Object backporting and the associated service

2016-01-18 Thread Duncan Thomas
On 5 January 2016 at 18:55, Ryan Rossiter wrote: > This is definitely good to know. Are you planning on setting up something > off to the side of o.vo within that holds a dictionary of all values for a > release? Something like: > > {‘liberty’: {‘volume’: ‘1.3’, …},

Re: [openstack-dev] [cinder] Object backporting and the associated service

2016-01-18 Thread Michał Dulko
On 01/18/2016 03:31 PM, Duncan Thomas wrote: > On 5 January 2016 at 18:55, Ryan Rossiter > wrote: > > This is definitely good to know. Are you planning on setting up > something off to the side of o.vo within that holds a

Re: [openstack-dev] [cinder] Object backporting and the associated service

2016-01-05 Thread Ryan Rossiter
> On Jan 5, 2016, at 7:13 AM, Michał Dulko wrote: > > On 01/04/2016 11:41 PM, Ryan Rossiter wrote: >> My first question is: what will be handling the object backports that the >> different cinder services need? In Nova, we have the conductor service, >> which handles

Re: [openstack-dev] [cinder] Object backporting and the associated service

2016-01-05 Thread Michał Dulko
On 01/04/2016 11:41 PM, Ryan Rossiter wrote: > My first question is: what will be handling the object backports that the > different cinder services need? In Nova, we have the conductor service, which > handles all of the messy RPC and DB work. When anyone needs something > backported, they ask

[openstack-dev] [cinder] Object backporting and the associated service

2016-01-04 Thread Ryan Rossiter
Hey everybody, your favorite versioned objects guy is back! So as I’m helping out more and more with the objects stuff around Cinder, I’m starting to notice something that may be a problem with rolling upgrades/object backporting. Feel free to say “you’re wrong” at any point during this email,