Description of problem: In order to work with Neutron you need to run "engine-config -s Keystone Auth Url=http://<keystone_ip>:<keystone_port>/v2.0" command and then restart the engine. It should be done via GUI for better user experience. Version-Release number of selected component (if applicable): How reproducible: Always Actual results: Configuration of Keystone is done via engine-config command Expected results: Configuration of Keystone shold be done via GUI Additional info:
moving to high, since if user has 3.4 install and would like to add neutron , restart engine will cause downtime
Please don't forget REST-API users.
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
This is a part of a larger feature, Currently keystone is hidden under the hood (and used by Newtron & glance). We need to provide a separate approach and integrate keystone as authentication domain (which may happen for 3.4), and than depend on it for the other providers. Or we could add specifically specific keystone provider (only for use by other providers to depend on). Anyway this is not in the scope for 3.4 moving to 3.5
*** This bug has been marked as a duplicate of bug 1157999 ***