<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>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.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Doug</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Mike Spreitzer <<a href="mailto:mspreitz@us.ibm.com">mspreitz@us.ibm.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, July 23, 2014 at 2:03 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [heat] health maintenance in autoscaling groups<br>
</div>
<div><br>
</div>
<div>
<div><tt><font size="2">Doug Wiegley <<a href="mailto:dougw@a10networks.com">dougw@a10networks.com</a>> wrote on 07/23/2014 03:43:02 PM:<br>
<br>
> From: Doug Wiegley <<a href="mailto:dougw@a10networks.com">dougw@a10networks.com</a>></font></tt>
<br>
<tt><font size="2">> ...</font></tt> <br>
<tt><font size="2">> The state of the world today: ‘status’ in the neutron database is
<br>
> configuration/provisioning status, not operational status. Neutron-<br>
> wide thing. We were discussing adding operational status fields (or<br>
> a neutron REST call to get the info from the backend) last month, <br>
> but it’s something that isn’t planned for a serious conversation <br>
> until Kilo, at present.</font></tt> <br>
<br>
<tt><font size="2">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?</font></tt><br>
<br>
<tt><font size="2">Thanks,</font></tt> <br>
<tt><font size="2">Mike</font></tt></div>
</div>
</span>
</body>
</html>