m...@samsung.com>; Assaf
> Muller <as...@redhat.com>
> Subject: Re: [ovs-dev] [RFC 0/2] dpdk: minor refactor of the
> initialization step
>
> On 04/11/2018 02:21 PM, Aaron Conole wrote:
> > "Mooney, Sean K" <sean.k.moo...@intel.com> writes:
> >
On 04/11/2018 02:21 PM, Aaron Conole wrote:
> "Mooney, Sean K" writes:
>
>>> -Original Message-
>>> From: Aaron Conole [mailto:acon...@redhat.com]
>>> Sent: Monday, April 9, 2018 4:32 PM
>>> To: Mooney, Sean K
>>> Cc:
"Mooney, Sean K" writes:
>> -Original Message-
>> From: Aaron Conole [mailto:acon...@redhat.com]
>> Sent: Monday, April 9, 2018 4:32 PM
>> To: Mooney, Sean K
>> Cc: d...@openvswitch.org; Stokes, Ian ; Kevin
>>
> -Original Message-
> From: Aaron Conole [mailto:acon...@redhat.com]
> Sent: Monday, April 9, 2018 4:32 PM
> To: Mooney, Sean K
> Cc: d...@openvswitch.org; Stokes, Ian ; Kevin
> Traynor ; Ilya Maximets
"Mooney, Sean K" writes:
> So just from a deployment tools point of view I would like to point out that
> This change could break existing workflow that deploy ovs in a docker
> container.
> Kolla ansible assumes that if the docker ovs_vswitchd container is
> still
So just from a deployment tools point of view I would like to point out that
This change could break existing workflow that deploy ovs in a docker container.
Kolla ansible assumes that if the docker ovs_vswitchd container is still
running that the
is infact running in dpdk mode when we set
Sometimes, DPDK initialization can fail, but ovs-vswitchd will abort in
that case. When that occurs, ovs-vswitchd will be restarted by the
monitor and immediately abort. This is rather unfriendly to users, who
would prefer to possibly correct the issue or at least, not have lots of
processes