Comment 6 for bug 1913718
Revision history for this message
| Ghanshyam Mann (ghanshyammann) wrote Re: rally ci job is unstable - port list takes very long time | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
adding oslo.policy also.
slaweq, lbragstad, and I discussed it in the neutron IRC channel today[1].
Loading rules should be done during init time of policy instead of each rule check. we could move the load_rules() call from enforcer()[2] which is called for every check to policy __init__(). But we need to consider both cases here to know the side effect of it.
1. no policy file: this case will be fine and have no impact as there is no change in the rule after policy init.
2. policy file and operator change rule dynamically: This will be impacted and the operator needs to restart the API service to re-init the policy and load the latest rule. This is something we need to discuss more and get operator feedback if they do restart API service for any modification in policy file or not?
3. policy file name change or new policy file: this anyways needs policy restart. self.policy_file pick the right policy file during policy's init only[3] so new policy file need service restart now also which means no impact of moving load_rule() from enforce(). One example: https:/
[1] http://
[2] https:/
[3] https:/