Listed below is the summary of conversation with Steve on this defect:
1. We can do away without the Keystonemiddleware changes. As the Keystonemiddleware.audit already sends user and project information as part of the event , ceilometer can extract info from there. Thus, https://review.openstack.org/#/c/198555/ can be abandoned.
2. Instead of changing the Event schema to add user_id and project_id as the base attributes, I added these as Traits by defining them in the events_definition file for the audit event types.
3 . I re-used the rbac.enforce method and made some changes so that it is able to better utilize the oslo policy engine.
Listed below is the summary of conversation with Steve on this defect:
1. We can do away without the Keystonemiddleware changes. As the Keystonemiddlew are.audit already sends user and project information as part of the event , ceilometer can extract info from there. Thus, https:/ /review. openstack. org/#/c/ 198555/ can be abandoned.
2. Instead of changing the Event schema to add user_id and project_id as the base attributes, I added these as Traits by defining them in the events_definition file for the audit event types.
3 . I re-used the rbac.enforce method and made some changes so that it is able to better utilize the oslo policy engine.