Replace ci.o.o links with docs.o.o/infra

The http://ci.openstack.org/ documentation site has been deprecated,
replaced by redirects to corresponding paths within
http://docs.openstack.org/infra/ where other Project Infrastructure
documentation already resides.

Change-Id: Ie915eb9711c100e536498c57549ef901b1db3abc

README.md

@@ -12,12 +12,12 @@ either in agent or apply mode.
 These puppet modules require puppet 2.7 or greater. Additionally, the
 site.pp manifest assumes the existence of hiera.
 
-See http://ci.openstack.org for more information.
+See http://docs.openstack.org/infra/system-config for more information.
 
 Documentation
 ==============
 
-The documentation presented at http://ci.openstack.org comes from
+The documentation presented at http://docs.openstack.org/infra/system-config comes from
 git://git.openstack.org/openstack-infra/system-config repo's docs/source.  To
 build the documentation use
 

doc/source/jenkins.rst

@@ -116,7 +116,7 @@ hand:
 #. Setup matrix security: add the 'authenticated' pseudo user and
    grant Admin access to your own user.
 
-#. Setup one account per `http://ci.openstack.org/jenkins-job-builder/installation.html#configuration-file`
+#. Setup one account per `http://docs.openstack.org/infra/jenkins-job-builder/installation.html#configuration-file`
    and grab the API token for it.
 
 #. Configure the number of executors you want on the Jenkins Master

doc/source/jjb.rst

@@ -23,7 +23,7 @@ At a Glance
 :Bugs:
   * https://storyboard.openstack.org/#!/project/723
 :Resources:
-  * `Reference Manual <http://ci.openstack.org/jenkins-job-builder>`_
+  * `Reference Manual <http://docs.openstack.org/infra/jenkins-job-builder>`_
 
 Overview
 ========
@@ -237,7 +237,7 @@ it finds the XML is different then it will proceed to send this
 to Jenkins, otherwise it is skipped. If a job is accidentally deleted
 then this file should be modified or removed.
 
-.. _cache: http://ci.openstack.org/jenkins-job-builder/installation.html#running
+.. _cache: http://docs.openstack.org/infra/jenkins-job-builder/installation.html#running
 
 Sending a Job to Jenkins
 ------------------------

doc/source/nodepool.rst

@@ -26,7 +26,7 @@ At a Glance
 :Bugs:
   * https://storyboard.openstack.org/#!/project/668
 :Resources:
-  * `Nodepool Reference Manual <http://ci.openstack.org/nodepool>`_
+  * `Nodepool Reference Manual <http://docs.openstack.org/infra/nodepool>`_
 
 Overview
 ========

doc/source/running-your-own.rst

@@ -52,7 +52,7 @@ Initial setup
    For more details on the config repo split, read the following spec:
    http://specs.openstack.org/openstack-infra/infra-specs/specs/config-repo-split.html.
 
-#. Follow http://ci.openstack.org/puppet.html#id2 and use your repository
+#. Follow http://docs.openstack.org/infra/system-config/puppet.html#id2 and use your repository
    in addition to the OpenStack CI repository. This is appropriate to stay in
    sync with OpenStack Infra team rolling out new functionality and at the same
    time applying the necessary customizations through the config overrides.
@@ -354,7 +354,7 @@ which get the most load (as they run jobs from anyone).
 
 #. Update hiera with the relevant parameters.
    You'll need to get the jenkins_jobs_password from Jenkins (see
-   `http://ci.openstack.org/jenkins-job-builder/installation.html#configuration-file`)
+   `http://docs.openstack.org/infra/jenkins-job-builder/installation.html#configuration-file`)
    after Jenkins is up - start with it set to ''.  You can use your own user or
    make a dedicated user.
 

doc/source/storyboard.rst

@@ -29,7 +29,7 @@ At a Glance
 :Bugs:
   * https://storyboard.openstack.org/#!/project/456
 :Resources:
-  * `StoryBoard Documentation <http://ci.openstack.org/storyboard/>`_
+  * `StoryBoard Documentation <http://docs.openstack.org/infra/storyboard/>`_
   * `StoryBoard Wiki <https://wiki.openstack.org/wiki/StoryBoard>`_
   * `StoryBoard Roadmap <https://wiki.openstack.org/wiki/StoryBoard/Roadmap>`_
 

doc/source/third_party.rst

@@ -284,7 +284,7 @@ uploaded and will report the results to Gerrit automatically.
 The Zuul Gerrit Trigger Way
 ---------------------------
 
-`Zuul <http://ci.openstack.org/zuul.html>`_ is a tool that determines what jobs are run when.
+`Zuul <http://docs.openstack.org/infra/system-config/zuul.html>`_ is a tool that determines what jobs are run when.
 Zuul listens to the Gerrit event stream, and first tries to match each event to one or more pipelines.
 Zuul’s pipelines are configured in a single file called layout.yaml.
 Here’s a snippet from that file that constructs the ``check`` pipeline taken from this
@@ -312,7 +312,7 @@ patch set created. The matching event will invoke the configured Jenkins job(s)
 to Gerrit with a ``verified +1`` vote, and if any one fails, with a ``verified -1``.
 
 The sample includes other possible configurations, or you can configure your own by
-following the `Zuul layout documentation <http://ci.openstack.org/zuul/zuul.html#layout-yaml>`_
+following the `Zuul layout documentation <http://docs.openstack.org/infra/zuul/zuul.html#layout-yaml>`_
 
 After a Gerrit event matches a pipeline, Zuul will look at the project identified
 in that Gerrit event and invoke the Jenkins jobs specified in the ``projects`` section
@@ -343,7 +343,7 @@ and project-pipeline-job definitions.
 Managing Jenkins Jobs
 ---------------------
 When code is pushed to Gerrit, a series of jobs are triggered that run a series
-of tests against the proposed code. `Jenkins <http://ci.openstack.org/jenkins.html>`_
+of tests against the proposed code. `Jenkins <http://docs.openstack.org/infra/system-config/jenkins.html>`_
 is the server that executes and
 manages these jobs. It is a Java application with an extensible architecture
 that supports plugins that add functionality to the base server.
@@ -354,15 +354,15 @@ You may manually edit a Jenkins job as an administrator in Jenkins. However,
 in a testing platform as large as the upstream OpenStack CI system,
 doing so manually would be virtually impossible and fraught with errors.
 Luckily, there is a helper tool called `Jenkins Job Builder (JJB)
-<http://ci.openstack.org/jenkins-job-builder/>`_ that
+<http://docs.openstack.org/infra/jenkins-job-builder/>`_ that
 constructs and manages these XML configuration files after reading a
 set of YAML files and job templating rules. These references provide more details:
 
 * `A basic overview of using JJB to define projects, templates, and jobs in yaml
-  format is available here. <http://ci.openstack.org/jjb.html>`_
+  format is available here. <http://docs.openstack.org/infra/system-config/jjb.html>`_
 
 * `The official documentation to define Jenkins jobs using JJB is here.
-  <http://ci.openstack.org/jenkins-job-builder/definition.html>`_
+  <http://docs.openstack.org/infra/jenkins-job-builder/definition.html>`_
 
 * `The JJB description of all jobs used by OpenStack are defined in this folder.
   <https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs>`_

doc/source/zuul.rst

@@ -26,7 +26,7 @@ At a Glance
 :Bugs:
   * https://storyboard.openstack.org/#!/project/679
 :Resources:
-  * `Zuul Reference Manual <http://ci.openstack.org/zuul>`_
+  * `Zuul Reference Manual <http://docs.openstack.org/infra/zuul>`_
 
 Overview
 ========

modules/openstack_project/templates/zuul/status.html.erb

@@ -260,7 +260,7 @@ progress[aria-valuenow]:before  {
 	system.  Each of the sections below is a separate pipeline
 	configured to automate some portion of the testing or
 	operation of the OpenStack project.  For more information, please see
-	<a href="http://ci.openstack.org/zuul">the Zuul reference manual.</a>
+	<a href="http://docs.openstack.org/infra/zuul">the Zuul reference manual.</a>
       </p>
 
       <p>

setup.cfg

@@ -5,7 +5,7 @@ description-file =
     README.md
 author = OpenStack Infrastructure Team
 author-email = openstack-infra@lists.openstack.org
-home-page = http://ci.openstack.org/
+home-page = http://docs.openstack.org/infra/system-config/
 classifier =
     Environment :: OpenStack
     Intended Audience :: Information Technology