<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I forgot to mention that I can help to coordinate the creation and maintenance of the wiki for non-upstreamed drivers for Neutron.</div>
<div>We need to be sure that we DO NOT confuse users with the current information here:</div>
<div><a href="https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers">https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers</a></div>
<div><br>
</div>
<div>I have been maintaining that wiki and I would like to keep just for upstreamed vendor-specific plugins/drivers. </div>
<div><br>
</div>
<div>Edgar</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Edgar Magana <<a href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, October 23, 2014 at 9:46 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, Kyle Mestery <<a href="mailto:mestery@mestery.com">mestery@mestery.com</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I second Anne’s and Kyle comments. Actually, I like very much the wiki part to provide some visibility for out-of-tree plugins/drivers but not into the official documentation.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Edgar</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, October 23, 2014 at 8:51 AM<br>
<span style="font-weight:bold">To: </span>Kyle Mestery <<a href="mailto:mestery@mestery.com">mestery@mestery.com</a>><br>
<span style="font-weight:bold">Cc: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 23, 2014 at 10:31 AM, Kyle Mestery <span dir="ltr">
<<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Vad:<br>
<br>
The third-party CI is required for your upstream driver. I think<br>
what's different from my reading of this thread is the question of<br>
what is the requirement to have a driver listed in the upstream<br>
documentation which is not in the upstream codebase. To my knowledge,<br>
we haven't done this. Thus, IMHO, we should NOT be utilizing upstream<br>
documentation to document drivers which are themselves not upstream.<br>
When we split out the drivers which are currently upstream in neutron<br>
into a separate repo, they will still be upstream. So my opinion here<br>
is that if your driver is not upstream, it shouldn't be in the<br>
upstream documentation. But I'd like to hear others opinions as well.<br>
<br>
</blockquote>
<div><br>
</div>
<div>This is my sense as well. </div>
<div><br>
</div>
<div>The hypervisor drivers are documented on the wiki, sometimes they're in-tree, sometimes they're not, but the state of testing is documented on the wiki. I think we could take this approach for network and storage drivers as well. </div>
<div><br>
</div>
<div><a href="https://wiki.openstack.org/wiki/HypervisorSupportMatrix">https://wiki.openstack.org/wiki/HypervisorSupportMatrix</a><br>
</div>
<div><br>
</div>
<div>Anne</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Thanks,<br>
Kyle<br>
<br>
On Thu, Oct 23, 2014 at 9:44 AM, Vadivel Poonathan<br>
<div class="">
<div class="h5"><<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
> Kyle,<br>
> Gentle reminder... when you get a chance!..<br>
><br>
> Anne,<br>
> In case, if i need to send it to different group or email-id to reach Kyle<br>
> Mestery, pls. let me know. Thanks for your help.<br>
><br>
> Regards,<br>
> Vad<br>
> --<br>
><br>
><br>
> On Tue, Oct 21, 2014 at 8:51 AM, Vadivel Poonathan<br>
> <<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
>><br>
>> Hi Kyle,<br>
>><br>
>> Can you pls. comment on this discussion and confirm the requirements for<br>
>> getting out-of-tree mechanism_driver listed in the supported plugin/driver<br>
>> list of the Openstack Neutron docs.<br>
>><br>
>> Thanks,<br>
>> Vad<br>
>> --<br>
>><br>
>> On Mon, Oct 20, 2014 at 12:48 PM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On Mon, Oct 20, 2014 at 2:42 PM, Vadivel Poonathan<br>
>>> <<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hi,<br>
>>>><br>
>>>> >>>> On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton <<a href="mailto:blak111@gmail.com">blak111@gmail.com</a>><br>
>>>> >>>> wrote:<br>
>>>> >>>>><br>
>>>> >>>>> I think you will probably have to wait until after the summit so<br>
>>>> >>>>> we can<br>
>>>> >>>>> see the direction that will be taken with the rest of the in-tree<br>
>>>> >>>>> drivers/plugins. It seems like we are moving towards removing all<br>
>>>> >>>>> of them so<br>
>>>> >>>>> we would definitely need a solution to documenting out-of-tree<br>
>>>> >>>>> drivers as<br>
>>>> >>>>> you suggested.<br>
>>>><br>
>>>> [Vad] while i 'm waiting for the conclusion on this subject, i 'm trying<br>
>>>> to setup the third-party CI/Test system and meet its requirements to get my<br>
>>>> mechanism_driver listed in the Kilo's documentation, in parallel.<br>
>>>><br>
>>>> Couple of questions/confirmations before i proceed further on this<br>
>>>> direction...<br>
>>>><br>
>>>> 1) Is there anything more required other than the third-party CI/Test<br>
>>>> requirements ??.. like should I still need to go-through the entire<br>
>>>> development process of submit/review/approval of the blue-print and code of<br>
>>>> my ML2 driver which was already developed and in-use?...<br>
>>>><br>
>>><br>
>>> The neutron PTL Kyle Mestery can answer if there are any additional<br>
>>> requirements.<br>
>>><br>
>>>><br>
>>>> 2) Who is the authority to clarify and confirm the above (and how do i<br>
>>>> contact them)?...<br>
>>><br>
>>><br>
>>> Elections just completed, and the newly elected PTL is Kyle Mestery,<br>
>>> <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-March/031433.html" target="_blank">
http://lists.openstack.org/pipermail/openstack-dev/2014-March/031433.html</a>.<br>
>>><br>
>>>><br>
>>>><br>
>>>> Thanks again for your inputs...<br>
>>>><br>
>>>> Regards,<br>
>>>> Vad<br>
>>>> --<br>
>>>><br>
>>>> On Tue, Oct 14, 2014 at 3:17 PM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On Tue, Oct 14, 2014 at 5:14 PM, Vadivel Poonathan<br>
>>>>> <<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
>>>>>><br>
>>>>>> Agreed on the requirements of test results to qualify the vendor<br>
>>>>>> plugin to be listed in the upstream docs.<br>
>>>>>> Is there any procedure/infrastructure currently available for this<br>
>>>>>> purpose?..<br>
>>>>>> Pls. fwd any link/pointers on those info.<br>
>>>>>><br>
>>>>><br>
>>>>> Here's a link to the third-party testing setup information.<br>
>>>>><br>
>>>>> <a href="http://ci.openstack.org/third_party.html" target="_blank">http://ci.openstack.org/third_party.html</a><br>
>>>>><br>
>>>>> Feel free to keep asking questions as you dig deeper.<br>
>>>>> Thanks,<br>
>>>>> Anne<br>
>>>>><br>
>>>>>><br>
>>>>>> Thanks,<br>
>>>>>> Vad<br>
>>>>>> --<br>
>>>>>><br>
>>>>>> On Mon, Oct 13, 2014 at 10:25 PM, Akihiro Motoki <<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>><br>
>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>> I agree with Kevin and Kyle. Even if we decided to use separate tree<br>
>>>>>>> for neutron<br>
>>>>>>> plugins and drivers, they still will be regarded as part of the<br>
>>>>>>> upstream.<br>
>>>>>>> These plugins/drivers need to prove they are well integrated with<br>
>>>>>>> Neutron master<br>
>>>>>>> in some way and gating integration proves it is well tested and<br>
>>>>>>> integrated.<br>
>>>>>>> I believe it is a reasonable assumption and requirement that a vendor<br>
>>>>>>> plugin/driver<br>
>>>>>>> is listed in the upstream docs. This is a same kind of question as<br>
>>>>>>> what vendor plugins<br>
>>>>>>> are tested and worth documented in the upstream docs.<br>
>>>>>>> I hope you work with the neutron team and run the third party<br>
>>>>>>> requirements.<br>
>>>>>>><br>
>>>>>>> Thanks,<br>
>>>>>>> Akihiro<br>
>>>>>>><br>
>>>>>>> On Tue, Oct 14, 2014 at 10:09 AM, Kyle Mestery <<a href="mailto:mestery@mestery.com">mestery@mestery.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>> > On Mon, Oct 13, 2014 at 6:44 PM, Kevin Benton <<a href="mailto:blak111@gmail.com">blak111@gmail.com</a>><br>
>>>>>>> > wrote:<br>
>>>>>>> >>>The OpenStack dev and docs team dont have to worry about<br>
>>>>>>> >>> gating/publishing/maintaining the vendor specific<br>
>>>>>>> >>> plugins/drivers.<br>
>>>>>>> >><br>
>>>>>>> >> I disagree about the gating part. If a vendor wants to have a link<br>
>>>>>>> >> that<br>
>>>>>>> >> shows they are compatible with openstack, they should be reporting<br>
>>>>>>> >> test<br>
>>>>>>> >> results on all patches. A link to a vendor driver in the docs<br>
>>>>>>> >> should signify<br>
>>>>>>> >> some form of testing that the community is comfortable with.<br>
>>>>>>> >><br>
>>>>>>> > I agree with Kevin here. If you want to play upstream, in whatever<br>
>>>>>>> > form that takes by the end of Kilo, you have to work with the<br>
>>>>>>> > existing<br>
>>>>>>> > third-party requirements and team to take advantage of being a part<br>
>>>>>>> > of<br>
>>>>>>> > things like upstream docs.<br>
>>>>>>> ><br>
>>>>>>> > Thanks,<br>
>>>>>>> > Kyle<br>
>>>>>>> ><br>
>>>>>>> >> On Mon, Oct 13, 2014 at 11:33 AM, Vadivel Poonathan<br>
>>>>>>> >> <<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
>>>>>>> >>><br>
>>>>>>> >>> Hi,<br>
>>>>>>> >>><br>
>>>>>>> >>> If the plan is to move ALL existing vendor specific<br>
>>>>>>> >>> plugins/drivers<br>
>>>>>>> >>> out-of-tree, then having a place-holder within the OpenStack<br>
>>>>>>> >>> domain would<br>
>>>>>>> >>> suffice, where the vendors can list their plugins/drivers along<br>
>>>>>>> >>> with their<br>
>>>>>>> >>> documentation as how to install and use etc.<br>
>>>>>>> >>><br>
>>>>>>> >>> The main Openstack Neutron documentation page can explain the<br>
>>>>>>> >>> plugin<br>
>>>>>>> >>> framework (ml2 type drivers, mechanism drivers, serviec plugin<br>
>>>>>>> >>> and so on)<br>
>>>>>>> >>> and its purpose/usage etc, then provide a link to refer the<br>
>>>>>>> >>> currently<br>
>>>>>>> >>> supported vendor specific plugins/drivers for more details. That<br>
>>>>>>> >>> way the<br>
>>>>>>> >>> documentation will be accurate to what is "in-tree" and limit the<br>
>>>>>>> >>> documentation of external plugins/drivers to have just a<br>
>>>>>>> >>> reference link. So<br>
>>>>>>> >>> its now vendor's responsibility to keep their driver's<br>
>>>>>>> >>> up-to-date and their<br>
>>>>>>> >>> documentation accurate. The OpenStack dev and docs team dont have<br>
>>>>>>> >>> to worry<br>
>>>>>>> >>> about gating/publishing/maintaining the vendor specific<br>
>>>>>>> >>> plugins/drivers.<br>
>>>>>>> >>><br>
>>>>>>> >>> The built-in drivers such as LinuxBridge or OpenVSwitch etc can<br>
>>>>>>> >>> continue<br>
>>>>>>> >>> to be "in-tree" and their documentation will be part of main<br>
>>>>>>> >>> Neutron's docs.<br>
>>>>>>> >>> So the Neutron is guaranteed to work with built-in<br>
>>>>>>> >>> plugins/drivers as per<br>
>>>>>>> >>> the documentation and the user is informed to refer the "external<br>
>>>>>>> >>> vendor<br>
>>>>>>> >>> plug-in page" for additional/specific plugins/drivers.<br>
>>>>>>> >>><br>
>>>>>>> >>><br>
>>>>>>> >>> Thanks,<br>
>>>>>>> >>> Vad<br>
>>>>>>> >>> --<br>
>>>>>>> >>><br>
>>>>>>> >>><br>
>>>>>>> >>> On Fri, Oct 10, 2014 at 8:10 PM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>><br>
>>>>>>> >>> wrote:<br>
>>>>>>> >>>><br>
>>>>>>> >>>><br>
>>>>>>> >>>><br>
>>>>>>> >>>> On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton<br>
>>>>>>> >>>> <<a href="mailto:blak111@gmail.com">blak111@gmail.com</a>> wrote:<br>
>>>>>>> >>>>><br>
>>>>>>> >>>>> I think you will probably have to wait until after the summit<br>
>>>>>>> >>>>> so we can<br>
>>>>>>> >>>>> see the direction that will be taken with the rest of the<br>
>>>>>>> >>>>> in-tree<br>
>>>>>>> >>>>> drivers/plugins. It seems like we are moving towards removing<br>
>>>>>>> >>>>> all of them so<br>
>>>>>>> >>>>> we would definitely need a solution to documenting out-of-tree<br>
>>>>>>> >>>>> drivers as<br>
>>>>>>> >>>>> you suggested.<br>
>>>>>>> >>>>><br>
>>>>>>> >>>>> However, I think the minimum requirements for having a driver<br>
>>>>>>> >>>>> being<br>
>>>>>>> >>>>> documented should be third-party testing of Neutron patches.<br>
>>>>>>> >>>>> Otherwise the<br>
>>>>>>> >>>>> docs will become littered with a bunch of links to<br>
>>>>>>> >>>>> drivers/plugins with no<br>
>>>>>>> >>>>> indication of what actually works, which ultimately makes<br>
>>>>>>> >>>>> Neutron look bad.<br>
>>>>>>> >>>><br>
>>>>>>> >>>><br>
>>>>>>> >>>> This is my line of thinking as well, expanded to "ultimately<br>
>>>>>>> >>>> makes<br>
>>>>>>> >>>> OpenStack docs look bad" -- a perception I want to avoid.<br>
>>>>>>> >>>><br>
>>>>>>> >>>> Keep the viewpoints coming. We have a crucial balancing act<br>
>>>>>>> >>>> ahead: users<br>
>>>>>>> >>>> need to trust docs and trust the drivers. Ultimately the<br>
>>>>>>> >>>> responsibility for<br>
>>>>>>> >>>> the docs is in the hands of the driver contributors so it seems<br>
>>>>>>> >>>> those should<br>
>>>>>>> >>>> be on a domain name where drivers control publishing and<br>
>>>>>>> >>>> OpenStack docs are<br>
>>>>>>> >>>> not a gatekeeper, quality checker, reviewer, or publisher.<br>
>>>>>>> >>>><br>
>>>>>>> >>>> We have documented the status of hypervisor drivers on an<br>
>>>>>>> >>>> OpenStack wiki<br>
>>>>>>> >>>> page. [1] To me, that type of list could be maintained on the<br>
>>>>>>> >>>> wiki page<br>
>>>>>>> >>>> better than in the docs themselves. Thoughts? Feelings? More<br>
>>>>>>> >>>> discussion,<br>
>>>>>>> >>>> please. And thank you for the responses so far.<br>
>>>>>>> >>>> Anne<br>
>>>>>>> >>>><br>
>>>>>>> >>>> [1] <a href="https://wiki.openstack.org/wiki/HypervisorSupportMatrix" target="_blank">
https://wiki.openstack.org/wiki/HypervisorSupportMatrix</a><br>
>>>>>>> >>>><br>
>>>>>>> >>>>><br>
>>>>>>> >>>>><br>
>>>>>>> >>>>> On Fri, Oct 10, 2014 at 1:28 PM, Vadivel Poonathan<br>
>>>>>>> >>>>> <<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Hi Anne,<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Thanks for your immediate response!...<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Just to clarify... I have developed and maintaining a Neutron<br>
>>>>>>> >>>>>> plug-in<br>
>>>>>>> >>>>>> (ML2 mechanism_driver) since Grizzly and now it is up-to-date<br>
>>>>>>> >>>>>> with Icehouse.<br>
>>>>>>> >>>>>> But it was never listed nor part of the main Openstack<br>
>>>>>>> >>>>>> releases. Now i would<br>
>>>>>>> >>>>>> like to have my plugin mentioned as "supported<br>
>>>>>>> >>>>>> plugin/mechanism_driver for<br>
>>>>>>> >>>>>> so and so vendor equipments" in the <a href="http://docs.openstack.org" target="_blank">
docs.openstack.org</a>, but<br>
>>>>>>> >>>>>> without having<br>
>>>>>>> >>>>>> the actual plugin code to be posted in the main Openstack GIT<br>
>>>>>>> >>>>>> repository.<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Reason is that I dont have plan/bandwidth to go thru the<br>
>>>>>>> >>>>>> entire process<br>
>>>>>>> >>>>>> of new plugin blue-print/development/review/testing etc as<br>
>>>>>>> >>>>>> required by the<br>
>>>>>>> >>>>>> Openstack development community. Bcos this is already<br>
>>>>>>> >>>>>> developed, tested and<br>
>>>>>>> >>>>>> released to some customers directly. Now I just want to get it<br>
>>>>>>> >>>>>> to the<br>
>>>>>>> >>>>>> official Openstack documentation, so that more people can get<br>
>>>>>>> >>>>>> this and use.<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> The plugin package is made available to public from Ubuntu<br>
>>>>>>> >>>>>> repository<br>
>>>>>>> >>>>>> along with necessary documentation. So people can directly get<br>
>>>>>>> >>>>>> it from<br>
>>>>>>> >>>>>> Ubuntu repository and use it. All i need is to get listed in<br>
>>>>>>> >>>>>> the<br>
>>>>>>> >>>>>> <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a> so that people knows that it exists and can<br>
>>>>>>> >>>>>> be used with<br>
>>>>>>> >>>>>> any Openstack.<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Pls. confrim whether this is something possible?...<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Thanks again!..<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> Vad<br>
>>>>>>> >>>>>> --<br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> On Fri, Oct 10, 2014 at 12:18 PM, Anne Gentle<br>
>>>>>>> >>>>>> <<a href="mailto:anne@openstack.org">anne@openstack.org</a>><br>
>>>>>>> >>>>>> wrote:<br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> On Fri, Oct 10, 2014 at 2:11 PM, Vadivel Poonathan<br>
>>>>>>> >>>>>>> <<a href="mailto:vadivel.openstack@gmail.com">vadivel.openstack@gmail.com</a>> wrote:<br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> Hi,<br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> How to include a new vendor plug-in (aka mechanism_driver in<br>
>>>>>>> >>>>>>>> ML2<br>
>>>>>>> >>>>>>>> framework) into the Openstack documentation?.. In other<br>
>>>>>>> >>>>>>>> words, is it<br>
>>>>>>> >>>>>>>> possible to include a new plug-in in the Openstack<br>
>>>>>>> >>>>>>>> documentation page<br>
>>>>>>> >>>>>>>> without having the actual plug-in code as part of the<br>
>>>>>>> >>>>>>>> Openstack neutron<br>
>>>>>>> >>>>>>>> repository?... The actual plug-in is posted and available<br>
>>>>>>> >>>>>>>> for the public to<br>
>>>>>>> >>>>>>>> download as Ubuntu package. But i need to mention somewhere<br>
>>>>>>> >>>>>>>> in the Openstack<br>
>>>>>>> >>>>>>>> documentation that this new plugin is available for the<br>
>>>>>>> >>>>>>>> public to use along<br>
>>>>>>> >>>>>>>> with its documentation.<br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> We definitely want you to include pointers to vendor<br>
>>>>>>> >>>>>>> documentation in<br>
>>>>>>> >>>>>>> the OpenStack docs, but I'd prefer make sure they're gate<br>
>>>>>>> >>>>>>> tested before they<br>
>>>>>>> >>>>>>> get listed on <a href="http://docs.openstack.org" target="_blank">
docs.openstack.org</a>. Drivers change enough<br>
>>>>>>> >>>>>>> release-to-release<br>
>>>>>>> >>>>>>> that it's difficult to keep up maintenance.<br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> Lately I've been talking to driver contributors (hypervisor,<br>
>>>>>>> >>>>>>> storage,<br>
>>>>>>> >>>>>>> networking) about the out-of-tree changes possible. I'd like<br>
>>>>>>> >>>>>>> to encourage<br>
>>>>>>> >>>>>>> even out-of-tree drivers to get listed, but to store their<br>
>>>>>>> >>>>>>> main documents<br>
>>>>>>> >>>>>>> outside of <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a>, if they are gate-tested.<br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> Anyone have other ideas here?<br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> Looping in the OpenStack-docs mailing list also.<br>
>>>>>>> >>>>>>> Anne<br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> Pls. provide some insights into whether it is possible?..<br>
>>>>>>> >>>>>>>> and any<br>
>>>>>>> >>>>>>>> further info on this?..<br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> Thanks,<br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> Vad<br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> --<br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> _______________________________________________<br>
>>>>>>> >>>>>>>> OpenStack-dev mailing list<br>
>>>>>>> >>>>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >>>>>>>><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> _______________________________________________<br>
>>>>>>> >>>>>>> OpenStack-dev mailing list<br>
>>>>>>> >>>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >>>>>>><br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> _______________________________________________<br>
>>>>>>> >>>>>> OpenStack-dev mailing list<br>
>>>>>>> >>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >>>>>><br>
>>>>>>> >>>>><br>
>>>>>>> >>>>><br>
>>>>>>> >>>>><br>
>>>>>>> >>>>> --<br>
>>>>>>> >>>>> Kevin Benton<br>
>>>>>>> >>>>><br>
>>>>>>> >>>>> _______________________________________________<br>
>>>>>>> >>>>> OpenStack-dev mailing list<br>
>>>>>>> >>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >>>>><br>
>>>>>>> >>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >>>>><br>
>>>>>>> >>>><br>
>>>>>>> >>>><br>
>>>>>>> >>>> _______________________________________________<br>
>>>>>>> >>>> OpenStack-dev mailing list<br>
>>>>>>> >>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >>>><br>
>>>>>>> >>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >>>><br>
>>>>>>> >>><br>
>>>>>>> >>><br>
>>>>>>> >>> _______________________________________________<br>
>>>>>>> >>> OpenStack-dev mailing list<br>
>>>>>>> >>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >>><br>
>>>>>>> >><br>
>>>>>>> >><br>
>>>>>>> >><br>
>>>>>>> >> --<br>
>>>>>>> >> Kevin Benton<br>
>>>>>>> >><br>
>>>>>>> >> _______________________________________________<br>
>>>>>>> >> OpenStack-dev mailing list<br>
>>>>>>> >> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>> >><br>
>>>>>>> ><br>
>>>>>>> > _______________________________________________<br>
>>>>>>> > OpenStack-dev mailing list<br>
>>>>>>> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> --<br>
>>>>>>> Akihiro Motoki <<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>><br>
>>>>>>><br>
>>>>>>> _______________________________________________<br>
>>>>>>> OpenStack-dev mailing list<br>
>>>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> OpenStack-dev mailing list<br>
>>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> OpenStack-dev mailing list<br>
>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> OpenStack-dev mailing list<br>
>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>><br>
><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>