<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Interesting thread!<br>
<br>
I was very intrigued about reading this thread, and reading through
Julien's blog posts.<br>
We are consuming the various Telemetry projects and I would like to
get more involved in the Telemetry-effort.<br>
<br>
The mentioned Train roadmap ethernetpad [1] is a great start on
defining the focus for the Telemetry projects.<br>
<br>
I think this is a great start to getting to the roots of how, based
on the words of Julien's, how Ceilometer should<br>
have been build and not how it was built to work around all the
limitations of the old OpenStack era.<br>
<br>
Most new deployments are probably already using Gnocchi, I'm
including myself, were even third parties has<br>
implemented billing connections to the API. In my opinion the bigger
questions here is how the various Telemetry<br>
parts should evolve based on the theory that storage is already
provided.<br>
<br>
There should be a lot of thought put into the difference between a
metrics- and billingbased storage solution<br>
in the back.<br>
<br>
I'll check out the Doodle and see if I can make the next meeting.<br>
<br>
Best regards<br>
Tobias<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/telemetry-train-roadmap">https://etherpad.openstack.org/p/telemetry-train-roadmap</a><br>
<br>
<div class="moz-cite-prefix">On 05/08/2019 11:27 PM, Joseph Davis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:14ff728c-f19e-e869-90b1-4ff37f7170af@suse.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="moz-cite-prefix">On 5/8/19 7:12 AM, <a
class="moz-txt-link-abbreviated"
href="mailto:openstack-discuss-request@lists.openstack.org"
moz-do-not-send="true">
openstack-discuss-request@lists.openstack.org</a> wrote: </div>
<blockquote type="cite"
cite="mid:mailman.184065.1557324725.4677.openstack-discuss@lists.openstack.org">
<pre class="moz-quote-pre" wrap="">Hello Trinh,
Where does the meeting happen? Will it be via IRC Telemetry channel? Or, in
the Etherpad (<a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/telemetry-meeting-agenda" moz-do-not-send="true">https://etherpad.openstack.org/p/telemetry-meeting-agenda</a>)? I
would like to discuss and understand a bit better the context behind
the Telemetry
events deprecation.</pre>
</blockquote>
<p>Unfortunately, I have a conflict at that time and will not be
able to attend.<br>
</p>
<p>I do have a little bit of context on the Events deprecation to
share.</p>
<p>First, you will note the commit message from the commit [0]
when Events were deprecated:</p>
<p>"</p>
<p class="commit-title">Deprecate event subsystem </p>
<pre>This subsystem has never been finished and is not maintained.
Deprecate it for future removal.</pre>
<p>"</p>
<p>I got the impression from jd at the time that there were a
number of features in Telemetry,</p>
<p>including Panko, that were not really "finished" and that the
engineers who had worked on them</p>
<p>had moved on to other things, so the features had become
unsupported. In late 2018 there was</p>
<p>an effort to clean up things that were not well maintained or
didn't fit the direction of Telemetry.</p>
<p>See also: <a class="moz-txt-link-freetext"
href="https://julien.danjou.info/lessons-from-openstack-telemetry-deflation/"
moz-do-not-send="true">
https://julien.danjou.info/lessons-from-openstack-telemetry-deflation/</a></p>
<p><br>
</p>
<p>Events is one feature that often gets requested, but the use
cases and demand for it are not expressed</p>
<p>strongly or well understood by most people. If the Telemetry
project has demand to de-deprecate</p>
<p>Event handling (including Panko), I'd suggest a review of the
requirements for event handling and</p>
<p>possibly choosing a champion for maintaining the Panko service.<br>
</p>
<p><br>
</p>
<p>Also note: over in Monasca we have a spec [1] for handling
Events ingestion which I hope we will be
<br>
</p>
<p>completing in Train. Contributions and comments welcome. :)</p>
<p><br>
</p>
<p>joseph<br>
</p>
<p>[0] <a class="moz-txt-link-freetext"
href="https://github.com/openstack/ceilometer/commit/8a0245a5b3e1357d35ad6653be37ca01176577e4"
moz-do-not-send="true">
https://github.com/openstack/ceilometer/commit/8a0245a5b3e1357d35ad6653be37ca01176577e4</a><br>
</p>
<p>[1] <a class="moz-txt-link-freetext"
href="https://github.com/openstack/monasca-specs/blob/master/specs/stein/approved/monasca-events-listener.rst"
moz-do-not-send="true">
https://github.com/openstack/monasca-specs/blob/master/specs/stein/approved/monasca-events-listener.rst</a><br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:mailman.184065.1557324725.4677.openstack-discuss@lists.openstack.org">
<pre class="moz-quote-pre" wrap="">On Wed, May 8, 2019 at 12:19 AM Trinh Nguyen <a class="moz-txt-link-rfc2396E" href="mailto:dangtrinhnt@gmail.com" moz-do-not-send="true"><dangtrinhnt@gmail.com></a> wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">Hi team,
As planned, we will have a team meeting at 02:00 UTC, May 9th on
#openstack-telemetry to discuss what we gonna do for the next milestone
(Train-1) and continue what we left off from the last meeting.
I put here [1] the agenda thinking that it should be fine for an hour
meeting. If you have anything to talk about, please put it there too.
[1] <a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/telemetry-meeting-agenda" moz-do-not-send="true">https://etherpad.openstack.org/p/telemetry-meeting-agenda</a>
Bests,
--
<b class="moz-txt-star"><span class="moz-txt-tag">*</span>Trinh Nguyen<span class="moz-txt-tag">*</span></b>
*www.edlab.xyz <a class="moz-txt-link-rfc2396E" href="https://www.edlab.xyz" moz-do-not-send="true"><https://www.edlab.xyz></a>*
</pre>
</blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>