openstack-doc-core team mailing list archive

[Anne Gentle <anne@xxxxxxxxxxxxx>]

Hi again all -

I took a closer look this morning. The patch is only for Object
Storage installation using "zypper" commands for SLES.

So we need to figure out how to deal with this. The install guide
works in a way that all OpenStack projects are installed. If we accept
that we want the SLES instructions, we'd have to mark up all the rest
to not be included (I think). Or we restructure it somehow.

I also wanted to report back on the way the build works. I don't think
we have to change anything in the pom to add another platform. See:

<properties>
        <!-- This is set by Jenkins according to the branch. -->
        <release.path.name>local</release.path.name>
        <comments.enabled>1</comments.enabled>
        <operating.system>yum</operating.system>
        <!-- This is set by Jenkins to run twice for each similar
operating system group -->
        <profile.os>centos;fedora;rhel</profile.os>
    </properties>

Rather we have to change the Jenkins build files
/modules/openstack_project/files/jenkins_job_builder/config/manuals.yaml
to add a third build job with these "goals" -

-Doperating.system=zypper -Dprofile.os=sles;opensuse
-Drelease.path.name=${DOC_RELEASE_PATH}
-Dcomments.enabled=${DOC_COMMENTS_ENABLED}

So, how can we incorporate this info? Perhaps we include it in the
Object Storage Admin guide only and skip the conditionalizing since it
doesn't work well in our current scheme with all projects being
installed?

Thanks,
Anne

On Sun, Nov 11, 2012 at 11:00 AM, Anne Gentle
<annegentle@xxxxxxxxxxxxxxxxxx> wrote:
> Yes we do something like that already and it sure makes the release easier since it is just variables in the Pom. It is possible we don't have to change the Pom at all and just add the variable to the ci puppet scripts so Jenkins knows about the new conditions but I'll have to look when I have a "real" computer. :)
>
> Anne Gentle
> Content Stacker
> anne@xxxxxxxxxxxxx
>
>
> On Nov 11, 2012, at 9:52 AM, David Cramer <david.cramer@xxxxxxxxxxxxx> wrote:
>
>> I'll talk to you about this next week Anne, but I think we also need a
>> configuration point in the pom so you can control what the output file
>> name is and avoid having to use postProcess to move output out of the
>> way of building the next profile. I.e.
>>
>> <outputBasename>install-guide-suse</outputBasename>
>>
>> Would result in install-guide-suse.pdf and a install-guide-suse webhelp
>> dir name.
>>
>> David
>>
>> On 11/11/2012 09:18 AM, Anne Gentle wrote:
>>> Yeah, I can patch-the-patch next week to do so. I'll put a comment on
>>> it to that effect.
>>>
>>> So others know the magic behind the scenes: Looks like he's using
>>> os="sles;opensuse" for all conditional text so the pom.xml needs some
>>> work. Plus for it to build correctly, we may also need to change some
>>> of the openstack-ci-puppet scripts, plus update the
>>> www/install/index.html file to point to the new file, and get a new
>>> disqus-id. Whew!
>>>
>>> Anne
>>>
>>> On Sat, Nov 10, 2012 at 10:33 PM, Tom Fifield <fifieldt@xxxxxxxxxxxxxx> wrote:
>>>> Hi,
>>>>
>>>> We've had a patch to bring SUSE into the install guide:
>>>>
>>>> https://review.openstack.org/#/c/15721
>>>>
>>>> I'm guessing the pom file needs an update for a new os= ?
>>>>
>>>> Regards,
>>>>
>>>> Tom
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~openstack-doc-core
>>>> Post to     : openstack-doc-core@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack-doc-core
>>>> More help   : https://help.launchpad.net/ListHelp
>>