Hi, I'm working on this bug :
https://bugs.launchpad.net/neutron/+bug/1237807 and I'm wondering how we should address this issue, below my suggestions/thoughts Currently when the admin_state_up of a network is set to false, the only thing which is done is that the dhcp instance of this network is disabled/destroyed, so the dhcp port is removed from br-int. So should we : 1. set all ports admin_state_up to false, and let the agents (ovs) set the port as dead, which is a different behavior than the dhcp which removes the port from br-int. 2. do not change the admin_state_up value of ports and introduce a new field in the get_device_details rpc call in order to indicate that the admin_state_up of network is down and then set the port as dead ? So that if the admin_state_up of the network is restored all ports recover their original status. In any case it could be a good thing to have a consistent behavior between dhcp ports and other network ports ? Thanks in advance, -Sylvain _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
