----- Original Message -----
From: "Alan Pevec" <apevec(a)gmail.com>
To: "Kashyap Chamarthy" <kchamart(a)redhat.com>, "Adam Young"
<ayoung(a)redhat.com>
> So, RDO just seems to be sticking with upstream behavior.
dist.conf is not upstream, it was introduced in the initial Fedora
packaging specifically to enforce distribution defaults.
Regarding paste.ini, the thinking was that this is NOT an user
configurable file and should be treated as _code_ because it has full
code paths for filters which could change between releases so RPM
packaging is doing the right thing by keeping distro default out of
/etc and overwriting it on upgrades. There's still an option for users
to create paste.ini in /etc or wherever and point to it in
/etc/keystone.conf [paste_deploy] section but this is problematic from
the support perspective.
Keystone project could consider providing something more supportable
like Glance with paste_deploy.flavor instead of documenting editing of
paste.ini.
Cheers,
Alan
OK, but in this case the keystone-paste.ini we are using in RDO includes the
admin_token_auth directives that the documentation patch is endeavoring to remove [1] and
the RHEL-OSP 7 beta packages I took a look at don't. Which is correct?
Thanks,
Steve
[1]
https://review.openstack.org/#/c/185120/1/doc/install-guide/section_keyst...