<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</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>Hi Thomas,</div>
<div><br>
</div>
<div>I will definitely hop into the next meeting, and I will definitely swing by your desk to chat!</div>
<div><br>
</div>
<div>-Steven</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>Thomas Maddox <<a href="mailto:thomas.maddox@RACKSPACE.COM">thomas.maddox@RACKSPACE.COM</a>><br>
<span style="font-weight:bold">Reply-To: </span>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, September 25, 2013 3:59 PM<br>
<span style="font-weight:bold">To: </span>OpenStack Development Mailing List <<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] [Ceilometer][IceHouse] Ceilometer + Kibana + ElasticSearch Integration<br>
</div>
<div><br>
</div>
<div>
<div 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>Hey Steven!</div>
<div><br>
</div>
<div>Sorry for missing my chance to chat on IRC today. We have our next weekly meeting on October 3rd (next Thursday) at 15:00 UTC (10:00 CST). That's probably the best chance at getting us all in a room, since we're pretty well distributed around the planet.
I definitely agree with you that we're working on very similar goals and ought to communicate about what we're trying to accomplish and how we can help each other. Feel free to ping us on #openstack-metering; also you sit a few desks away from me, feel free
to come by and chat. =]</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>-Thomas</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 9/24/13 2:10 PM, "Steven Gonzales" <<a href="mailto:steven.gonzales@RACKSPACE.COM">steven.gonzales@RACKSPACE.COM</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div 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>
<div>Celiometer Team,</div>
<div><br>
</div>
<div>I am a developer on the Project Meniscus team. I noticed the conversation on adding ElasticSearch and Kibana to Ceilometer and thought I would share some information regarding our project. I would love to discuss a way our projects could work together
on some of these common goals and possibly collaborate.</div>
<div><br>
</div>
<div>Project Meniscus is an open-source Python logging-as-a-service solution. The multi-tenant service will allow the dispatch of log messages to sinks such as ElasticSearch, Swift, and HDFS. Our initial implementation is defaulting to ElasticSearch. </div>
<div><br>
</div>
<div>The system was designed with the intention to scale and to be resilient to failure. We have written a tcp server for receiving syslog messages from standard syslog servers/daemons such as RSYSLOG and SYSLOG-NG. The server receives syslog messages over
long-lived tcp connections and parses individual log messages into json documents. The server uses the tornado tcp server, and the parser itself is written in C and uses Cython bindings.</div>
<div><br>
</div>
<div>We have implemented features such as normalization of log data by writing a python library that that binds to liglognorm, a C library for log processing.</div>
<div><br>
</div>
<div>In our very early alpha implementation we have been able to process about 30-40 GB of syslog messages per day on a single worker</div>
<div>node with a very small amount of load on the server. Our current worker nodes are 8GB RAM Virtual Machines running on Nova. </div>
<div><br>
</div>
<div><br>
</div>
<div>Currently we are working on:</div>
<div> 1. load balancing for syslog messages after parsing(since syslog servers transmit using long lived tcp connections)</div>
<div> 2. Implementing keystone authentication into Kibana 3 </div>
<div> 3. Building a proxy in front of ElasticSearch to limit queries by tenant.</div>
<div><br>
</div>
<div>Our project page is <a href="http://projectmeniscus.org/">http://projectmeniscus.org/</a></div>
<div>Our repo is located at: <a href="https://github.com/ProjectMeniscus">https://github.com/ProjectMeniscus</a> </div>
<div><br>
</div>
<div>The repo contains the main code base and all supporting projects, including our chef repository. </div>
<div><br>
</div>
<div>We would love to discuss a way our projects could work together on some of these common goals and possibly collaborate. Would it be possible to set up a time for us talk briefly?</div>
<div><br>
</div>
<div>Steven Gonzales</div>
<div>Software Developer</div>
<div>Rackspace Hosting</div>
<div><a href="mailto:steven.gonzales@rackspace.com">steven.gonzales@rackspace.com</a></div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>