I would like involvement in this discussion too from a documentation perspective... particularly maintaining the configuration reference and possibly standardizing how packagers include dynamic configuration files.
On Wed, Jan 6, 2016 at 10:53 AM, Martin Hickey <martin.hic...@ie.ibm.com> wrote: > Hey Kendall, > > Sure. Count me in! :) > > Thanks,, > Martin > > > [image: Inactive hide details for "Kendall J Nelson" ---06/01/2016 > 16:57:41---Hey Martin, I thought it might be interesting to get a]"Kendall > J Nelson" ---06/01/2016 16:57:41---Hey Martin, I thought it might be > interesting to get a panel discussion at the > > From: "Kendall J Nelson" <kjnel...@us.ibm.com> > To: "OpenStack Development Mailing List \(not for usage questions\)" < > openstack-dev@lists.openstack.org> > Date: 06/01/2016 16:57 > > Subject: Re: [openstack-dev] [all] Austin Summit Panel on Generation of > Sample Configuration Option Files > ------------------------------ > > > > Hey Martin, > > I thought it might be interesting to get a panel discussion at the Summit > to discuss the lack of consistency/ work towards a more universal way of > using the oslo config generator. Would you be interested? I was hoping to > get someone from Neutron, Nova and Keystone and I could represent Cinder. > > All the Best, > *Kendall J. Nelson* > Software Engineer &Openstack Cinder Contributor > ------------------------------ > *E-mail:* *kjnel...@us.ibm.com* <zah...@us.ibm.com> > *Cell Phone:* (952) 215- 4025 > *IRC Nickname:* diablo_rojo > [image: IBM] > > 3605 Hwy 52 N > Rochester, MN 55901-1407 > United States > > > [image: Inactive hide details for "Martin Hickey" ---01/06/2016 06:34:59 > AM---Hi Jay, +1 on the lack of consistency between projects. W]"Martin > Hickey" ---01/06/2016 06:34:59 AM---Hi Jay, +1 on the lack of consistency > between projects. When adding the generator > > From: "Martin Hickey" <martin.hic...@ie.ibm.com> > To: jsbry...@electronicjungle.net, "OpenStack Development Mailing List > \(not for usage questions\)" <openstack-dev@lists.openstack.org> > Date: 01/06/2016 06:34 AM > Subject: Re: [openstack-dev] [all] Austin Summit Panel on Generation of > Sample Configuration Option Files > ------------------------------ > > > > Hi Jay, > > +1 on the lack of consistency between projects. When adding the generator > to Neutron, we could not find a consistent pattern so we tried to adopt as > best as possible. > > Let me know if you need any feedback on the Neutron experience. > > Regards, > Martin > > > [image: Inactive hide details for "Jay S. Bryant" ---05/01/2016 > 19:56:25---Ben, Please see my in-line responses ...]"Jay S. Bryant" > ---05/01/2016 19:56:25---Ben, Please see my in-line responses ... > > From: "Jay S. Bryant" <jsbry...@electronicjungle.net> > To: openst...@nemebean.com, "OpenStack Development Mailing List (not for > usage questions)" <openstack-dev@lists.openstack.org> > Date: 05/01/2016 19:56 > Subject: Re: [openstack-dev] [all] Austin Summit Panel on Generation of > Sample Configuration Option Files > ------------------------------ > > > > Ben, > > Please see my in-line responses ... > > On 01/04/2016 05:43 PM, Ben Nemec wrote: > > On 01/04/2016 03:50 PM, Kendall J Nelson wrote: > >> Hello, > >> > >> > >> In brainstorming ideas for talks at the upcoming summit, I thought about > >> some of the things I had worked on for Cinder and what could still be > >> improved. One of the things I have been looking into is the generation > >> of sample configuration option files. Upon initial research it looks > >> like none of the main projects are doing it the same way. > > I'm not sure what you mean. Nova, Neutron, Keystone, Glance, and Heat > > (at least) are all using the oslo-config-generator tool for this. There > > might be some slight variation in how they call it, but they are using > it. > Yes, we know that they are all using oslo-config-generator but there is > not consistency > in how the information that oslo-config-generator needs to do its job is > being created. > Kendall is looking to better understand what we should be doing and try > to bring > greater consistency between the projects. > > > I only vaguely recall having discussions about this with Cinder, so I'd > > be interested in a refresher around why Cinder didn't want to do it the > > same way. I kind of considered it a solved problem. > So, the challenge Cinder has is the fact that there are many > configuration options with all the > different drivers. We had proposed a static cinder/opts.py file with > hacking checks to ensure > that all new options were pulled into the file. This was considered > undesirable. This lead to > the current solution where we are working to find all the possible > option lists to dynamically > create the cinder/opts.py file. Similar to what we used to do with the > old config generator. > > For Nova, having a dynamic solution is less important as they don't have > options changing > as frequently. It appears that Neutron was less concerned about the > potentially dynamic nature > of options in their drivers. > > > For reference: > > Nova: *https://github.com/openstack/nova/blob/master/tox.ini#L90* > <https://github.com/openstack/nova/blob/master/tox.ini#L90> > > Neutron: *https://github.com/openstack/neutron/blob/master/tox.ini#L198* > <https://github.com/openstack/neutron/blob/master/tox.ini#L198> > > which calls > > > *https://github.com/openstack/neutron/blob/master/tools/generate_config_file_samples.sh#L17* > <https://github.com/openstack/neutron/blob/master/tools/generate_config_file_samples.sh#L17> > > Keystone: > *https://github.com/openstack/keystone/blob/master/tox.ini#L148* > <https://github.com/openstack/keystone/blob/master/tox.ini#L148> > > Etc... > > > >> I thought it > >> might be interesting to get a panel together to talk about how it is > >> done for each project, why it is done that way for each project, and > >> maybe discuss a more universal approach that could be implemented in > >> oslo and used by all the projects. Please let me know if you have > >> knowledge on your project’s method and are interested in being part of a > >> panel. > >> > >> > >> If you are interested in looking at Cinder’s approach, here is the patch > >> I implemented to make the generation of the sample config file dynamic: > >> *https://review.openstack.org/#/c/219700/* > <https://review.openstack.org/#/c/219700/> > >> > >> > >> All the Best, > >> > >> *Kendall J. Nelson* > >> Software Engineer & > >> > >> Openstack Cinder Contributor > >> ------------------------------------------------------------------------ > >> *E-mail:*_kjnel...@us.ibm.com_ <*mailto:zah...@us.ibm.com* > <zah...@us.ibm.com>> > >> *Cell Phone:*(952) 215- 4025* > >> IRC Nickname:*diablo_rojo > >> IBM > >> > >> 3605 Hwy 52 N > >> Rochester, MN 55901-1407 > >> United States > >> > >> > >> > >> > >> > >> > __________________________________________________________________________ > >> 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* > <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* > <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* > <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* > <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 > > > > __________________________________________________________________________ > 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