Open Stack

> This patch set makes the extra_resources a list of object, instead of
> opaque json string. How do you think about that?

Sounds better to me, I'll go have a look.

> However, the compute resource object is different with current
> NovaObject, a) it has no corresponding table, but just a field in
> another table, and I assume it will have no save/update functions. b)
> it defines the functions for the object like alloc/free etc. Not sure
> if this is correct direction.

Having a NovaObject that isn't backed by a conventional SQLAlchemy model
is fine with me, FWIW.

--Dan