add support for user id in keystone cadf events
Bug #1429339 reported by
Steve Martinelli
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Low
|
Steve Martinelli |
Bug Description
as of kilo, keystone now allows a deployer to emit 'cadf' notifications instead of the standard notifications for most CRUD operations. as a result, the user_id that initiated the request is now available if 'cadf' is selected as the notifications format.
ceilometer may be updated to check for a user id in the initiator payload of the notification.
Changed in ceilometer: | |
assignee: | nobody → Steve Martinelli (stevemar) |
status: | New → In Progress |
Changed in ceilometer: | |
importance: | Undecided → Low |
Changed in ceilometer: | |
milestone: | none → kilo-3 |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
patch to address the issue: https:/ /review. openstack. org/#/c/ 151524/