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 suggested.
However, I think the minimum requirements for having a driver being documented should be third-party testing of Neutron patches. Otherwise the docs will become littered with a bunch of links to drivers/plugins with no indication of what actually works, which ultimately makes Neutron look bad. On Fri, Oct 10, 2014 at 1:28 PM, Vadivel Poonathan < vadivel.openst...@gmail.com> wrote: > 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 mentioned as "supported plugin/mechanism_driver for > so and so vendor equipments" in the docs.openstack.org, but without > having the actual plugin code to be posted in the main Openstack GIT > repository. > > Reason is that I dont have plan/bandwidth to go thru the entire process of > new plugin blue-print/development/review/testing etc as required by the > Openstack development community. Bcos this is already developed, tested and > released to some customers directly. Now I just want to get it to the > official Openstack documentation, so that more people can get this and use. > > The plugin package is made available to public from Ubuntu repository > along with necessary documentation. So people can directly get it from > Ubuntu repository and use it. All i need is to get listed in the > docs.openstack.org so that people knows that it exists and can be used > with any Openstack. > > Pls. confrim whether this is something possible?... > > Thanks again!.. > > Vad > -- > > On Fri, Oct 10, 2014 at 12:18 PM, Anne Gentle <a...@openstack.org> wrote: > >> >> >> 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 page >>> without having the actual plug-in code as part of the Openstack neutron >>> repository?... The actual plug-in is posted and available for the public to >>> download as Ubuntu package. But i need to mention somewhere in the >>> Openstack documentation that this new plugin is available for the public to >>> use along with its documentation. >>> >> >> We definitely want you to include pointers to vendor documentation in the >> OpenStack docs, but I'd prefer make sure they're gate tested before they >> get listed on docs.openstack.org. Drivers change enough >> release-to-release that it's difficult to keep up maintenance. >> >> Lately I've been talking to driver contributors (hypervisor, storage, >> networking) about the out-of-tree changes possible. I'd like to encourage >> even out-of-tree drivers to get listed, but to store their main documents >> outside of docs.openstack.org, if they are gate-tested. >> >> Anyone have other ideas here? >> >> Looping in the OpenStack-docs mailing list also. >> Anne >> >> >> >>> Pls. provide some insights into whether it is possible?.. and any >>> further info on this?.. >>> >>> Thanks, >>> >>> Vad >>> >>> -- >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStackemail@example.com >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStackfirstname.lastname@example.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev