[openstack-dev] [ceilometer] Inconsistent timestamping of polled data

2015-10-09 Thread Wen Zhi WW Yu

Hi all,

As Gordon descriped in https://bugs.launchpad.net/ceilometer/+bug/1491509 ,
many of pollsters define the timestamp individually for each sample that is
generated rather than basing on when the data was polled. I agree with
Gordon on that the timestamping of samples should base on when the data was
polled.

What's your opinion on this?

Best Regards,
Yu WenZhi(余文治)
OpenStack on Power Development, IBM Shanghai
2F, 399 Keyuan Rd, Zhangjiang Chuangxin No. 10 Building, Zhangjiang High
Tech Park Shanghai
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Nova]Need suggestion for fixing bug 1466451(pci_passthrough_whitelist configration)

2015-07-20 Thread Wen Zhi WW Yu

Hi,

I'm working on bug 1466451, which is about the invalid configuration of
property pci_passthrough_whitelist in nova.

My proposal for fixing this issue is:

Before start nova-compute sevice, do a precheck against /etc/nova/nova.conf
file, if the value format of pci_passthrough_whitelist doesn't match with
any of following ones, the configuration will be recongnized as invalid:

1. Only devname:
pci_passthrough_whitelist = {devname:eth0,
physical_network:physnet1}
2. Only address:
pci_passthrough_whitelist = {address:*:0a:00.*,
physical_network:physnet1}
3. Only vendor_id + product_id:
pci_passthrough_whitelist = {vendor_id:1137,product_id:0071,
physical_network:physnet1}
4. devname and address:
pci_passthrough_whitelist = {devname:eth0, address:*:0a:00.*,
physical_network:physnet1}
5. devname and vendor_id+product_id':
pci_passthrough_whitelist = {devname:eth0,
vendor_id:1137,product_id:0071, physical_network:physnet1}
6. address and vendor_id+product_id':
pci_passthrough_whitelist = {address:*:0a:00.*,
vendor_id:1137,product_id:0071, physical_network:physnet1}
7. All of them:
pci_passthrough_whitelist = {devname:eth0, address:*:0a:00.*,
vendor_id:1137, product_id:0071, physical_network:physnet1}

Now I need some suggestion to proceed:

1. Do I need to register a blueprint for fixing this issue?
2. What kind of action is appropriate when the invalid configuration of
pci_passthrough_whitelist is dectected, logging the error or raising the
error?

Thanks in advance!

Best Regards,
Yu WenZhi(余文治)
OpenStack on Power Development, IBM Shanghai
2F, 399 Keyuan Rd, Zhangjiang Chuangxin No. 10 Building, Zhangjiang High
Tech Park Shanghai__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev