On Fri, Jul 8, 2016 at 8:18 AM, Saravanan KR wrote:
> Thanks Emilien. I definitely agree with the preference for (1). It is
> simpler in choosing either vswitch::ovs or vswitch::dpdk for the
> deployment.
Cool, /me looking forward to see the patch, I'll help you to get it merged asap.
> Regards,
Thanks Emilien. I definitely agree with the preference for (1). It is
simpler in choosing either vswitch::ovs or vswitch::dpdk for the
deployment.
Regards,
Saravanan KR
On Fri, Jul 8, 2016 at 5:15 PM, Emilien Macchi wrote:
> On Fri, Jul 8, 2016 at 2:33 AM, Saravanan KR wrote:
>> Also, there is
On Fri, Jul 8, 2016 at 2:33 AM, Saravanan KR wrote:
> 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
> a
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-dp
On Thu, Jul 7, 2016 at 5:12 AM, Saravanan KR 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]
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
