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 the
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 wrote:
> > > > Excerpts from Guangyu Suo's messa
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 min
a
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
索广宇(Guangyu Suo)
UnitedStack Inc.
_
2013/8/8 Julien Danjou
> 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
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
+--
OK, thanks, Julien, that is what I actually do.
2013/7/17 Julien Danjou
> On Wed, Jul 17 2013, Guangyu Suo wrote:
>
> > # Support potential entry-points console scripts
> > if [[ -d $CEILOMETER_DIR/bin ]]; then
> > CEILOMETER_BIN_DIR=$CEILOMETER_DIR/bin
> > e
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 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
ceilomete
