> Seems awkward to me, if an IPSec connection has a status of ACTIVE, but an admin state of ADMIN DOWN. Right, you see, that's the problem. Constant name 'ACTIVE' makes you expect that IPSec connection should work, while it is a deployment status.
> OK, so the change is merely change "ACTIVE" into "DEPLOYED" instead? We can't just rename the ACTIVE to DEPLOYED, and may be the latter is not the best name, but yes, that's the intent. Thanks, Eugene. On Mon, Mar 17, 2014 at 7:31 PM, Kyle Mestery <mest...@noironetworks.com>wrote: > On Mon, Mar 17, 2014 at 8:36 AM, Eugene Nikanorov <enikano...@mirantis.com > > wrote: > >> Hi Kyle, >> >> >> >> >> >> >>>> It's a typical use case for network devices to have both admin and >>> operational >>> state. In the case of having admin_state=DOWN and >>> operational_state=ACTIVE, >>> this just means the port/link is active but has been configured down. >>> Isn't this >>> the same for LBaaS here? Even reading the bug, the user has clearly >>> configured >>> the VIP pool as admin_state=DOWN. When it becomes ACTIVE, it's due to >>> this >>> configuration that the pool remains admin_state=DOWN. >>> >>> Am I missing something here? >>> >> No, you're not. The user sees 'ACTIVE' status and think it contradicts >> 'DOWN' admin_state. >> It's naming (UX problem), in my opinion. >> >> OK, so the change is merely change "ACTIVE" into "DEPLOYED" instead? > > >> Thanks, >> Eugene. >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStackemail@example.com >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev