openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] ovsdb: Expose vhost-user socket directory in
> ovsdb
>
>
> Hi Robert,
>
> Robert Wojciechowicz writes:
>
> > In order to correctly interoperate with Openstack and ODL,
> > the vhost-user socket directory must b
/checkpatch.py is ok.
> >
> > Thanks,
> > Antonio
> >
> >> -Original Message-
> >> From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Robert
> >> Wojciechowicz
> >> Sent: Monday, May 23, 2016 11:29 AM
> >> To:
Hi Robert,
Robert Wojciechowicz writes:
> In order to correctly interoperate with Openstack and ODL,
> the vhost-user socket directory must be exposed from OVS via OVSDB.
> Different distros may package OVS in different ways,
> so the locations of these sockets may vary depending on how
> ovs-v
to:dev-boun...@openvswitch.org] On Behalf Of Robert
>> Wojciechowicz
>> Sent: Monday, May 23, 2016 11:29 AM
>> To: dev@openvswitch.org
>> Subject: [ovs-dev] [PATCH] ovsdb: Expose vhost-user socket directory
>> in ovsdb
>>
>> In order to correctly interoperate
ay 23, 2016 11:29 AM
> To: dev@openvswitch.org
> Subject: [ovs-dev] [PATCH] ovsdb: Expose vhost-user socket directory
> in ovsdb
>
> In order to correctly interoperate with Openstack and ODL,
> the vhost-user socket directory must be exposed from OVS via OVSDB.
> Different dis
: [ovs-dev] [PATCH] ovsdb: Expose vhost-user socket directory in
> ovsdb
>
> Hi,
>
> this patch is actually a supplement to the conversion of DPDK configuration
> from command line to DB (http://openvswitch.org/pipermail/dev/2016-
> April/070308.html).
> Currently the full v
Hi,
this patch is actually a supplement to the conversion of DPDK configuration
from command line to DB
(http://openvswitch.org/pipermail/dev/2016-April/070308.html).
Currently the full vhost-user socket directory consists of two components:
ovs_rundir and subdirectory for vhost-user sockets. Com
In order to correctly interoperate with Openstack and ODL,
the vhost-user socket directory must be exposed from OVS via OVSDB.
Different distros may package OVS in different ways,
so the locations of these sockets may vary depending on how
ovs-vswitchd has been started. Some clients need informatio
On Thu, Jan 28, 2016 at 10:57:35AM +, Robert Wojciechowicz wrote:
> In order to correctly interoperate with Openstack and ODL,
> the vhost-user socket directory must be exposed from OVS via OVSDB.
> Different distros may package OVS in different ways,
> so the locations of these sockets may var
Hi Robert,
Aaron was working on the same and more (permissions&ownership)
=> netdev-dpdk: Support user cfg vhost socket perms (
http://openvswitch.org/pipermail/dev/2015-December/063567.html)
To be resubmitted, It depends on the discussion and acceptance of the
current 7th revision of the groundw
In order to correctly interoperate with Openstack and ODL,
the vhost-user socket directory must be exposed from OVS via OVSDB.
Different distros may package OVS in different ways,
so the locations of these sockets may vary depending on how
ovs-vswitchd has been started. Some clients need informatio
11 matches
Mail list logo
