yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #34894
[Bug 1470154] [NEW] List objects should use obj_relationships
Public bug reported:
Nova's List-based objects have something called child_versions, which is
a naive mapping of the objects field and the version relationships
between the list object and the content object. This was created before
we generalized the work in obj_relationships, which normal objects now
use. The list-based objects still use child_versions, which means we
need a separate test and separate developer behaviors when updating
these.
For consistency, we should replace child_versions on all the list
objects with obj_relationships, remove the list-specific test in
test_objects.py, and make sure that the generalized tests properly cover
list objects and relationships between list and non-list objects.
** Affects: nova
Importance: Low
Assignee: Ryan Rossiter (rlrossit)
Status: Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1470154
Title:
List objects should use obj_relationships
Status in OpenStack Compute (Nova):
Confirmed
Bug description:
Nova's List-based objects have something called child_versions, which
is a naive mapping of the objects field and the version relationships
between the list object and the content object. This was created
before we generalized the work in obj_relationships, which normal
objects now use. The list-based objects still use child_versions,
which means we need a separate test and separate developer behaviors
when updating these.
For consistency, we should replace child_versions on all the list
objects with obj_relationships, remove the list-specific test in
test_objects.py, and make sure that the generalized tests properly
cover list objects and relationships between list and non-list
objects.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1470154/+subscriptions
Follow ups
References