<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On Dec 17, 2019, at 6:14 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org" class="">thierry@openstack.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Zane Bitter wrote:<br class="">
<blockquote type="cite" class="">On 15/12/19 10:20 pm, Rong Zhu wrote:<br class="">
<blockquote type="cite" class="">1.Add Ceilometer API back<br class="">
Since Gnocchi is out of OpenStack and is unmaintained, we need to add Ceilometer API back again.<br class="">
</blockquote>
This is concerning because even the people who wrote it don't consider it adequate to the job. That inadequacy has been the source of significant reputational damage to OpenStack in the past, and many folks (me included) are anxious to avoid a repeat.<br class="">
</blockquote>
<br class="">
Yes this concerns me too, and even if we workaround the issue by adding Ceilo API back, I'd like to have a long-term plan to solve this issue. It seems there are several options on the table (including integrating Monasca and Ceilometer into a single stack,
and other big-bang replacements) but it's never a one-for-one comparison as the solutions seem to address slightly disjoint problem spaces.<br class="">
<br class="">
I'd like to hear from more Ceilometer users. What are they using Ceilometer for, and what long-term plans would be acceptable. There is a trade-off between adopting short-term workarounds that reintroduce performance issues vs. undergoing a complex migration
to the "right" way of fixing this. Like for example there is little point in pushing Monasca/Ceilometer stack integration if most users say, like Catalyst Cloud seems to say, that they would rather have a slow performing Ceilometer API back.<br class="">
<br class="">
<blockquote type="cite" class="">Telemetry is part of the TC "Approved Release" that is eligible for the trademark program; I think at a minimum the TC will want to remove the resurrected Ceilometer API from the "designated sections" that users are required
to run to participate in any trademark program that includes the functionality in question. But I think that we should explore other ways of reducing the chance of anyone confusing this for a viable way of building a cloud, including possibly changing the
name (Antediluvian API?) and having this part of the stack live outside of the official OpenStack project.<br class="">
</blockquote>
<br class="">
Legacy API?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div class="">FWIW, telemetry projects are indeed eligible *for consideration*…but Ceilometer has never actually been required by any interop guideline:</div>
<div class=""><br class="">
</div>
<a href="https://github.com/openstack/interop/blob/master/2019.11.json#L3218-L3222" class="">https://github.com/openstack/interop/blob/master/2019.11.json#L3218-L3222</a>
<div class=""><br class="">
</div>
<div class="">It’s come up a few times over the years but was never deemed to have met enough of the criteria [1] to warrant inclusion in a guideline.</div>
<div class="">
<div class=""><br class="">
</div>
<div class="">[1] <a href="https://github.com/openstack/interop/blob/master/doc/source/process/CoreCriteria.rst" class="">https://github.com/openstack/interop/blob/master/doc/source/process/CoreCriteria.rst</a></div>
<div class=""><br class="">
</div>
<div class="">At Your Service,</div>
<div class=""><br class="">
<div class="">
<div>Mark T. Voelker</div>
<div><br class="">
</div>
</div>
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
-- <br class="">
Thierry Carrez (ttx)<br class="">
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>