<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/13/2015 09:06 AM, Simon Pasquier
wrote:<br>
</div>
<blockquote
cite="mid:CAOq3GZXqvCGaR2JF3wKtuHCEcC5Q5+YHLHWLuohmjBbow8NZTw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>
<div>
<div>
<div>Hello,<br>
<br>
Like many others commented before, I don't quite
understand how unique are the Cloudpulse use cases.<br>
<br>
For operators, I got the feeling that existing solutions
fit well:<br>
- Traditional monitoring tools (Nagios, Zabbix, ....)
are necessary anyway for infrastructure monitoring (CPU,
RAM, disks, operating system, RabbitMQ, databases and
more) and diagnostic purposes. Adding OpenStack service
checks is fairly easy if you already have the toolchain.<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Is it really so easy? Rabbitmq has an "aliveness" test that is easy
to hook into. I don't know exactly what it does, other than what the
doc says, but I should not have to. If I want my standard monitoring
system to call into a cloud and ask "is nova healthy?", "is glance
healthy?", etc. are their such calls? <br>
<br>
There are various sets of calls associated with nagios, zabbix, etc.
but those seem like "after-market" parts for a car. Seems to me the
services themselves would know best how to check if they are
healthy, particularly as that could change version to version. Has
their been discussion of adding a health-check (admin) api in each
service? Lacking that, is there documentation from any OpenStack
projects about "how to check the health of nova"? When I saw this
thread start, that is what I thought it was going to be about.<br>
<br>
-David<br>
<br>
<blockquote
cite="mid:CAOq3GZXqvCGaR2JF3wKtuHCEcC5Q5+YHLHWLuohmjBbow8NZTw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>- OpenStack projects like Rally or Tempest can
generate synthetic loads and run end-to-end tests.
Integrating them with a monitoring system isn't terribly
difficult either.<br>
</div>
</div>
<br>
As far as Monitoring-as-a-service is concerned, do you have
plans to integrate/leverage Ceilometer?<br>
<br>
</div>
BR,<br>
</div>
Simon</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 12, 2015 at 7:20 PM, Vinod
Pandarinathan (vpandari) <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:vpandari@cisco.com"
target="_blank">vpandari@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote">
<div>
<div>
<div>
<span>Hello,</span></div>
<div>
<br>
</div>
<div>
I'm pleased to announce the development of a new
project called CloudPulse. CloudPulse provides
Openstack</div>
<div>
<span>health-checking services to both operators,
tenants, and applications. This project will begin
as </span></div>
<div>
<span>a StackForge project based upon an empty
cookiecutter[1] repo. The repos to work in are:</span></div>
<div>
<span>Server:
</span><span><a moz-do-not-send="true"
href="https://github.com/stackforge/cloudpulse"
target="_blank">https://github.com/stackforge/cloudpulse</a></span></div>
<div>
<span>Client:
</span><span><a moz-do-not-send="true"
href="https://github.com/stackforge/python-cloudpulseclient"
target="_blank">https://github.com/stackforge/python-cloudpulseclient</a></span></div>
<div>
<br>
</div>
<div>
<span>Please join us via iRC on #openstack-cloudpulse
on freenode.</span></div>
<div>
<br>
</div>
<div>
<span>I am holding a doodle poll to select times for
our first meeting the week after summit. This
doodle poll will close May 24th and meeting times
will be announced on the mailing list at that time.
At our first IRC meeting, </span></div>
<div>
<span>we will draft additional core team members, so
if your interested in joining a fresh new
development effort, please attend our first
meeting. </span></div>
<div>
Please take a moment if your interested in CloudPulse
to fill out the doodle poll here: </div>
<div>
<br>
</div>
<div>
<span><a moz-do-not-send="true"
href="https://doodle.com/kcpvzy8kfrxe6rvb"
target="_blank">https://doodle.com/kcpvzy8kfrxe6rvb</a></span></div>
<div>
<br>
</div>
<div>
The initial core team is composed of</div>
<div>
<span>Ajay Kalambur, </span></div>
<div>
<span>Behzad Dastur,
</span><span>Ian Wells,
</span><span>Pradeep chandrasekhar,
</span><span>Steven Dake</span><span> and</span><span>
Vinod Pandarinathan</span><span>.</span><span>
<br>
</span></div>
<div>
<span>I expect more members to join during our initial
meeting.</span></div>
<div>
<br>
</div>
<div>
A little bit about CloudPulse:</div>
<div>
<span> Cloud operators need notification of OpenStack
failures before a customer reports the failure.
Cloud operators can then take timely corrective
actions with minimal disruption to applications.
Many cloud applications, including </span></div>
<div>
<span>those I am interested in (NFV) have very
stringent service level agreements. Loss of service
can trigger contractual</span></div>
<div>
<span>costs associated with the service. Application
high availability requires an operational OpenStack
Cloud, and the reality</span></div>
<div>
<span>is that occascionally OpenStack clouds fail in
some mysterious ways. This project intends to
identify when those failures </span></div>
<div>
<span>occur so corrective actions may be taken by
operators, tenants, and the applications themselves.</span></div>
<div>
<span><br>
</span></div>
<div>
<span></span>OpenStack is considered healthy when
OpenStack API services respond appropriately. Further
OpenStack is</div>
<div>
<span>healthy when network traffic can be sent between
the tenant networks and
</span><span>can access the Internet. Finally
OpenStack</span></div>
<div>
<span>is healthy when all infrastructure cluster
elements are in an operational state.</span></div>
<div>
<br>
</div>
<div>
<span>For information about blueprints check out:</span></div>
<div>
<span> </span><span><a moz-do-not-send="true"
href="https://blueprints.launchpad.net/cloudpulse"
target="_blank">https://blueprints.launchpad.net/cloudpulse</a></span></div>
<div>
<span><a moz-do-not-send="true"
href="https://blueprints.launchpad.net/python-cloudpulseclient"
target="_blank">https://blueprints.launchpad.net/python-cloudpulseclient</a></span></div>
<div>
<br>
</div>
<div>
For more details, check out our Wiki:</div>
<div>
<span><a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Cloudpulse"
target="_blank">https://wiki.openstack.org/wiki/Cloudpulse</a></span></div>
<div>
<br>
</div>
<div>
Plase join the CloudPulse team in designing and
implementing a world-class Carrier Grade system for
checking</div>
<div>
<span>the health of OpenStack clouds. We look forward
to seeing you on IRC on #openstack-cloudpulse.</span></div>
<div>
<br>
</div>
<div>
Regards,</div>
<div>
<span>Vinod Pandarinathan</span></div>
<div>
<span>[1]
</span><span><a moz-do-not-send="true"
href="https://github.com/openstack-dev/cookiecutter"
target="_blank">https://github.com/openstack-dev/cookiecutter</a></span></div>
</div>
<div><br>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>