Fix policy working in Blazar
Summary
========
Fix policy working in Blazar.
Problem description
================
Currently there is good base for policy in Blazar, but still we have some problems:
- when request comes to Blazar before any policy is enforced there are used params from
ctx to be put in target. So when it comes to enforcing, it looks like a==a
we need something inspired by Keystone policies:
https:/
https:/
Use Cases
---------------
- TBD
Proposed change
==============
TBD
Alternatives
-----------------
TBD
Data model impact
-------
TBD
REST API impact
-------
TBD
Security impact
-------
TBD
Notifications impact
-------
TBD
Other end user impact
-------
TBD
Performance impact
-------
None.
Other deployer impact
-------
TBD
Developer impact
-------
TBD
Dependencies
===========
TBD
Testing
======
TBD
Documentation impact
==================
TBD
References
=========
[1] https:/
Note: this form is based on the nova-specs template[1].
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Dina Belova
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
- Pierre Riteau
Related branches
Related bugs
Sprints
Whiteboard
History:
Gerrit topic: https:/
Addressed by: https:/
Fix policy working process