[Rdo-list] [OpenStack-docs] [install-guide] Status of RDO

[Matt Kassawara]

I think packages available for standalone installation (i.e., without a
deployment tool) should include complete upstream configuration files in
standard locations without modification. In the case of *-dist.conf files
with RDO packages, they seldom receive updates leading to deprecation
warnings and sometimes override useful upstream default values. For
example, most if not all services default to keystone for authentication
(auth_strategy), yet the RDO neutron packages revert authentication to
"noauth" in the *-dist.conf file. In another example, the RDO keystone
package only includes the keystone-paste.ini file as
/usr/share/keystone/keystone-dist-paste.ini rather than using the standard
location and name which leads to confusion, particularly for new users. The
installation guide contains quite a few extra steps and option-value pairs
that work around the existence and contents of *-dist.conf files...
additions that unnecessarily increase complexity for our audience of new
users.

On Wed, Oct 21, 2015 at 4:22 AM, Ihar Hrachyshka <ihrachys at redhat.com>
wrote:

>
> > On 21 Oct 2015, at 12:02, Alan Pevec <apevec at gmail.com> wrote:
> >
> > 2015-10-21 10:48 GMT+02:00 Ihar Hrachyshka <ihrachys at redhat.com>:
> >>> On 15 Oct 2015, at 20:31, Matt Kassawara <mkassawara at gmail.com> wrote:
> >>>
> >>> 4) Packages only reference upstream configuration files in standard
> >>> locations (e.g., /etc/keystone).
> >>
> >> Not sure what exactly it means. RDO packages are using
> neutron-dist.conf that contains RDO specific default configuration located
> under /usr/share/ for quite a long time.
> >
> > Yes, it's about dist.conf that are unique solution to provide distro
> > specific default values.
> > I'm not sure how are other distros solving this if at all, they
> > probably either rely on upstream defaults or their configuration
> > management tools?
> > Thing is that upstream defaults cannot fit all distributions, so I
> > would expect all distros to pick up our dist.conf solution but we
> > probably have not been exaplaning and advertising it enough hence
> > confusion in the upstream docs.
>
> I suspect other distros may just modify /etc/neutron/neutron.conf as they
> fit. It’s obviously not the cleanest solution.
>
> I believe enforcing a specific way to configure services upon
> distributions is not the job of upstream, as long as default upstream way
> (modifying upstream configuration files located in
> /etc/<service-name>/*.conf) works.
>
> Ihar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20151021/4411b1a3/attachment.html>