[openstack-dev] [Heat] Versioned objects upgrade patterns

Zane Bitter zbitter at redhat.com
Tue May 17 19:54:43 UTC 2016

On 17/05/16 15:40, Crag Wolfe wrote:
> Another thing I am wondering about: if my particular object is not
> exposed by RPC, is it worth making it a full blown o.vo or not? I.e, I
> can do the 3 steps over 3 releases just in the object's .py file -- what
> additional value do I get from o.vo?

It's more of a cargo-cult thing ;)

(Given that *none* of the versioned objects in Heat are exposed over 
RPC, the additional value you get is consistency and a nice place to 
abstract whatever weirdness is going on in the database at any given 
time so that it doesn't leak into the rest of the code.)


More information about the OpenStack-dev mailing list