<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I agree, this was supposed to be small.<br>
    <br>
    P.<br>
    <br>
    <div class="moz-cite-prefix">On 11/26/2014 11:03 AM, Stanislaw
      Bogatkin wrote:<br>
    </div>
    <blockquote
cite="mid:CACxS=aDrOSLt9kdqgPyqZNLyH9SWmWMX=6_FPNZ_bzbAOgCziw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Hi all,<br>
          As I understand, we just need to monitoring one node - Fuel
          master. For slave nodes we already have a solution - zabbix.<br>
        </div>
        So, in that case why we need some complicated stuff like
        monasca? Let's use something small, like monit or sensu.<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Nov 24, 2014 at 10:36 PM, Fox,
          Kevin M <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div>
              <div>One of the selling points of tripleo is to reuse as
                much as possible from the cloud, to make it easier to
                deploy. While monasca may be more complicated, if it
                ends up being a component everyone learns, then its not
                as bad as needing to learn two different monitoring
                technologies. You could say the same thing cobbler vs
                ironic. the whole Ironic stack is much more complicated.
                But for an openstack admin, its easier since a lot of
                existing knowlege applies. Just something to consider.<br>
                <br>
                Thanks,<br>
                Kevin <strong>
                  <div><font color="#000000" face="Tahoma"> </font></div>
                </strong>
                <hr>
                <font face="Tahoma"><b>From:</b> Tomasz Napierala<br>
                  <b>Sent:</b> Monday, November 24, 2014 6:42:39 AM<span
                    class=""><br>
                    <b>To:</b> OpenStack Development Mailing List (not
                    for usage questions)<br>
                    <b>Subject:</b> Re: [openstack-dev] [Fuel] fuel
                    master monitoring<br>
                  </span></font><br>
              </div>
              <div>
                <div class="h5">
                  <font><span style="font-size:10pt">
                      <div><br>
                        > On 24 Nov 2014, at 11:09, Sergii Golovatiuk
                        <<a moz-do-not-send="true"
                          href="mailto:sgolovatiuk@mirantis.com"
                          target="_blank">sgolovatiuk@mirantis.com</a>>
                        wrote:<br>
                        > <br>
                        > Hi,<br>
                        > <br>
                        > monasca looks overcomplicated for the
                        purposes we need. Also it requires Kafka which
                        is Java based transport protocol.<br>
                        > I am proposing Sensu. It's architecture is
                        tiny and elegant. Also it uses rabbitmq as
                        transport so we won't need to introduce new
                        protocol.<br>
                        <br>
                        Do we really need such complicated stuff? Sensu
                        is huge project, and it's footprint is quite
                        large. Monit can alert using scripts, can we use
                        it instead of API?<br>
                        <br>
                        Regards,<br>
                        -- <br>
                        Tomasz 'Zen' Napierala<br>
                        Sr. OpenStack Engineer<br>
                        <a moz-do-not-send="true"
                          href="mailto:tnapierala@mirantis.com"
                          target="_blank">tnapierala@mirantis.com</a><br>
                        <br>
                        <br>
                        <br>
                        <br>
                        <br>
                        <br>
                        <br>
                        _______________________________________________<br>
                        OpenStack-dev mailing list<br>
                        <a moz-do-not-send="true"
                          href="mailto:OpenStack-dev@lists.openstack.org"
                          target="_blank">OpenStack-dev@lists.openstack.org</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>
                      </div>
                    </span></font>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            OpenStack-dev mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>