[openstack-dev] Neutron documentation to update about new vendor plugin, but without code in repository?
Anne Gentle
anne at openstack.org
Fri Oct 10 19:18:46 UTC 2014
On Fri, Oct 10, 2014 at 2:11 PM, Vadivel Poonathan <
vadivel.openstack at 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
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141010/354091e9/attachment.html>
More information about the OpenStack-dev
mailing list