<div dir="ltr"><div>Hello,<br></div><div><br>This email is triggered by the comments I received in my patch [1] when trying to fix bug [2].<br clear="none"></div><div><br clear="none"></div><div>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 admin state is down, as
other network resource is doing currently.</div><div><br clear="none"></div><div>But
I noticed besides "DOWN" state, "INACTIVE" state is also used in FWaaS
and LBaaS. So I hope someone can help me understand any background of
this. If this is not particularly
by design and inconsistent with other network resource, I can open a
bug to fix this in FWaaS and LBaaS. <br><br></div><div>Thanks, <br></div><div>Xu Han<br clear="none"></div><div><br clear="none"></div><div>[1]: <a href="https://review.openstack.org/#/c/73944/">https://review.openstack.org/#/c/73944/</a><br clear="none">
</div><div>[2]: <a href="https://launchpad.net/bugs/1279213">https://launchpad.net/bugs/1279213</a><br><br></div><div><br></div></div>