Doug Wiegley <[email protected]> wrote:
What is the plan for out of tree objects derived from neutron, and out of
tree projects that are using the current neutron objects? Specifically,
the ones which *can’t* use the REST API, because they’re for something
loaded directly into neutron-server (core plugins, service plugins, etc).
Will they work? Is our live upgrade strategy going to be labeled
“reference only”?
For subprojects that plug into neutron, nothing should change on the first
phase: we will try to keep all [sort of] ‘public’ methods behave in the old
way, returning explicit dicts to callers. That said, we will need to look
into returning actual objects to callers later in the effort.
One thing that may help us to return objects to components that are not
aware of them is the compatibility layer that provides __getitem__
interface to objects. We already apply the interface to all objects in
neutron tree:
https://git.openstack.org/cgit/openstack/neutron/tree/neutron/objects/base.py?id=4c65e2ff1efd2f60a0812d7cbe56c267bb27b289#n72
In some far future we may also look at dropping support for the dict like
interactions [obviously going thru some deprecation process]. But we are
currently far from it, and we’ll manage it when we get there.
Ihar
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
