Open Stack

Great question, and to my knowledge, not at present.  There is an ongoing discussion about a common usage framework for ceilometer, for all the various *aaS things, but status I not included (yet!).  I think that spec is in gerrit.

Thanks,
Doug


From: Mike Spreitzer <mspreitz at us.ibm.com<mailto:mspreitz at us.ibm.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, July 23, 2014 at 2:03 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [heat] health maintenance in autoscaling groups

Doug Wiegley <dougw at a10networks.com<mailto:dougw at a10networks.com>> wrote on 07/23/2014 03:43:02 PM:

> From: Doug Wiegley <dougw at a10networks.com<mailto:dougw at a10networks.com>>
> ...
> The state of the world today: ‘status’ in the neutron database is
> configuration/provisioning status, not operational status.  Neutron-
> wide thing.  We were discussing adding operational status fields (or
> a neutron REST call to get the info from the backend) last month,
> but it’s something that isn’t planned for a serious conversation
> until Kilo, at present.

Thanks for the prompt response.  Let me just grasp at one last straw: is there any chance that Neutron will soon define and implement Ceilometer metrics that reveal PoolMember health?

Thanks,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140723/3b3e29c7/attachment.html>