Bug 1061131

Summary:	[RFE] Updating keystone should be done via GUI instead of "engine-config" command
Product:	[Retired] oVirt	Reporter:	GenadiC <gcheresh>
Component:	ovirt-engine-webadmin	Assignee:	Oved Ourfali <oourfali>
Status:	CLOSED DUPLICATE	QA Contact:	GenadiC <gcheresh>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	bazulay, bugs, ecohen, gklein, iheim, mgoldboi, oblaut, rbalakri, s.kieske, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	infra
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-14 11:31:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1063716

Description GenadiC 2014-02-04 12:26:14 UTC

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:

Comment 1 Ofer Blaut 2014-02-05 14:29:30 UTC

moving to high, since if user has 3.4 install and would like to add neutron , restart engine will cause downtime

Comment 2 Sven Kieske 2014-02-06 08:07:40 UTC

Please don't forget REST-API users.

Comment 3 Itamar Heim 2014-02-09 08:52:38 UTC

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.

Comment 4 Barak 2014-02-11 12:40:25 UTC

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

Comment 6 Oved Ourfali 2015-04-14 11:31:16 UTC


*** This bug has been marked as a duplicate of bug 1157999 ***