On Mon, Aug 05 2013, Herndon, John Luke (HPCS - Ft. Collins) wrote:
> This plans sounds good to me. We can enable/disable the event api for
> users, but is there a way to restrict a user to viewing only his/her
> events using the policy system? Or do we not need to do that?
There may be, but we d
Hi Julien,
On 8/5/13 2:04 AM, "Julien Danjou" wrote:
>On Sat, Aug 03 2013, Herndon, John Luke (HPCS - Ft. Collins) wrote:
>
>Hi John,
>
>> Hello, I'm currently implementing the event api blueprint[0], and am
>> wondering what access controls we should impose on the event api. The
>> purpose of t
On Sat, Aug 03 2013, Herndon, John Luke (HPCS - Ft. Collins) wrote:
Hi John,
> Hello, I'm currently implementing the event api blueprint[0], and am
> wondering what access controls we should impose on the event api. The
> purpose of the blueprint is to provide a StackTach equivalent in the
> ceil
On 08/02/2013 06:26 PM, Herndon, John Luke (HPCS - Ft. Collins) wrote:
Hello, I'm currently implementing the event api blueprint[0], and am
wondering what access controls we should impose on the event api. The
purpose of the blueprint is to provide a StackTach equivalent in the
ceilometer api. I
Hello, I'm currently implementing the event api blueprint[0], and am
wondering what access controls we should impose on the event api. The
purpose of the blueprint is to provide a StackTach equivalent in the
ceilometer api. I believe that StackTach is used as an internal tool which
end with no acce
