Am I understanding correctly that in Ocata release, the policy.json file for 
NOVA is blank?
What does that mean for us (operators)? Everything will be open for everybody 
for the other way around?

In any case, that sounds like an awful approach because know if we upgrade we 
will need to be sure that we have a proper json file while in the past we at 
least were starting from the default one.

Edgar

From: David Medberry <openst...@medberry.net>
Date: Thursday, February 23, 2017 at 10:45 AM
To: "openstack-operators@lists.openstack.org" 
<openstack-operators@lists.openstack.org>
Subject: [Openstack-operators] Policy Updates

Nova no longer ships with a fleshed-out skeleton of all policy.json. It ships 
blank.

Discussion in here on how to help operators select specific settings to include 
in their policy.json via documentation.

You (as an op) may want to review and comment on this. This model is being 
proposed for all openstack projects (or at least MORE openstack projects.)

https://review.openstack.org/#/c/433010<https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_c_433010&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=3tiVftxu5kWJH9yl4tb4lxPaW079paAEMVaQLaH6zFQ&s=p8d6hJ7YRUfgeFEI5IM40XIinJRezyxQu_dLUC9TO3E&e=>
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to