Structured Object Fields
The field specification of NovaObjects is not very well-defined and requires us to spread the serialization logic all over the place. Fields should be objects themselves, which encapsulate coercion and serialization routines.
Blueprint information
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Avoid caching quota.QUOTAS in Quotas object
Addressed by: https:/
Migrate InstanceAction and InstanceActionEvent objects to Fields
Addressed by: https:/
Migrate InstanceGroup object to Fields
Addressed by: https:/
Migrate Migration object to Fields
Addressed by: https:/
Migrate SecurityGroup object to Fields
Addressed by: https:/
Migrate NovaPersistentO
Addressed by: https:/
Migrate Service object to Fields
Addressed by: https:/
Migrate InstanceFault object to Fields
Addressed by: https:/
Migrate Quotas object to Fields
Addressed by: https:/
Migrate ComputeNode object to Fields
Addressed by: https:/
Migrate Instance object to Fields
Addressed by: https:/
Make the base object infrastructure use Fields
Addressed by: https:/
Migrate InstanceInfoCache object to Fields
Addressed by: https:/
Migrate PciDevice object to Fields
Addressed by: https:/
Fix conductor's object change detection
Addressed by: https:/
Remove transitional callable field interface
Addressed by: https:/
Migrate some tests that were using callable fields
Addressed by: https:/
Migrate KeyPair object to Fields
Addressed by: https:/
Migrate Aggregate object to Fields
Addressed by: https:/
Make field object support transitional call-based interface
Addressed by: https:/
Add Field model and tests
Addressed by: https:/
Make a note about Object deepcopy helper
Addressed by: https:/
Fix conductor's object change detection
Gerrit topic: https:/
Addressed by: https:/
Make Object FieldType take an object name instead of a class
