Re: [openstack-dev] [Neutron] "DOWN" and "INACTIVE" status in FWaaS and LBaaS

2014-02-26 Thread Xuhan Peng
Oleg, Thanks a lot for your quick response! I will open a bug to address that soon. For the LBaaS part, probably I will just make the fix dependent on the code review you mentioned. Xu Han On Wed, Feb 26, 2014 at 6:43 PM, Oleg Bondarev wrote: > Hi, > > For LBaaS the background is simple: it use

Re: [openstack-dev] [Neutron] "DOWN" and "INACTIVE" status in FWaaS and LBaaS

2014-02-26 Thread Oleg Bondarev
Hi, For LBaaS the background is simple: it uses statuses from neutron/plugins/common/constants.py and INACTIVE was there initially while DOWN appeared later (with VPNaaS first commit). So LBaaS doesn't use DOWN at all. As for INACTIVE, it is currently used only for members that stop responding to

[openstack-dev] [Neutron] "DOWN" and "INACTIVE" status in FWaaS and LBaaS

2014-02-26 Thread Xuhan Peng
Hello, This email is triggered by the comments I received in my patch [1] when trying to fix bug [2]. The problem I was trying to fix is that current firewall remains in status "ACTIVE" after admin state is changed to "DOWN". My plan is to change the status of firewall from ACTIVE to DOWN when ad