I forgot to add something to my 'wishlist' ;-)
Changing the way we configure Nova should be a process announced in
advanced. One or two releases in advance, to give enough time to teams
doing deployments and upgrades of Nova to be prepared. Changes that
can impact in the upgrade of the product
Christian Berendt wrote:
a) we should create a useful documentation including all flags
That's been identified as a necessary area of improvement for doc. I
plan to work on the raw info (organize them in themes and document their
use) and Anne should help me get it into the openstack manual.
can of worms
Just use optparse/argparse. paste.deploy handles configuration files
already, which is where most flags should really be... gflags adds
unneeded complexity for no real gains, IMHO. Swift and Glance do just
fine without gflags, as do the vast majority of Python projects. As
for
Thanks for starting this thread, comments below.
*Anne Gentle*
a...@openstack.org
my blog http://justwriteclick.com/ | my
bookhttp://xmlpress.net/publications/conversation-community/|
LinkedIn http://www.linkedin.com/in/annegentle |
Delicioushttp://del.icio.us/annegentle|
Twitter
A few points:
(1) I agree with Todd and others that having flags localized to where they
are used is good idea.
(2) We should do some work to re-localize many of the flags, there has been
a lot of kludge over time that just needs a little re-organization. This
will solve the which flags are
5 matches
Mail list logo
