On 04/28/2015 06:25 AM, Rossella Sblendido wrote:
On 04/28/2015 03:24 AM, Armando M. wrote:
UnsupportedVersion error if the version is not bumped in their agent
too.
Could the server fall back and keep on using the old version of the
API? I
think that would
On 28 April 2015 at 05:52, Russell Bryant rbry...@redhat.com wrote:
On 04/28/2015 06:25 AM, Rossella Sblendido wrote:
On 04/28/2015 03:24 AM, Armando M. wrote:
UnsupportedVersion error if the version is not bumped in their
agent too.
Could the server fall back
On 04/28/2015 03:24 AM, Armando M. wrote:
UnsupportedVersion error if the version is not bumped in their agent
too.
Could the server fall back and keep on using the old version of the
API? I
think that would make for a much nicer experience, especially in face
On 27 April 2015 at 09:09, Rossella Sblendido rsblend...@suse.com wrote:
Hello all,
I am working at the blueprint Restructure the L2 agent [1] .
One of the work item of this blueprint is to modify the port_update
message to include the attributes of the ports that were modified. This
is
On 27 April 2015 at 18:16, YAMAMOTO Takashi yamam...@valinux.co.jp wrote:
On 27 April 2015 at 09:09, Rossella Sblendido rsblend...@suse.com
wrote:
Hello all,
I am working at the blueprint Restructure the L2 agent [1] .
One of the work item of this blueprint is to modify the
On 27 April 2015 at 09:09, Rossella Sblendido rsblend...@suse.com wrote:
Hello all,
I am working at the blueprint Restructure the L2 agent [1] .
One of the work item of this blueprint is to modify the port_update
message to include the attributes of the ports that were modified. This
is
On 04/27/2015 12:09 PM, Rossella Sblendido wrote:
Hello all,
I am working at the blueprint Restructure the L2 agent [1] .
One of the work item of this blueprint is to modify the port_update
message to include the attributes of the ports that were modified. This
is implemented in this patch
