Open Stack

Ah, I think I've responded too fast, sorry.

meter-list provides a list of various measurements that are being done per resource.
sample-list provides a list of samples per every meter: ceilometer sample-list --meter cpu_util -q resource_id=vm_uuid
These samples can be aggregated over a period of time per every meter and resource:
ceilometer statistics -m cpu_util -q 'timestamp>START;timestamp<=END;resource_id=vm_uuid' --period 3600

Vladik



----- Original Message -----
> From: "Daniel P. Berrange" <berrange at redhat.com>
> To: "Vladik Romanovsky" <vladik.romanovsky at enovance.com>
> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>, "John
> Garbutt" <john at johngarbutt.com>
> Sent: Thursday, 19 December, 2013 10:37:27 AM
> Subject: Re: [openstack-dev] [nova] VM diagnostics - V3 proposal
> 
> On Thu, Dec 19, 2013 at 03:47:30PM +0100, Vladik Romanovsky wrote:
> > I think it was:
> > 
> > ceilometer sample-list -m cpu_util -q 'resource_id=vm_uuid'
> 
> Hmm, a standard devstack deployment of ceilometer doesn't seem to
> record any performance stats at all - just shows me the static
> configuration parameters :-(
> 
>  ceilometer meter-list  -q 'resource_id=296b22c6-2a4d-4a8d-a7cd-2d73339f9c70'
> +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+
> | Name                | Type  | Unit     | Resource ID
> | | User ID                          | Project ID
> | |
> +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+
> | disk.ephemeral.size | gauge | GB       |
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |
> | ec26984024c1438e8e2f93dc6a8c5ad0 |
> | disk.root.size      | gauge | GB       |
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |
> | ec26984024c1438e8e2f93dc6a8c5ad0 |
> | instance            | gauge | instance |
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |
> | ec26984024c1438e8e2f93dc6a8c5ad0 |
> | instance:m1.small   | gauge | instance |
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |
> | ec26984024c1438e8e2f93dc6a8c5ad0 |
> | memory              | gauge | MB       |
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |
> | ec26984024c1438e8e2f93dc6a8c5ad0 |
> | vcpus               | gauge | vcpu     |
> | 296b22c6-2a4d-4a8d-a7cd-2d73339f9c70 | 96f9a624a325473daf4cd7875be46009 |
> | ec26984024c1438e8e2f93dc6a8c5ad0 |
> +---------------------+-------+----------+--------------------------------------+----------------------------------+----------------------------------+
> 
> 
> If the admin user can't rely on ceilometer guaranteeing availability of
> the performance stats at all, then I think having an API in nova to report
> them is in fact justifiable. In fact it is probably justifiable no matter
> what as a fallback way to check that VMs are doing in the fact of failure
> of ceilometer / part of the cloud infrastructure.
> 
> Daniel
> --
> |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org              -o-             http://virt-manager.org :|
> |: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|
>