[openstack-dev] [heat] health maintenance in autoscaling groups

Doug Wiegley dougw at a10networks.com
Fri Jul 25 04:38:52 UTC 2014


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" <mspreitz at us.ibm.com<mailto:mspreitz at us.ibm.com>> wrote:

Doug Wiegley <dougw at a10networks.com<mailto:dougw at 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 at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140725/349b9ba3/attachment-0001.html>


More information about the OpenStack-dev mailing list