Agreed on the requirements of test results to qualify the vendor plugin to
be listed in the upstream docs.
Is there any procedure/infrastructure currently available for this
purpose?..
Pls. fwd any link/pointers on those info.
Thanks,
Vad
--
On Mon, Oct 13, 2014 at 10:25 PM, Akihiro Motoki
On Tue, Oct 14, 2014 at 5:14 PM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
Agreed on the requirements of test results to qualify the vendor plugin to
be listed in the upstream docs.
Is there any procedure/infrastructure currently available for this
purpose?..
Pls. fwd any
Hi,
If the plan is to move ALL existing vendor specific plugins/drivers
out-of-tree, then having a place-holder within the OpenStack domain would
suffice, where the vendors can list their plugins/drivers along with their
documentation as how to install and use etc.
The main Openstack Neutron
The OpenStack dev and docs team dont have to worry about
gating/publishing/maintaining the vendor specific plugins/drivers.
I disagree about the gating part. If a vendor wants to have a link that
shows they are compatible with openstack, they should be reporting test
results on all patches. A
On Mon, Oct 13, 2014 at 6:44 PM, Kevin Benton blak...@gmail.com wrote:
The OpenStack dev and docs team dont have to worry about
gating/publishing/maintaining the vendor specific plugins/drivers.
I disagree about the gating part. If a vendor wants to have a link that
shows they are compatible
I agree with Kevin and Kyle. Even if we decided to use separate tree for neutron
plugins and drivers, they still will be regarded as part of the upstream.
These plugins/drivers need to prove they are well integrated with Neutron master
in some way and gating integration proves it is well tested
Hi,
How to include a new vendor plug-in (aka mechanism_driver in ML2 framework)
into the Openstack documentation?.. In other words, is it possible to
include a new plug-in in the Openstack documentation page without having
the actual plug-in code as part of the Openstack neutron repository?...
On Fri, Oct 10, 2014 at 2:11 PM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
Hi,
How to include a new vendor plug-in (aka mechanism_driver in ML2
framework) into the Openstack documentation?.. In other words, is it
possible to include a new plug-in in the Openstack documentation
Hi Anne,
Thanks for your immediate response!...
Just to clarify... I have developed and maintaining a Neutron plug-in (ML2
mechanism_driver) since Grizzly and now it is up-to-date with Icehouse. But
it was never listed nor part of the main Openstack releases. Now i would
like to have my plugin
I think you will probably have to wait until after the summit so we can see
the direction that will be taken with the rest of the in-tree
drivers/plugins. It seems like we are moving towards removing all of them
so we would definitely need a solution to documenting out-of-tree drivers
as you
On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton blak...@gmail.com wrote:
I think you will probably have to wait until after the summit so we can
see the direction that will be taken with the rest of the in-tree
drivers/plugins. It seems like we are moving towards removing all of them
so we
11 matches
Mail list logo
