Appendix A. The policy.json file in OpenStack Configuration Reference - liberty

[Matt Riedemann]

-----------------------------------
Built: 2015-11-12T06:24:40 00:00
git SHA: 3014e2a33b96190edb7cee52e06cc473c25167f5
URL: http://docs.openstack.org/liberty/config-reference/content/policy-json-file.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/config-reference/app_policy_json.xml
xml:id: policy-json-file

This came up in the nova irc channel today:

(12:32:56 PM) ev1lkry: everything I have read states that when editing the policy.json for nova that no services need to be restarted but when doing "compute_extension:flavormanage": [ ], it still says that the polixy doesnt hallow compute_extension:flavormanage to be perfomed on my other users
(12:33:10 PM) ev1lkry: i've edited the /nova/policy.json file
(12:33:21 PM) dansmith: ev1lkry: nova-api will need to be restarted at least
(12:34:56 PM) ev1lkry: dansmith that was it thank you
(12:39:50 PM) mriedem: ev1lkry: are there docs that are wrong somewhere?
(12:42:14 PM) ev1lkry: dansmith : I have read in some non openstack.org sites that you do not need to restart services when editing the policy.json file however the docs i've see doesnt say either for example: http://docs.openstack.org/kilo/config-reference/content/policy-json-file.html
(12:42:44 PM) alaski: ev1lkry: for some projects that might be true, like Glance I think, but not for Nova

So we should have a note in the docs that if you modify nova's policy.json file you'll need to restart the nova-api service.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/246058

[Gauvain Pocentek (gpocentek)]

I just tested on liberty. No need to restart nova-api to change the policy.

[Gauvain Pocentek (gpocentek)]

Is there any other project that requires a restart?

[OpenStack Infra (hudson-openstack)]

Change abandoned by Gauvain Pocentek (<email address hidden>) on branch: master
Review: https://review.openstack.org/246058
Reason: No update on this patch and on this bug in a month, let's abandon. Feel free to restore this patch if something new comes up.