<div dir="ltr">Hi everyone,<div><br></div><div>I'm sorry for being late to the thread, but what about baremetal driver? Should it support the get_diagnostics() as well?</div><div><br></div><div>--</div><div>Best regards,</div>
<div>Oleg Gelbukh</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 19, 2013 at 8:21 PM, Vladik Romanovsky <span dir="ltr"><<a href="mailto:vladik.romanovsky@enovance.com" target="_blank">vladik.romanovsky@enovance.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ah, I think I've responded too fast, sorry.<br>
<br>
meter-list provides a list of various measurements that are being done per resource.<br>
sample-list provides a list of samples per every meter: ceilometer sample-list --meter cpu_util -q resource_id=vm_uuid<br>
These samples can be aggregated over a period of time per every meter and resource:<br>
ceilometer statistics -m cpu_util -q 'timestamp>START;timestamp<=END;resource_id=vm_uuid' --period 3600<br>
<div class="im HOEnZb"><br>
Vladik<br>
<br>
<br>
<br>
----- Original Message -----<br>
> From: "Daniel P. Berrange" <<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>><br>
</div><div class="im HOEnZb">> To: "Vladik Romanovsky" <<a href="mailto:vladik.romanovsky@enovance.com">vladik.romanovsky@enovance.com</a>><br>
> Cc: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, "John<br>
> Garbutt" <<a href="mailto:john@johngarbutt.com">john@johngarbutt.com</a>><br>
> Sent: Thursday, 19 December, 2013 10:37:27 AM<br>
> Subject: Re: [openstack-dev] [nova] VM diagnostics - V3 proposal<br>
><br>
</div><div class="HOEnZb"><div class="h5">> On Thu, Dec 19, 2013 at 03:47:30PM +0100, Vladik Romanovsky wrote:<br>
> > I think it was:<br>
> ><br>
> > ceilometer sample-list -m cpu_util -q 'resource_id=vm_uuid'<br>
><br>
> Hmm, a standard devstack deployment of ceilometer doesn't seem to<br>
> record any performance stats at all - just shows me the static<br>
> configuration parameters :-(<br>
><br>
> ceilometer meter-list -q 'resource_id=296b22c6-2a4d-4a8d-a7cd-2d73339f9c70'<br>
> +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+<br>
> | Name | Type | Unit | Resource ID<br>
> | | User ID | Project ID<br>
> | |<br>
> +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+<br>
> | disk.ephemeral.size | gauge | GB |<br>
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |<br>
> | ec26984024c1438e8e2f93dc6a8c5ad0 |<br>
> | disk.root.size | gauge | GB |<br>
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |<br>
> | ec26984024c1438e8e2f93dc6a8c5ad0 |<br>
> | instance | gauge | instance |<br>
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |<br>
> | ec26984024c1438e8e2f93dc6a8c5ad0 |<br>
> | instance:m1.small | gauge | instance |<br>
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |<br>
> | ec26984024c1438e8e2f93dc6a8c5ad0 |<br>
> | memory | gauge | MB |<br>
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |<br>
> | ec26984024c1438e8e2f93dc6a8c5ad0 |<br>
> | vcpus | gauge | vcpu |<br>
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |<br>
> | ec26984024c1438e8e2f93dc6a8c5ad0 |<br>
> +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+<br>
><br>
><br>
> If the admin user can't rely on ceilometer guaranteeing availability of<br>
> the performance stats at all, then I think having an API in nova to report<br>
> them is in fact justifiable. In fact it is probably justifiable no matter<br>
> what as a fallback way to check that VMs are doing in the fact of failure<br>
> of ceilometer / part of the cloud infrastructure.<br>
><br>
> Daniel<br>
> --<br>
> |: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
> |: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
> |: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
> |: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a 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></div></blockquote></div><br></div>