> -Original Message-
> From: Aaron Conole [mailto:acon...@redhat.com]
> Sent: Monday, August 15, 2016 9:57 PM
> To: Daniele Di Proietto
> Cc: Mooney, Sean K ; dev@openvswitch.org
> Subject: Re: [ovs-dev] Remote OVS feature discovery
>
> Daniele Di Proietto writ
Daniele Di Proietto writes:
> 2016-08-15 11:39 GMT-07:00 Mooney, Sean K :
>
>>
>>
>>
>>
>> *From:* Daniele Di Proietto [mailto:diproiet...@ovn.org]
>> *Sent:* Monday, August 15, 2016 6:29 PM
>> *To:* Mooney, Sean K
>> *Cc:* dev@openvswitch.
2016-08-15 11:39 GMT-07:00 Mooney, Sean K :
>
>
>
>
> *From:* Daniele Di Proietto [mailto:diproiet...@ovn.org]
> *Sent:* Monday, August 15, 2016 6:29 PM
> *To:* Mooney, Sean K
> *Cc:* dev@openvswitch.org; Loftus, Ciara
> *Subject:* Re: [ovs-dev] Remote OVS featur
From: Daniele Di Proietto [mailto:diproiet...@ovn.org]
Sent: Monday, August 15, 2016 6:29 PM
To: Mooney, Sean K
Cc: dev@openvswitch.org; Loftus, Ciara
Subject: Re: [ovs-dev] Remote OVS feature discovery
Hi Sean,
I'm not familiar with OpenStack, so I'm not sure that my comments make
Hi Sean,
I'm not familiar with OpenStack, so I'm not sure that my comments make
sense for every possible use case.
I'm not 100% sure an explicit feature discovery interface is required. If
an interface is well designed it should be possible to discover features by
"probing". We never had any pr
Hi Sean,
I'm not familiar with OpenStack, so I'm not sure that my comments make
sense for every possible use case.
I'm not 100% sure an explicit feature discovery interface is required. If
an interface is well designed it should be possible to discover features by
"probing". We never had any pr
