----- Original Message ----- > A thread [1] was also initiated on the ML by Syvlain but no answers/comment > for the moment. > > [1] http://openstack.markmail.org/thread/qy6ikldtq2o4imzl > > Édouard. >
IMHO admin_state_up = false should bring the network down and the traffic needs to be stopped. This is of course a risky operation, so there should be some clear warning describing the action and asking the user to confirm that. With regards to the implementation of this, I think that there is a difference between the network admin_state and the individual ports admin_state; setting the network admin_state to false should not change the port's state to false. Instead, I am in favor of the second solution [1] described by Sylvain in the ML. I also included this in the bug. /Nir [1] 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 > > On Mon, Feb 24, 2014 at 9:35 AM, 黎林果 <[email protected]> wrote: > > > Thanks you very much. > > > > "IMHO when admin_state_up is false that entity should be down, meaning > > network should be down. > > otherwise what it the usage of admin_state_up ? same is true for port > > admin_state_up" > > > > It likes switch's power button? > > > > 2014-02-24 16:03 GMT+08:00 Assaf Muller <[email protected]>: > > > > > > > > > ----- Original Message ----- > > >> Hi, > > >> > > >> I want to know the admin_state_up attribute about networks but I > > >> have not found any describes. > > >> > > >> Can you help me to understand it? Thank you very much. > > >> > > > > > > There's a discussion about this in this bug [1]. > > > From what I gather, nobody knows what admin_state_up is actually supposed > > > to do with respect to networks. > > > > > > [1] https://bugs.launchpad.net/neutron/+bug/1237807 > > > > > >> > > >> Regard, > > >> > > >> Lee Li > > >> > > >> _______________________________________________ > > >> OpenStack-dev mailing list > > >> [email protected] > > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > >> > > > > > > _______________________________________________ > > > OpenStack-dev mailing list > > > [email protected] > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
