-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/12/14 16:59, Vadivel Poonathan wrote:
Hi Kyle and all,
Was there any conclusion in the design summit or the meetings
afterward about splitting the vendor plugins/drivers from the
mainstream neutron and documentation of out-of-tree
For anyone who had an interest in following this thread, they might want to
have a look at [1], and [2] (which is the tl;dr version [1]).
HTH
Armando
[1] https://review.openstack.org/#/c/134680
[2]
http://lists.openstack.org/pipermail/openstack-dev/2014-December/052346.html
Hi Kyle and all,
Was there any conclusion in the design summit or the meetings afterward
about splitting the vendor plugins/drivers from the mainstream neutron and
documentation of out-of-tree plugins/drivers?...
Thanks,
Vad
--
On Thu, Oct 23, 2014 at 11:27 AM, Kyle Mestery mest...@mestery.com
Edgar,
Did we get consensus on having a wiki page for non-upstreamed drivers for
Neutron?... or Are we waiting for summit outcome on the direction on how to
handle the vendor plug-ins/drivers ?
Thanks,
Vad
--
On Thu, Oct 23, 2014 at 12:07 PM, Vadivel Poonathan
vadivel.openst...@gmail.com
Kyle,
Gentle reminder... when you get a chance!..
Anne,
In case, if i need to send it to different group or email-id to reach Kyle
Mestery, pls. let me know. Thanks for your help.
Regards,
Vad
--
On Tue, Oct 21, 2014 at 8:51 AM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
Hi Kyle,
Vad:
The third-party CI is required for your upstream driver. I think
what's different from my reading of this thread is the question of
what is the requirement to have a driver listed in the upstream
documentation which is not in the upstream codebase. To my knowledge,
we haven't done this.
On Thu, Oct 23, 2014 at 10:31 AM, Kyle Mestery mest...@mestery.com wrote:
Vad:
The third-party CI is required for your upstream driver. I think
what's different from my reading of this thread is the question of
what is the requirement to have a driver listed in the upstream
documentation
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.
Thanks,
Edgar
From: Anne Gentle a...@openstack.orgmailto:a...@openstack.org
Reply-To: OpenStack Development Mailing
I forgot to mention that I can help to coordinate the creation and maintenance
of the wiki for non-upstreamed drivers for Neutron.
We need to be sure that we DO NOT confuse users with the current information
here:
https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers
I have been
Hi Kyle and Anne,
Thanks for the clarifications... understood and it makes sense.
However, per my understanding, the drivers (aka plugins) are meant to be
developed and supported by third-party vendors, outside of the OpenStack
community, and they are supposed to work as plug-n-play... they are
On Thu, Oct 23, 2014 at 9:49 AM, Edgar Magana edgar.mag...@workday.com
wrote:
I forgot to mention that I can help to coordinate the creation and
maintenance of the wiki for non-upstreamed drivers for Neutron.
[vad] Edgar, that would be nice!... but not sure whether it has to wait
till the
Hi Kyle,
Can you pls. comment on this discussion and confirm the requirements for
getting out-of-tree mechanism_driver listed in the supported plugin/driver
list of the Openstack Neutron docs.
Thanks,
Vad
--
On Mon, Oct 20, 2014 at 12:48 PM, Anne Gentle a...@openstack.org wrote:
On Mon, Oct
Hi,
* On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton blak...@gmail.com
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
On Mon, Oct 20, 2014 at 2:42 PM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
Hi,
* On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton blak...@gmail.com
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
14 matches
Mail list logo
