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 <[email protected]> wrote: > > > On Thu, Jul 7, 2016 at 5:12 AM, Saravanan KR <[email protected]> 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: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
