glance-control all start not working

glance-control should be renamed until this is fixed. None of the --log-* flags work with it either.

And it isn't clear how to pass in the two conf files with this integrated helper anyway.

Is glance-control really necessary? I have *never* used it until now, just to check the validity of this bug.

If we are in favor of keeping glance-control, I would like to comment that I don't think this bug is valid anymore. All the services came up for me when i did a 'glance-control all start'.

Is it necessary? No. You should be able to use the upstart/daemon script of your platform du jour to run Glance servers in a production environment.

That said, what you *cannot* do with simple upstart/daemon scripts is:

* Pass custom parameters to the daemon (instead it must look in the standard configuration file directories for a config file
* Spin up multiple Glance servers simulataneously using different ports (in different config files)
* Use upstart/daemon scripts in the functional test suite (which uses glance-control to start servers)

And so, I do believe that glance-control has a place in Glance and is not irrelevant.

Not sure about the validity of this bug still, though... I'll have to test it out.
-jay

glance-control still works, it might need some love though...

I've confirmed that 'glance all start' works on master HEAD, but with the important caveat that all glance-<service>.conf files must be available in their default locations, as its not possible to specify a different config file per-service via the CONFPATH command line argument.