On Mon, Mar 17, 2014 at 8:36 AM, Eugene Nikanorov <[email protected]>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 > [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
