RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1082729 - [RFE] allow for Keystone/LDAP configuration at deployment time
Summary: [RFE] allow for Keystone/LDAP configuration at deployment time
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Icehouse
Assignee: Rich Megginson
QA Contact: Mike Abrams
URL:
Whiteboard:
Depends On:
Blocks: 1172310
TreeView+ depends on / blocked
 
Reported: 2014-03-31 17:24 UTC by Giulio Fidente
Modified: 2016-05-19 15:47 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:47:19 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 129989 0 None None None Never
OpenStack gerrit 136415 0 None None None Never
OpenStack gerrit 150041 0 None None None Never

Description Giulio Fidente 2014-03-31 17:24:41 UTC 
It would be nice to allow for Keystone/LDAP Identity driver configuration at deployment time. Moving from the default SQL backend to LDAP currently requires users to hack into the database to update a few references, see https://bugzilla.redhat.com/show_bug.cgi?id=1072988

NOTE: puppet-keystone recipes seem to be ready for this
Comment 1 Gaël Chamoulaud 2014-11-21 16:38:47 UTC 
Backported to icehouse https://review.openstack.org/#/c/136415/
Comment 2 Rich Megginson 2015-01-26 17:04:33 UTC 
The above gerrit reviews are for juno - can we change the target release of this bug to juno, or should we close it and open a new bz against juno?
Note that 136415 for packstack is for read-only LDAP support - read-write LDAP works fine without it.
Comment 3 Mike McCune 2016-03-28 23:29:09 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 4 Chandan Kumar 2016-05-19 15:47:19 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.
Note You need to log in before you can comment on or make changes to this bug.