I'd say, no. We should not be setting a default at all. Ther is a
readically different approach between Fedora and Debian regarding thee
state that an application is in post Package install. The Debian
approach will make you go through the configuration, and leave you
with a working application. THe Fedora approach assumes that you are
doing an unattended install and upgrade, and that you will configure
the application afterwards.
Our sample configuration file should instead be commented to show the
user what they need to set in order to get the various back ends
working. But assuming MySQL, SQLITE, or LDAP, will be wrong for some
subset of users.
On 02/22/2012 12:30 PM, Dan Prince wrote:
----- Original Message -----
From: "Alan Pevec"<apevec@xxxxxxxxx>
To: "Fedora Cloud SIG"<cloud@xxxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, February 22, 2012 12:14:29 PM
Subject: Re: keystone config file defaults
On Wed, Feb 22, 2012 at 6:11 PM, Dan Prince<dprince@xxxxxxxxxx>
wrote:
Reverse that diff!
26c27
< driver = keystone.identity.backends.kvs.Identity
---
driver = keystone.identity.backends.sql.Identity
yeah, I do that
http://pkgs.fedoraproject.org/gitweb/?p=openstack-keystone.git;a=commitdiff;h=074d4a0762a33d2b020920be3650849cf2f69ea0
Ah. Thanks Alan. I must have pulled it just before that change went in this morning.
Cheers.
Next on my list is to switch to mysql, same like openstack-nova RPM.
Sounds good.
Alan
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
