On 2/23/2017 3:20 PM, David Medberry wrote:
and the 'nova-policy' command was introduced at the same time
finally found the right release notes:
ref: https://docs.openstack.org/releasenotes/nova/newton.html
The nova-policy command line is implemented as a tool to experience the
na <edgar.mag...@workday.com>,
"openstack-operators@lists.openstack.org"
<openstack-operators@lists.openstack.org>
Subject: Re: [Openstack-operators] Policy Updates
Yep what Logan said. I'm pretty sure Sean Dague talked about this at the last
Operator's mid-cycle. The "blan
and the 'nova-policy' command was introduced at the same time finally
found the right release notes:
ref: https://docs.openstack.org/releasenotes/nova/newton.html
The nova-policy command line is implemented as a tool to experience the
under-development feature policy discovery. User can
Yep what Logan said. I'm pretty sure Sean Dague talked about this at the
last Operator's mid-cycle. The "blank" policy.json just means you get the
default policies. You set a value to override the defaults.
I don't see it in the Ocata relnotes but git indicates this is where it
happened:
I think this actually started in Newton. Yes it ships blank, however
there is still a default policy implemented as before with similar
defaults separating the admin and user roles. The default policy is
implemented in the nova code base
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
