Open Stack

Is there a reason that you are starting a new project instead of contributing to
The networking-ovs-dpdk puppet module?

Networking-ovs-dpdk was created to host both the integration code with neutron and then deployment tool
Support for deploying ovs with dpdk for differnet tools.

Currently we support devstack and we have developed a puppet module.
The puppet module was developed with the express intention of integrating it with 
Fuel, packstack and trippleo at a later date. It was created to be a reusable module for
Other tools to use and build on top of.

I will be working on kolla support upstream in kolla this cycle with networking-ovs-dpdk providing
Source install support in addition the binary install support that will be submitted to kolla.

A fule plugin(developed in opnfv) was planned to be added to this repo but that has now been
Abandoned as support is been added to fuel core instead.

If there is a good technical reason for a separate repo then that is ok but otherwise it
Seams wasteful to start another project to develop a puppet module to install ovs with dpdk.

Are there any featues missing form netoworking-ovs-dpdk puppet module that you require?
it should be noted that we will be adding support for binary installs from package manages
and persistent installs (auto loading kernel driver, persistent binding of nics) this cycle but if you have
any other feature gaps we would be happy to hear about them.

Regards
Sean.
 



> -----Original Message-----
> From: Saravanan KR [mailto:skramaja at redhat.com]
> Sent: Friday, July 08, 2016 8:33 AM
> To: OpenStack Development Mailing List (not for usage questions) <openstack-
> dev at lists.openstack.org>
> Cc: Emilien Macchi <emacchi at redhat.com>; Jaganathan Palanisamy
> <jpalanis at redhat.com>; Vijay Chundury <vchundur at redhat.com>
> Subject: Re: [openstack-dev] [puppet] Request to add puppet-dpdk module
> 
> Also, there is a repository networking-ovs-dpdk[1] for all the dpdk related
> changes including puppet. We considered both (puppet-vswitch and networking-
> ovs-dpdk).
> 
> And we had chat with Emilien about this. His suggestion is to have it as a separate
> project to make the modules cleaner like 'puppet-dpdk'.
> 
> Regards,
> Saravanan KR
> 
> [1] https://github.com/openstack/networking-ovs-dpdk
> 
> On Fri, Jul 8, 2016 at 2:36 AM, Russell Bryant <rbryant at redhat.com> wrote:
> >
> >
> > On Thu, Jul 7, 2016 at 5:12 AM, Saravanan KR <skramaja at redhat.com> wrote:
> >>
> >> Hello,
> >>
> >> We are working on blueprint [1] to integrate DPDK with tripleo. In
> >> the process, we are planning to add a new puppet module "puppet-dpdk"
> >> for the required puppet changes.
> >>
> >> The initial version of the repository is at github [2]. Note that the
> >> changes are not complete yet. It is in progress.
> >>
> >> Please let us know your views on including this new module.
> >>
> >> Regards,
> >> Saravanan KR
> >>
> >> [1] https://blueprints.launchpad.net/tripleo/+spec/tripleo-ovs-dpdk
> >> [2] https://github.com/krsacme/puppet-dpdk
> >
> >
> > I took a quick look at Emilien's request.  In general, including this
> > functionality in the puppet openstack project makes sense to me.
> >
> > It looks like this is installing and configuring openvswitch-dpdk.
> > Have you considered integrating DPDK awareness into the existing
> > puppet-vswitch that configures openvswitch?  Why is a separate puppet-dpdk
> needed?
> >
> > --
> > Russell Bryant
> >
> >
> ______________________________________________________________
> ________
> > ____ OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> ______________________________________________________________
> ____________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev