<br><br><div class="gmail_quote">On Fri, Nov 2, 2012 at 3:07 AM, Patrick Petit <span dir="ltr"><<a href="mailto:patrick.michel.petit@gmail.com" target="_blank">patrick.michel.petit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Folks,<br>
I'd like to add to this that physical server metering shouldn't be treated differently in Ceilometer now that bare metal provisioning framework enters into Grizzly. Physical servers will just become billable resources much like VMs. I am not speaking of physical server monitoring here. Just extending Ceilometer agent to also report usage data out of the physical box.<br>
</blockquote><div><br></div><div>Thanks for posting this, Patrick. I understood "physical devices" as "host server" not as "bare-metal server".</div><div><br></div><div>I suspect we could use the same agent framework, but almost all of the pollsters would need to be different because they would be running inside the guest OS rather than on a host VM, so the APIs they will use to collect the same data will be different.</div>
<div><br></div><div>Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers<br>
Patrick<br>
<br>
Envoyé de mon iPad<br>
<br>
Le 1 nov. 2012 à 19:13, Julien Danjou <<a href="mailto:julien@danjou.info">julien@danjou.info</a>> a écrit :<br>
<div class="HOEnZb"><div class="h5"><br>
> On Thu, Nov 01 2012, Zehnder Toni (zehndton) wrote:<br>
><br>
>> My goal is to offer monitored data to the admin and customers. The admin is<br>
>> interested in the utilization of the physical components and the virtual<br>
>> machines and the customer is interested to know what his VMs do or can do.<br>
>> It would be nice to get the data from a single point. I thought I can<br>
>> enhance the Ceilometer compute agent to get this data out. Does this make<br>
>> sense or is it better to use another monitoring tool for the physical<br>
>> components?<br>
><br>
> I think the pollster implementation can be done. I wouldn't implement<br>
> this in the compute agent, but probably in some hardware agent, because<br>
> it's likely it would be used in different kinds of environment and not<br>
> only on compute node, i.e. you may also want to meter hardware usage for<br>
> you cinder or glance node anyway.<br>
><br>
> About the 10 minutes polling interval Doug mentionned, this can be a<br>
> problem indeed, but it's still solvable later and would be easy to solve<br>
> if this in a different agent, since you could change the periodic<br>
> interval for pollster runs to something like 1 or 5 minutes.<br>
><br>
> --<br>
> Julien Danjou<br>
> // Free Software hacker & freelance<br>
> // <a href="http://julien.danjou.info" target="_blank">http://julien.danjou.info</a><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br>