Hi mike, Awesome, thanks for chasing that down. Now I need to close the loop and figure out where that linkage is, so I don't go crazy.
Thanks, Doug On Jul 24, 2014, at 10:06 PM, "Mike Spreitzer" <mspre...@us.ibm.com<mailto:mspre...@us.ibm.com>> wrote: Doug Wiegley <do...@a10networks.com<mailto:do...@a10networks.com>> wrote on 07/23/2014 11:24:32 PM: > Hi Mike, > > > and listed the possible values of the status field, including > "INACTIVE". Other sources are telling me that status=INACTIVE when > the health monitor thinks the member is unhealthy, status!=INACTIVE > when the health monitor thinks the member is healthy. What's going on here? > > Indeed, the code will return a server status of INACTIVE if the > lbaas agent marks a member ‘DOWN’. But, nowhere can I find that it > actually ever does so. > > My statements about the status field for lbaas/neutron came from the > author of the ref lbaas driver; I’ll check with him tomorrow and see > if I misunderstood. I did an experiment, and found that the PoolMember status did indeed switch between ACTIVE and INACTIVE depending on the health of the member. Thanks, Mike _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev