On 24/4/2015, at 19:42, Armando M. arma...@gmail.com wrote:
On 24 April 2015 at 01:47, Miguel Angel Ajo Pelayo mangel...@redhat.com
mailto:mangel...@redhat.com wrote:
Hi Armando Salvatore,
On 23/4/2015, at 9:30, Salvatore Orlando sorla...@nicira.com
mailto:sorla...@nicira.com
Hi Armando Salvatore,
On 23/4/2015, at 9:30, Salvatore Orlando sorla...@nicira.com wrote:
On 23 April 2015 at 01:30, Armando M. arma...@gmail.com
mailto:arma...@gmail.com wrote:
On 22 April 2015 at 06:02, Miguel Angel Ajo Pelayo mangel...@redhat.com
mailto:mangel...@redhat.com
On 24 April 2015 at 01:47, Miguel Angel Ajo Pelayo mangel...@redhat.com
wrote:
Hi Armando Salvatore,
On 23/4/2015, at 9:30, Salvatore Orlando sorla...@nicira.com wrote:
On 23 April 2015 at 01:30, Armando M. arma...@gmail.com wrote:
On 22 April 2015 at 06:02, Miguel Angel Ajo Pelayo
On 23 April 2015 at 01:30, Armando M. arma...@gmail.com wrote:
On 22 April 2015 at 06:02, Miguel Angel Ajo Pelayo mangel...@redhat.com
wrote:
Hi everybody,
In the latest QoS meeting, one of the topics was a discussion about
how to implement
QoS [1] either as in core, or as a service
Hi everybody,
In the latest QoS meeting, one of the topics was a discussion about how to
implement
QoS [1] either as in core, or as a service plugin, in, or out-tree.
It’s my feeling, and Mathieu’s that it looks more like a core feature, as
we’re talking of
port properties that we
On 22 April 2015 at 06:02, Miguel Angel Ajo Pelayo mangel...@redhat.com
wrote:
Hi everybody,
In the latest QoS meeting, one of the topics was a discussion about how
to implement
QoS [1] either as in core, or as a service plugin, in, or out-tree.
My apologies if I was unable to join,
