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
t; >
>> >
>> > 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.
>> >
>> &g
> > 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>
> &g
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.openst
nstack.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
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
