Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

[Tony Breeds]

On Tue, Aug 01, 2017 at 06:32:36PM -0500, Matthew Thode wrote:
> +1 here as well, my only concern is that this will need to be consumed
> by so many projects.  If the community consensus on this is to go
> foraward with it then it's OK then.
> 
> http://codesearch.openstack.org/?q=oslo.policy=nope=requirements.txt=

So yeah this is used in a bunch of places.

Package  : oslo-policy [oslo-policy>=1.23.0] (used by 38 projects)
Also affects : 38 projects

They're all service-like projects.

We're currently sitting on 1.25.0 in u-c so the actual bump from 1.25.0
-> 1.25.1 is pretty low impact and as other have pointed out only alters
the way docs are built.

I'm +2 on the release and the requirements FFE for a constraints bump.

Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

[Matthew Thode]

+1 here as well, my only concern is that this will need to be consumed
by so many projects.  If the community consensus on this is to go
foraward with it then it's OK then.

http://codesearch.openstack.org/?q=oslo.policy=nope=requirements.txt=

On 17-08-01 16:58:53, Doug Hellmann wrote:
> Excerpts from Davanum Srinivas (dims)'s message of 2017-08-01 16:38:13 -0400:
> > +1, i'd support this as the 2 commits in there are not in the
> > normal/runtime flow for oslo.policy and just touch the doc bits.
> 
> +1 as well
> 
> > 
> > Thanks,
> > Dims
> > 
> > On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad  wrote:
> > > I was cleaning up a few documentation things for keystone and noticed an
> > > issue with how the configuration reference was rendering. It turns out
> > > the oslo.policy library needed a few tweaks to the show-policy directive
> > > along with some changes to keystone that allowed us to properly render
> > > all default policies. I documented these in a bug report tagging both
> > > projects [0].
> > >
> > > Two fixes were made to the oslo.policy library (thanks, Doug!) that will
> > > allow projects to render their entire policy document using the
> > > show-policy directive. Both fixes have merged in oslo.policy master and
> > > have been backported to stable/pike. I also have a release proposed to
> > > cut a new version of oslo.policy for us to use for pike [1].
> > >
> > > Opening this up for discussion to see if we can grant an FFE so that we
> > > can use the proper version of oslo.policy. More context in IRC as well 
> > > [2].
> > >
> > > Let me know if you have any questions. Thanks!
> > >
> > > Lance
> > >
> > > [0] https://bugs.launchpad.net/keystone/+bug/1707246
> > > [1] https://review.openstack.org/#/c/489599/
> > > [2]
> > > http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2017-08-01.log.html#t2017-08-01T18:14:57
> > >
> > >
> > >
> > > __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> > 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

[Doug Hellmann]

Excerpts from Davanum Srinivas (dims)'s message of 2017-08-01 16:38:13 -0400:
> +1, i'd support this as the 2 commits in there are not in the
> normal/runtime flow for oslo.policy and just touch the doc bits.

+1 as well

> 
> Thanks,
> Dims
> 
> On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad  wrote:
> > I was cleaning up a few documentation things for keystone and noticed an
> > issue with how the configuration reference was rendering. It turns out
> > the oslo.policy library needed a few tweaks to the show-policy directive
> > along with some changes to keystone that allowed us to properly render
> > all default policies. I documented these in a bug report tagging both
> > projects [0].
> >
> > Two fixes were made to the oslo.policy library (thanks, Doug!) that will
> > allow projects to render their entire policy document using the
> > show-policy directive. Both fixes have merged in oslo.policy master and
> > have been backported to stable/pike. I also have a release proposed to
> > cut a new version of oslo.policy for us to use for pike [1].
> >
> > Opening this up for discussion to see if we can grant an FFE so that we
> > can use the proper version of oslo.policy. More context in IRC as well [2].
> >
> > Let me know if you have any questions. Thanks!
> >
> > Lance
> >
> > [0] https://bugs.launchpad.net/keystone/+bug/1707246
> > [1] https://review.openstack.org/#/c/489599/
> > [2]
> > http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2017-08-01.log.html#t2017-08-01T18:14:57
> >
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

[Sean McGinnis]

> 
> Two fixes were made to the oslo.policy library (thanks, Doug!) that will
> allow projects to render their entire policy document using the
> show-policy directive. Both fixes have merged in oslo.policy master and
> have been backported to stable/pike. I also have a release proposed to
> cut a new version of oslo.policy for us to use for pike [1].
> 
> Opening this up for discussion to see if we can grant an FFE so that we
> can use the proper version of oslo.policy. More context in IRC as well [2].
> 

Those two commits [0] are very isolated, and should in no way impact
runtime. To me this looks like a low risk and a good gain to be able
to provide good documentation on policies.

[0] https://github.com/openstack/oslo.policy/compare/1.25.0...stable/pike

Sean

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

[Davanum Srinivas]

+1, i'd support this as the 2 commits in there are not in the
normal/runtime flow for oslo.policy and just touch the doc bits.

Thanks,
Dims

On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad  wrote:
> I was cleaning up a few documentation things for keystone and noticed an
> issue with how the configuration reference was rendering. It turns out
> the oslo.policy library needed a few tweaks to the show-policy directive
> along with some changes to keystone that allowed us to properly render
> all default policies. I documented these in a bug report tagging both
> projects [0].
>
> Two fixes were made to the oslo.policy library (thanks, Doug!) that will
> allow projects to render their entire policy document using the
> show-policy directive. Both fixes have merged in oslo.policy master and
> have been backported to stable/pike. I also have a release proposed to
> cut a new version of oslo.policy for us to use for pike [1].
>
> Opening this up for discussion to see if we can grant an FFE so that we
> can use the proper version of oslo.policy. More context in IRC as well [2].
>
> Let me know if you have any questions. Thanks!
>
> Lance
>
> [0] https://bugs.launchpad.net/keystone/+bug/1707246
> [1] https://review.openstack.org/#/c/489599/
> [2]
> http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2017-08-01.log.html#t2017-08-01T18:14:57
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [requirements][release][oslo] FFE for oslo.policy

[Lance Bragstad]

I was cleaning up a few documentation things for keystone and noticed an
issue with how the configuration reference was rendering. It turns out
the oslo.policy library needed a few tweaks to the show-policy directive
along with some changes to keystone that allowed us to properly render
all default policies. I documented these in a bug report tagging both
projects [0].

Two fixes were made to the oslo.policy library (thanks, Doug!) that will
allow projects to render their entire policy document using the
show-policy directive. Both fixes have merged in oslo.policy master and
have been backported to stable/pike. I also have a release proposed to
cut a new version of oslo.policy for us to use for pike [1].

Opening this up for discussion to see if we can grant an FFE so that we
can use the proper version of oslo.policy. More context in IRC as well [2].

Let me know if you have any questions. Thanks!

Lance

[0] https://bugs.launchpad.net/keystone/+bug/1707246
[1] https://review.openstack.org/#/c/489599/
[2]
http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2017-08-01.log.html#t2017-08-01T18:14:57




signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev