Re: [openstack-dev] [ceilometer] Why edited configuration get replaced after stack.sh

2016-03-15 Thread Sean Dague
Devstack assumes it owns everything on the system, and will overwrite all configs all the time. This is to keep things repeatable. There are 3 approaches you could to support your approach here. The first one is have a custom branch of ceilometer which you then reference in local.conf. 1)

Re: [openstack-dev] [ceilometer] Why edited configuration get replaced after stack.sh

2016-03-15 Thread Umar Yousaf
Hello Rubab, I already know these steps.But does this mean you have to update the previous all custom configurations again and again whenever you stack.sh??? Is there any way possible that these changes don't get updated because in a testing environment like mine I have to do it very often.

Re: [openstack-dev] [ceilometer] Why edited configuration get replaced after stack.sh

2016-03-15 Thread Rubab Syed
Hi Umar, As far as I know, you should follow these steps to make this work: 1- Run stack.sh 2- Add rules to policy.json in /etc/ceilometer 3- Restart ceilometer service. Follow this link [1] to see how can you restart a particular service. [1]

[openstack-dev] [ceilometer] Why edited configuration get replaced after stack.sh

2016-03-15 Thread Umar Yousaf
Hi, I am pretty new to openstack and I have a very basic question to ask. I have a single node liberty edition of devstack up and running. I order to get *ceilometer events* for instances running on demo tenant with admin token set I have heard about role based access control (rbac) following