wsgi conf file and command line opts

Asked by Armando Migliaccio

it seems that after removing the dependency on gflags some options like sqlconnection, working-directory, default_store, etc cannot be passed on the command line and must be parsed via glance.conf. Is this the desidered behaviour?
The reason why I am asking is because this does not seem to be consistent with the way nova workers parse options (as options are parsed on the command line).

Could someone fill me in on this? I am happy to file a bug and help with the fix, if needed.

Many thanks,
Armando

Question information

Language:
English Edit question
Status:
Solved
For:
Glance Edit question
Assignee:
No assignee Edit question
Solved by:
Armando Migliaccio
Solved:
Last query:
Last reply:
Revision history for this message
Armando Migliaccio (armando-migliaccio) said :
#1

Jay wrote:

Not sure, really. I think it's clear I'd prefer Nova take the approach
of Glance and Swift, which is to have minimal command line options for
server programs and use standard configuration files for documenting
program options.

But, Nova isn't Glance or Swift, and it would be up to the
contributors on that project to decide. Remember that at the last
summit, I tried to find a compromise with
http://wiki.openstack.org/CommonOptionsProcessing for the folks who
wanted to define all the program options as command-line options and
define those options in the modules where the option was defined. But
there was no critical mass behind the proposal, and frankly, in Glance
we just ripped out gflags and have adopted the Swift style of managing
program options which I believe is more in-line with the vast majority
of Python projects in the multiverse.