[Pulp-dev] complete - Re: Docs Builders and docs.pulpproject.org Migration

[Brian Bouterse]

Yesterday OSCI completed the migration, so docs.pulpproject.org is now
running in the new, OSCI hosted environment. There was a temporary ,
post-migration issue yesterday limiting the availability of some of the
older docs versions, but we got it resolved within an hour. I also updated
the docs builders. I've merged the necessary changes to pulp-ci [1], and
I've pushed the JJB config to all docs builders w/ the pulp-ci head
5e5f453. With that, Issue 3153 is now CLOSED.

I've taken down the old openshift V2 environment, so we are fully out of it
now! A big thanks to @Duck w/ OSCI who helped make this migration really
smooth.

[1]: https://github.com/pulp/pulp-ci/pull/466/files
[3]: https://pulp.plan.io/issues/3153

-Brian


On Sat, Dec 30, 2017 at 3:10 PM, Brian Bouterse <bbouters at redhat.com> wrote:

> tl;dr the docs.pulpprojet.org migration should be going live with the new
> OSCI hosting environment in the next few days. The existing environment
> (openshift V2) should stay on through the end of Jan, so even if this
> happens after Jan 1, docs should always be available.
>
> Yesterday I finished up the work [1] needed to get all of our docs
> publishing to the new OSCI environment. I updated the docs builders below,
> which are now publishing into the new environment. I verified all of the
> following builder in Jenkins will publish the expected docs in the new OSCI
> environment. We can easily revert any of these in case we need to push docs
> before the cutover occurs. Just reply-all to this thread requesting which
> ones to revert.
>
> docs-builder-2.14-dev
> docs-builder-2.15-build
> docs-builder-2.15-release
> docs-builder-3.0-dev
> docs-builder-master
>
> I just now took a backup of all existing content from the current site and
> I am storing it safely offline. I also just mirrored the content to the new
> OSCI environment. All of this means that we are ready to cutover.
>
> The next step is for us to wait on the OSCI folks to perform the cutover.
> As soon as the DNS updates, they will have to trigger the letsencrypt
> automation, otherwise all users will receive an HSTS error preventing them
> from seeing the docs. I've requested this from OSCI [2].
>
> I'll relay updates to this thread as things happen. Please send any
> questions or ideas.
>
> [1]: https://github.com/pulp/pulp-ci/pull/466/files
> [2]: https://pulp.plan.io/issues/3153#note-17
>
> -Brian
>
> On Wed, Dec 20, 2017 at 4:42 PM, Brian Bouterse <bbouters at redhat.com>
> wrote:
>
>> I got this mostly working today, but I ran into a few small issues with
>> the restricted commands allowed in the OSCI environments. All of the
>> builders should still build normally, except for the 2.14-release build
>> which I've temporarily modified.
>>
>> I will work on finishing this and completing the migration in the next
>> few days. I'll send email when things are updated.
>>
>>
>> On Wed, Dec 20, 2017 at 6:33 AM, Brian Bouterse <bbouters at redhat.com>
>> wrote:
>>
>>> As part of #3153 I'm testing some updates to the docs builders. If you
>>> are manually triggering docs updates today, your docs may not push to
>>> docs.pulpproject.org like normal. Instead they will push to the new
>>> hosting environment being tested.
>>>
>>> Once the testing is complete (today) I'm going to cut over the docs site
>>> to its new hosting home.I'll send a followup note to this thread when this
>>> is done and the docs builders are stable once again.
>>>
>>> If you have questions or run into issues, I'm on IRC as 'bmbouter'.
>>>
>>> [0]: https://pulp.plan.io/issues/3153
>>>
>>> -Brian
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180110/5279143d/attachment.htm>