Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

I think there is a little misunderstanding over here, the key point about this problem is that you store your password as *plaintext* in the configuration file, maybe this password is also the password of many other systems. You can't stop the right person to do the right thing, if someone gets

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

2016-04-26 10:33 GMT-05:00 Daniel P. Berrange : > On Tue, Apr 26, 2016 at 04:24:52PM +0200, Jordan Pittier wrote: > > On Tue, Apr 26, 2016 at 3:32 PM, Daniel P. Berrange > > > wrote: > > > > > On Tue, Apr 26, 2016 at 08:19:23AM -0500, Doug Hellmann

[openstack-dev] [oslo.config] Encrypt the sensitive options

Hello, oslo team For now, some sensitive options like password or token are configured as plaintext, anyone who has the priviledge to read the configure file can get the real password, this may be a security problem that can't be unacceptable for some people. So the first solution comes to my

Re: [openstack-dev] [Glance] Policy

mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- 索广宇(Guangyu Suo) UnitedStack Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [Openstack] [openstack][ceilometer] cpu util stats using libvirt qemu:///system

! - alejandrito ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- 索广宇(Guangyu Suo

Re: [Openstack] [openstack][ceilometer] cpu util stats using libvirt qemu:///system

, May 14, 2014 at 12:57 PM, Guangyu Suo guan...@unitedstack.com wrote: Hi, The cpu_util is calculated by cpu time in pipeline's transformer: https://github.com/openstack/ceilometer/blob/master/etc/ceilometer/pipeline.yaml#L43 2014-05-14 22:55 GMT+08:00 Alejandro Comisario

[openstack-dev] [openstack][ceilometer] About Grouping Meters

Hello, Ceilometer Team, For now, the results listing meters are not grouped, even we can filter the results by resource_id, project_id or meter_name, but I don't think this is a good way to group the meters. See an example: suo@ustack:~/devstack$ ceilometer meter-list

Re: [openstack-dev] [openstack][ceilometer] About Grouping Meters

2013/8/8 Julien Danjou jul...@danjou.info On Thu, Aug 08 2013, Guangyu Suo wrote: Any ideas ? The meter name should be sufficient to have such information, no? Yeah, we can get the info from meter name by filtering prefix of meter name, but I think this is a little weird, and further more

[openstack-dev] [ceilometer][devstack] What are ceilometer/bin/* files used for ?

Hi, ceilometer stackers I notice that there are two files (ceilometer-rpc-zmq-receiver, ceilometer-send-counter) in ceilometer/bin directory, when and where we should use them, and why we put them there ? The reason I ask this question is that I want to add mysql support in devstack for

[openstack-dev] [ceilometer] Is there need to implement CloudWatch compatible API for Ceilometer?

Hi, all Since ceilometer is becoming stronger at monitoring side, more and more companies will use ceilometer as their monitoring service, and AWS CloudWatch API is more general for monitoring service, so I am wondering whether there is need to implement CloudWatch compatible API to make