Open Stack

Excerpts from Kendall J Nelson's message of 2016-01-05 13:48:46 -0600:
> 
> Okay, to clarify, you are saying pip freeze to get the list of libraries
> for the oslo.config.opts section in entry
> points here https://github.com/openstack/cinder/blob/master/setup.cfg#L44 ?

We do have a convention that the entry point name matches the library
name. Those values should be listed in the input file for the config
generator. They should *not* be listed in your setup.cfg.

Doug

> 
> 
>     All the Best,
>                                                           
>    Kendall J. Nelson                                      
>    Software Engineer &                                    
>                                                           
> 
> 
>     Openstack Cinder Contributor
>                                                            
>                                                            
>                                                            
>    E-mail: kjnelson at us.ibm.com                         IBM 
>    Cell Phone: (952) 215- 4025                             
>    IRC Nickname: diablo_rojo                 3605 Hwy 52 N 
>                                              Rochester, MN 
>                                                 55901-1407 
>                                              United States 
>                                                            
> 
> 
> 
> 
> 
> From:    Joshua Harlow <harlowja at fastmail.com>
> To:    "OpenStack Development Mailing List (not for usage questions)"
>             <openstack-dev at lists.openstack.org>
> Date:    01/04/2016 04:40 PM
> Subject:    Re: [openstack-dev] [all] Austin Summit Panel on Generation of
>             Sample Configuration Option Files
> 
> 
> 
> So just out of curiosity:
> 
> https://review.openstack.org/#/c/219700/14/cinder/config/generate_cinder_opts.py
> 
> 
> Why does this not use
> https://github.com/openstack/cinder/blob/master/setup.cfg#L44 to find
> the exposed cinder configuration options (and drivers that cinder
> has/provides should expose a similar entrypoint and so-on)?
> 
> Also just brainstorming, but said 'generate_cinder_opts.py' should
> likely also have the output of `pip freeze` (sorted and canonicalized
> would be best to) because the generated opts that are found in other
> libraries (those libraries should/typically expose an entrypoint to list
> there own opts) depend on *exactly* what version of the package(s) is
> installed (yes I know this makes the application <-> library API for
> those libraries extremely weak/non-existent but this is how things have
> gone).
> 
> -Josh
> 
> 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 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/
> >
> >
> > All the Best,
> >
> > *Kendall J. Nelson*
> > Software Engineer &
> >
> > Openstack Cinder Contributor
> > ------------------------------------------------------------------------
> > *E-mail:*_kjnelson at us.ibm.com_ <mailto:zahill at us.ibm.com>
> > *Cell Phone:*(952) 215- 4025*
> > IRC Nickname:*diablo_rojo
> > IBM
> >
> > 3605 Hwy 52 N
> > Rochester, MN 55901-1407
> > United States
> >
> >
> >
> >