Open Stack

I mentioned the keystone chapter as a good place to start because the
issues impact the installation of most if not all other services. Also, I
view the patch as more of an experiment to see if we could integrate Debian
better into the guide without disabling Debconf, impacting installation for
other distros, or reversing much of the effort to reduce kludge in the Juno
cycle. I think your patch accomplishes most of those points fairly well,
but I'm still curious about other chapters.

At this point, almost every other chapter in the Debian variant of the Juno
guide needs similar patches to improve the content and make it consistent.
Furthermore, I anticipate that testing the installation process on Debian
will generate more patches. With the Kilo fork of the installation guide
likely coming within the next month or so, I'm asking the team whether it
makes sense to try fixing the Debian variant in Juno (potentially leaving
the guide in a bad/inconsistent state and making backports difficult) or
waiting until the Kilo cycle when larger changes make more sense.

On Thu, Jan 29, 2015 at 3:14 PM, Thomas Goirand <zigo at debian.org> wrote:

> On 01/29/2015 09:44 PM, Matt Kassawara wrote:
> > 4) Improve Debian content. Thomas Goirand wrote a patch [1] for Identity
> > service chapter. Due to significance of the patch, future similar
> > patches for other chapters, ongoing discussion, and a chances of leaving
> > the Juno version in a bad state (particularly making backports
> > confusing), we should consider pushing all of these changes to the Kilo
> > version.
>
> Matt, you were the one who pointed out that there was some work needed
> for Keystone (which is a good thing), and because of your reaction to
> the Debian version of the install-guide, I worked out this patch.
>
> Now, you've put the patch in a WIP state, blocking the improvement which
> you were the one to push for. This is very frustrating for me and
> demotivating.
>
> Please feel free to discuss about forking, backporting and so on, but do
> not take this as a reason to block my patch, on which I invested some
> time and effort.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150130/26b1c8ce/attachment.html>