As soon as a VM is booted, 'ceilometer resource-show' returns
g@ubuntu:~/trigger$ ceilometer resource-show -r dd4a2a98-07bf-4c05-85dd-adfaa873531b
+-------------+------------------------------------------------------------------------+
| Property | Value |
+-------------+------------------------------------------------------------------------+
| source | |
| project_id | d7030309ef3c47a6ac95a01be6ddbd12 |
| user_id | f45dceb47a35417f813ad7cea8fc60ce |
| metadata | {u'ephemeral_gb': u'0', u'event_type': u'compute.instance.create.end', |
| | u'disk_gb': u'0', u'availability_zone': u'None', u'kernel_id': u'', |
| | u'ramdisk_id': u'', u'host': u'compute.ubuntu', u'memory_mb': u'48', |
| | u'instance_type': u'8', u'vcpus': u'1', u'root_gb': u'0', |
| | u'architecture': u'None', u'os_type': u'None', u'reservation_id': |
| | u'r-a9pg5fd4'} |
| resource_id | dd4a2a98-07bf-4c05-85dd-adfaa873531b |
+-------------+------------------------------------------------------------------------+
But after a minute or so, metadata values that relate to the specific instance become null.
g@ubuntu:~/trigger$ ceilometer resource-show -r dd4a2a98-07bf-4c05-85dd-adfaa873531b
+-------------+--------------------------------------------------------------------------+
| Property | Value |
+-------------+--------------------------------------------------------------------------+
| source | |
| project_id | d7030309ef3c47a6ac95a01be6ddbd12 |
| user_id | f45dceb47a35417f813ad7cea8fc60ce |
| metadata | {u'ephemeral_gb': u'', u'display_name': u'one', u'name': |
| | u'instance-00000023', u'disk_gb': u'', u'availability_zone': u'', |
| | u'kernel_id': u'', u'ramdisk_id': u'', u'vcpus': u'', u'memory_mb': u'', |
| | u'instance_type': u'10', u'host': |
| | u'41378f4bbbb00b48d03cd6b79d98bd0a900f8486201243a78c67e9b0', u'root_gb': |
| | u'', u'image_ref': u'05f878a5-cca3-48cf-94ba-6928e9c02441', |
| | u'architecture': u'', u'os_type': u'', u'reservation_id': u'', |
| | u'image_ref_url': u'http://10.0.0.1:8774/86339ddb59f74dabab0e0e9a87a6f26 |
| | 6/images/05f878a5-cca3-48cf-94ba-6928e9c02441'} |
| resource_id | dd4a2a98-07bf-4c05-85dd-adfaa873531b |
+-------------+--------------------------------------------------------------------------+
I suspect this is the result of values reported by pollsters overwriting the values reported by the notifications.
I ran into this issue today 'stable/grizzy 2013.1.2 June' ubuntu cloud archive release as well as on devstack stable/grizzly. I've looked into the issue, and indeed the notification is sending the correct metadata on instance.create and then subsequent pollsters overwrite the metadata, using novaclient. servers. list(detailed= True, search_ opts={' host': 'mynode', 'all_tenants': True}) which doesn't return values in regards to vcpu, memory, etc for complete metadata. In older versions of ceilometer, it used directly libvirt calls instead of novaclient to grab that metadata.