Bug 1019616
Summary: | [RFE] glance integration: user needs to set KeystoneURL config in order to activate external provider | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Haim <hateya> |
Component: | ovirt-engine-setup | Assignee: | Ofer Schreiber <oschreib> |
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | bazulay, ebenahar, iheim, lpeer, oourfali, rbalakri, Rhev-m-bugs, scohen, yeylon |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | Flags: | sherold:
Triaged+
|
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | infra | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-04-06 08:38:28 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: |
Description
Haim
2013-10-16 07:24:39 UTC
(In reply to Haim from comment #0) > Description of problem: > > psql -U postgres engine -c "UPDATE vdc_options SET option_value = > 'http://10.35.161.239:35357/v2.0/' where option_id = '107' "; that's db hacking - use engine-config please... multiple auth providers not supported yet. plan is to add keystone as a provider later on. *** Bug 1019612 has been marked as a duplicate of this bug. *** (In reply to Itamar Heim from comment #1) > (In reply to Haim from comment #0) > > Description of problem: > > > > psql -U postgres engine -c "UPDATE vdc_options SET option_value = > > 'http://10.35.161.239:35357/v2.0/' where option_id = '107' "; > > that's db hacking - use engine-config please... > > multiple auth providers not supported yet. > plan is to add keystone as a provider later on. we need to provide better way, maybe using UI. We decided on engine-config, when there was a need only for one setting. IMO this is a valid approach. However, now we moved to configuration per provider, so obviously using engine-config isn't enough, so this was changed as part of Bug 1157999. Closing this as duplicate. *** This bug has been marked as a duplicate of bug 1157999 *** |