Ask Your Question

wsgi conf file and command line opts

asked 2011-02-28 15:38:51 -0500

armando-migliaccio gravatar image

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

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2011-03-01 19:32:16 -0500

armando-migliaccio gravatar image

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 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.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2011-02-28 15:38:51 -0500

Seen: 33 times

Last updated: Mar 01 '11