<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 05/09/2012 11:11 PM, Doug Hellmann wrote:
    <blockquote
cite="mid:CADb+p3RtZasYUjEGe6HJDpx2BxO8yN9DWBq+9Y_=Ja=+NiX-7A@mail.gmail.com"
      type="cite"><br>
      <br>
      <div class="gmail_quote">On Wed, May 9, 2012 at 3:07 PM, Tomasz
        Paszkowski <span dir="ltr"><<a moz-do-not-send="true"
            href="mailto:ss7pro@gmail.com" target="_blank">ss7pro@gmail.com</a>></span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div>On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann<br>
            <<a moz-do-not-send="true"
              href="mailto:doug.hellmann@dreamhost.com" target="_blank">doug.hellmann@dreamhost.com</a>>
            wrote:<br>
            ><br>
            > Nice!<br>
            ><br>
            > For production code I think we are going to want to
            separate collection from<br>
            > storage, aren't we? We don't want each compute node to
            require access to the<br>
            > database server (that's an issue with nova that they
            are trying to fix<br>
            > during the folsom release, IIRC).<br>
            <br>
          </div>
          Yes. Part of the code responsible for amqp support is not
          functional yet :(<br>
        </blockquote>
        <div><br>
        </div>
        <div>OK, that's what I thought.</div>
        <div><br>
        </div>
        <div>We all seem to be reinventing different parts of the
          services that we will eventually need, which is good for
          education but may be wasting a bit of energy. Is it premature
          to start talking a little more about architecture so we can
          start splitting up the implementation work and focusing that
          energy differently? There is a lot of work we can do
          independently of the remaining decisions outlined in <a
            moz-do-not-send="true"
            href="http://wiki.openstack.org/Meetings/MeteringAgenda">http://wiki.openstack.org/Meetings/MeteringAgenda</a>.</div>
      </div>
    </blockquote>
    Hi,<br>
    <br>
    It looks like the architecture of metering is indeed always
    implemented in similar ways. I had discussions with a company
    yesterday about their own metering implementation (which will be
    used in production soon) and it also has an architecture matching
    what has been proposed so far in ceilometer. I added a few points to
    the architecture chapter in the wiki:<br>
    <br>
    <a class="moz-txt-link-freetext" href="http://wiki.openstack.org/EfficientMetering#Architecture">http://wiki.openstack.org/EfficientMetering#Architecture</a><br>
    <br>
    including a note summarizing the conclusions of the discussion
    regarding need for an independent ceilometer agent in addition to
    the existing meters provided by the OpenStack components. <br>
    <br>
    What do you think ?<br>
    <blockquote
cite="mid:CADb+p3RtZasYUjEGe6HJDpx2BxO8yN9DWBq+9Y_=Ja=+NiX-7A@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div> </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div>
            <div><br>
              <br>
              <br>
              --<br>
              Tomasz Paszkowski<br>
              SS7, Asterisk, SAN, Datacenter, Cloud Computing<br>
              <a moz-do-not-send="true" href="tel:%2B48500166299"
                value="+48500166299" target="_blank">+48500166299</a><br>
              <br>
              _______________________________________________<br>
              Mailing list: <a moz-do-not-send="true"
                href="https://launchpad.net/%7Eopenstack"
                target="_blank">https://launchpad.net/~openstack</a><br>
              Post to     : <a moz-do-not-send="true"
                href="mailto:openstack@lists.launchpad.net"
                target="_blank">openstack@lists.launchpad.net</a><br>
              Unsubscribe : <a moz-do-not-send="true"
                href="https://launchpad.net/%7Eopenstack"
                target="_blank">https://launchpad.net/~openstack</a><br>
              More help   : <a moz-do-not-send="true"
                href="https://help.launchpad.net/ListHelp"
                target="_blank">https://help.launchpad.net/ListHelp</a><br>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to     : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help   : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="3000">-- 
Loïc Dachary         Chief Research Officer
// eNovance labs   <a class="moz-txt-link-freetext" href="http://labs.enovance.com">http://labs.enovance.com</a>
// ✉ <a class="moz-txt-link-abbreviated" href="mailto:loic@enovance.com">loic@enovance.com</a>  ☎ +33 1 49 70 99 82
</pre>
  </body>
</html>