Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-20 Thread Markus Zoeller
On 20.05.2016 16:51, Ben Nemec wrote: > On 05/20/2016 04:26 AM, Markus Zoeller wrote: >> On 05/19/2016 09:18 PM, Ben Nemec wrote: >>> On 05/17/2016 07:27 PM, Matt Fischer wrote: If config sample files are being used as a living document then that would be a reason to leave

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-20 Thread Ben Nemec
On 05/20/2016 04:26 AM, Markus Zoeller wrote: > On 05/19/2016 09:18 PM, Ben Nemec wrote: >> On 05/17/2016 07:27 PM, Matt Fischer wrote: >>> >>> If config sample files are being used as a living document then that >>> would be a reason to leave the deprecated options in there. In my >>>

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-20 Thread Markus Zoeller
On 05/19/2016 09:18 PM, Ben Nemec wrote: On 05/17/2016 07:27 PM, Matt Fischer wrote: If config sample files are being used as a living document then that would be a reason to leave the deprecated options in there. In my experience as a cloud deployer I never once used them in

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-19 Thread Ben Nemec
On 05/17/2016 07:27 PM, Matt Fischer wrote: > > If config sample files are being used as a living document then that > would be a reason to leave the deprecated options in there. In my > experience as a cloud deployer I never once used them in that manner > so it didn't occur

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-18 Thread Ian Cordasco
t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [all] Deprecated options in sample configs? > > If config sample files are being used as a living document then that would > > be a reason to leave the deprecated options in there. In my experience as a > > c

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Matt Fischer
> > > If config sample files are being used as a living document then that would > be a reason to leave the deprecated options in there. In my experience as a > cloud deployer I never once used them in that manner so it didn't occur to > me that people might, hence my question to the list. > >

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Andrew Laski
On Tue, May 17, 2016, at 03:00 PM, Dolph Mathews wrote: > I think the metadata_manager is one of many terrible examples of > deprecated configuration options. The documentation surrounding a > deprecation should *always* tell you why something is being > deprecated, and what you should be

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Ian Cordasco
t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [all] Deprecated options in sample configs? > I think the metadata_manager is one of many terrible examples of deprecated > configuration options. The documentation surrounding a deprecation should > *always* tell you why so

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Mathieu Gagné
On Tue, May 17, 2016 at 3:51 PM, Ben Nemec wrote: > > I'm +1 on removing them from sample configs. This feels like release > note information to me, and if someone happens to miss the release note > then they'll get deprecation warnings in their logs. The sample config >

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Ben Nemec
On 05/17/2016 01:47 PM, Andrew Laski wrote: > > > > On Tue, May 17, 2016, at 02:36 PM, Matt Fischer wrote: >> On Tue, May 17, 2016 at 12:25 PM, Andrew Laski > > wrote: >> >> I was in a discussion earlier about discouraging deployers from

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Matt Fischer
On Tue, May 17, 2016 at 12:47 PM, Andrew Laski wrote: > > > > On Tue, May 17, 2016, at 02:36 PM, Matt Fischer wrote: > > On Tue, May 17, 2016 at 12:25 PM, Andrew Laski wrote: > > I was in a discussion earlier about discouraging deployers from using >

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Dolph Mathews
I think the metadata_manager is one of many terrible examples of deprecated configuration options. The documentation surrounding a deprecation should *always* tell you why something is being deprecated, and what you should be using instead to achieve the same, or better, result moving forward. But

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Andrew Laski
On Tue, May 17, 2016, at 02:36 PM, Matt Fischer wrote: > On Tue, May 17, 2016 at 12:25 PM, Andrew Laski > wrote: >> I was in a discussion earlier about discouraging deployers from using >> deprecated options and the question came up about why we put >> deprecated >>

Re: [openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Matt Fischer
On Tue, May 17, 2016 at 12:25 PM, Andrew Laski wrote: > I was in a discussion earlier about discouraging deployers from using > deprecated options and the question came up about why we put deprecated > options into the sample files generated in the various projects. So, why >

[openstack-dev] [all] Deprecated options in sample configs?

2016-05-17 Thread Andrew Laski
I was in a discussion earlier about discouraging deployers from using deprecated options and the question came up about why we put deprecated options into the sample files generated in the various projects. So, why do we do that? I view the sample file as a reference to be used when setting up a