Hi all, It seems today that the ml2 rpc API only supports reporting that a port is up\down, There may be situations when the l2 agent can fail, For example SR-IOV agent can report failure when configuring a port on the wrong physnet. In these cases we should how would one report port failed status with the rpc messages? Should we add a new rpc call? Also it's not clear to me why the documentation in the plugins/ml2/rpc.py file States that the method 'update_device_down' function is: "Device no longer exists on agent", when it stets the port status to down in admin_state_down.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
