On 18.03.2014 16:59, Eric Blake wrote:
On 03/18/2014 04:01 AM, Michal Privoznik wrote:
We allow translation from no_bandwidth to has_bandwidth for a vnic.
However, going in the opposite direction is not implemented. It's not
limitation of the API rather than internal implementation.
Awkward.
We allow translation from no_bandwidth to has_bandwidth for a vnic.
However, going in the opposite direction is not implemented. It's not
limitation of the API rather than internal implementation. The problem
is, we correctly detect that user hasn't specified any outbound (say
he wants to clear
On 03/18/2014 04:01 AM, Michal Privoznik wrote:
We allow translation from no_bandwidth to has_bandwidth for a vnic.
However, going in the opposite direction is not implemented. It's not
limitation of the API rather than internal implementation.
Awkward. How about:
It's not a limitation of