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?...
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
in the docs themselves. Thoughts? Feelings? More discussion,
please. And thank you for the responses so far.
Anne
[1] https://wiki.openstack.org/wiki/HypervisorSupportMatrix
On Fri, Oct 10, 2014 at 1:28 PM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
Hi Anne,
Thanks for your
On Mon, Oct 13, 2014 at 11:33 AM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
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
, 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 link/pointers
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
taken
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
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.
https://wiki.openstack.org/wiki/HypervisorSupportMatrix
Anne
Thanks,
Kyle
On Thu, Oct 23, 2014 at 9:44 AM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote
and storage
drivers as well.
https://wiki.openstack.org/wiki/HypervisorSupportMatrix
Anne
Thanks,
Kyle
On Thu, Oct 23, 2014 at 9:44 AM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
Kyle,
Gentle reminder... when you get a chance!..
Anne,
In case, if i need to send
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 wrote
wrote:
On Thu, Oct 23, 2014 at 12:35 PM, Vadivel Poonathan
vadivel.openst...@gmail.com wrote:
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
@Armando,
Okay, so if I understand you correctly, you're saying that was easier for
you to go entirely out of tree, and that you have done so already. Okay,
good for you, problem solved!
One point that should be clear here is that, if someone is completely
comfortable with being entirely out of
Hi,
Once the Neutron's sub-project is released to pyPI, where does it show that
this sub-project release is associated with Liberty release of Openstack?..
I tried to see it in the Liberty Release notes, but it doesn't have any
info about the supported/released vendor plug-ins/drivers.
I see the
/drivers...
https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers
https://wiki.openstack.org/wiki/NeutronDevelopment
https://wiki.openstack.org/wiki/Neutron
Thanks,
Vad
--
On Fri, Jul 10, 2015 at 4:54 PM, Armando M. arma...@gmail.com wrote:
On 10 July 2015 at 16:01, Vadivel Poonathan
Hi,
I have a Neutron plugin (actually a mechanism_driver under ML2) developed
for Alcatel-Lucent Omniswitches and is currently being used. But it is not
part of Neutron upstream, nor listed in the docs/wiki section. I tried to
make it part of Kilo release, but that was when the decomposition
publishing of
packages to pypi:
networking-ale-omniswitch
networking-arista
On Wed, Sep 30, 2015 at 11:56 AM, Kyle Mestery <mest...@mestery.com> wrote:
> On Tue, Sep 29, 2015 at 8:04 PM, Kyle Mestery <mest...@mestery.com> wrote:
>
>> On Tue, Sep 29, 2015 at 2:36 PM, Vad
Hi,
As per the Sub-Project Release process - i would like to tag and release
the following sub-project as part of upcoming Liberty release.
The process says talk to one of the member of 'neutron-release' group. I
couldn’t find a group mail-id for this group. Hence I am sending this email
to the
17 matches
Mail list logo