On 07/15/2016 08:36 AM, Hayes, Graham wrote:
On 14/07/2016 21:20, Matt Riedemann wrote:
And does this also include plugins within projects, like storage
backends in cinder and hypervisor drivers in nova?
This is aimed at cross project interaction. So, if there is a project in
projects.yaml that is a backend, or a hypervisor driver, it should.
However, in the proposal, there is a choice that projects can make -
all in tree, or all plugins. The point of the proposal is equality of
access for the community.
What would that mean in practice for Nova? Nothing would really change
- they have decided to do in tree.
99% of deliverables tagged type:service will have no impact from this,
the change will be in projects that are used by teams across the
community (CLI, Docs, UI etc), and provide a way for these projects
to integrate with them.
These integration points should be the same for *all* projects.
What integration points exactly are you referring to? Can you provide a
specific example that Designate has run into issues with?
Nova has been pushing for a few releases now on getting rid of plug
points since they are barriers to interoperability.
Well, nova's plugins were barriers to interoperability, for other
projects they are the only mechanism for interoperability.
Perhaps there is some terminology problem here, but plugins absolutely
do NOT enable interoperability between clouds. They are the antithesis
of interoperability points.
The REST APIs (and for projects that support it, the versioned
notifications payloads) should be the *only* interoperability and
integration points that projects should rely on.
Best,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
