openstack
/
tripleo-docs
Code Issues Proposed changes

Update openstack.org to opendev.org 

We need to point now to opendev.org

Change-Id: I4f6e1c2d7ccc13c02e03b5333c30ca927756941e
This commit is contained in:
Carlos Camacho 2019-05-02 22:22:58 +02:00
parent 5faf00e45c
commit 449dd57547
34 changed files with 122 additions and 123 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -23,7 +23,7 @@ Getting Started
Documentation for the TripleO project is hosted on the OpenStack Gerrit
site. You can view all open and resolved issues in the
``openstack/tripleo-docs`` project at `TripleO
Reviews <https://review.openstack.org/#/q/project:openstack/tripleo-docs>`__.
Reviews <https://review.opendev.org/#/q/project:openstack/tripleo-docs>`__.
General information about contributing to the OpenStack documentation
available at `OpenStack Documentation Contributor

2
doc/source/ci/baremetal_jobs.rst
View File

@ -58,7 +58,7 @@ Parenting from upstream and RDO repos
-------------------------------------
Jobs that run from internal Zuul can parent off, and use resources (jobs,
roles etc.) from, upstream (review.openstack.org) and RDO
roles etc.) from, upstream (review.opendev.org) and RDO
(review.rdoproject.org) repos. As such, duplication can be kept to a minimum
and jobs that run internally on baremetal hardware can maintain parity with
OVB jobs run in RDO Cloud.

8
doc/source/ci/check_gates.rst
View File

@ -135,19 +135,19 @@ featureset override
In TripleO CI, we test each patchset using different jobs. These jobs
are defined using `featureset config files
<http://git.openstack.org/cgit/openstack/tripleo-quickstart/tree/config/general_config>`_.
<https://opendev.org/openstack/tripleo-quickstart/src/branch/master/config/general_config>`_.
Each featureset config file is mapped to a job template that is defined in
`tripleo-ci <http://git.openstack.org/cgit/openstack-infra/tripleo-ci/tree/zuul.d>`_.
`tripleo-ci <https://opendev.org/openstack-infra/tripleo-ci/src/branch/master/zuul.d>`_.
Tempest tests are basically triggered in scenario jobs in order to post validate the
a particular scenario deployment.
The set of tempest tests that run for a given TripleO CI job is defined in the
`featureset config files
<http://git.openstack.org/cgit/openstack/tripleo-quickstart/tree/config/general_config>`_.
<https://opendev.org/openstack/tripleo-quickstart/src/branch/master/config/general_config>`_.
You may want to run a popular TripleO CI job with a custom set of Tempest
tests and override the default Tempest run. This can be accomplished through
adding the `featureset_overrides` var to zuul job config `vars:` section.
The list of custom featureset_override are defined in `zuul-v3.yaml
<http://git.openstack.org/cgit/openstack-infra/tripleo-ci/tree/playbooks/tripleo-ci/run-v3.yaml>`_.
<https://opendev.org/openstack-infra/tripleo-ci/src/branch/master/playbooks/tripleo-ci/run-v3.yaml>`_.
This setting allows projects to override featureset post deployment configuration.
The overridable settings are:

2
doc/source/ci/ci_primer.rst
View File

@ -82,7 +82,7 @@ we can expect it to be defined in both gate and check.
.. _zuul.d: https://github.com/openstack-infra/tripleo-ci/tree/master/zuul.d
.. _scenario-standalone-jobs: https://github.com/openstack-infra/tripleo-ci/blob/101074b2e804f97880440a3e62351844f390b2f2/zuul.d/standalone-jobs.yaml#L86-L88
.. _openstack-codesearch: http://codesearch.openstack.org/?q=tripleo-ci-centos-7-scenario003-standalone&i=nope&files=&repos=
.. _zuul_builds: http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-scenario003-standalone
.. _zuul_builds: http://zuul.opendev.org/builds?job_name=tripleo-ci-centos-7-scenario003-standalone
Zuul queues - gate vs check
---------------------------

4
doc/source/ci/standalone_scenario_jobs.rst
View File

@ -88,8 +88,8 @@ Finally we use a task in the tripleo-ci-run-test-role_ to pass the scenario
environment file into the standalone deployment command using the standalone
role standalone_custom_env_files_ parameter.
.. _scenario012: https://review.openstack.org/634723
.. _dedicated-featureset: https://review.openstack.org/636355
.. _scenario012: https://review.opendev.org/634723
.. _dedicated-featureset: https://review.opendev.org/636355
.. _standalone-featureset052: https://github.com/openstack/tripleo-quickstart/blob/6585d6320ca4f0c37ae62dfc60fe2eb0cd42647c/config/general_config/featureset052.yml#L2
.. _scenario001-job: https://github.com/openstack-infra/tripleo-ci/blob/1d890565feeeea6ce637cf0384da822926480f07/zuul.d/standalone-jobs.yaml#L376
.. _scenario002-job: https://github.com/openstack-infra/tripleo-ci/blob/1d890565feeeea6ce637cf0384da822926480f07/zuul.d/standalone-jobs.yaml#L401

4
doc/source/contributor/contributions.rst
View File

@ -20,12 +20,12 @@ Contributing to this Documentation
-----------------------------------
|project| User Documentation lives on
`git.openstack.org <http://git.openstack.org/cgit/openstack/tripleo-docs/>`_
`git.opendev.org <https://opendev.org/openstack/tripleo-docs/>`_
and is mirrored on
`GitHub under the OpenStack organization <https://github.com/openstack/tripleo-docs>`_.
Learn `how to contribute into TripleO Docs
<http://git.openstack.org/cgit/openstack/tripleo-docs/tree/README.rst>`_.
<https://opendev.org/openstack/tripleo-docs/src/branch/master/README.rst>`_.
Reporting Bugs
--------------

26
doc/source/contributor/new_developers.rst
View File

@ -31,57 +31,57 @@ speed.
Repositories that are part of TripleO
-------------------------------------
* `tripleo-common <https://git.openstack.org/cgit/openstack/tripleo-common/>`_:
* `tripleo-common <https://opendev.org/openstack/tripleo-common/>`_:
This is intended to be for TripleO libraries of common code including Mistral
workflows and actions. Unfortunately it has become a bit overrun with
unrelated bits. Work is ongoing to clean this up and split this into
separate repositories.
* `tripleo-heat-templates <https://git.openstack.org/cgit/openstack/tripleo-heat-templates>`_:
* `tripleo-heat-templates <https://opendev.org/openstack/tripleo-heat-templates>`_:
This contains all the Heat templates necessary to deploy the overcloud (and
hopefully soon the undercloud as well).
* `python-tripleoclient <https://git.openstack.org/cgit/openstack/python-tripleoclient>`_:
* `python-tripleoclient <https://opendev.org/openstack/python-tripleoclient>`_:
The CLI for deploying TripleO. This contains some logic but remember that we
want to call Mistral actions from here where needed so that the logic can be
shared with the UI.
* `tripleo-docs <https://git.openstack.org/cgit/openstack/tripleo-docs>`_:
* `tripleo-docs <https://opendev.org/openstack/tripleo-docs>`_:
Where these docs are kept.
* `tripleo-image-elements <https://git.openstack.org/cgit/openstack/tripleo-image-elements>`_:
* `tripleo-image-elements <https://opendev.org/openstack/tripleo-image-elements>`_:
Image elements (snippets of puppet that prepare specific parts of the
image) for building the undercloud and overcloud disk images.
* `tripleo-puppet-elements <https://git.openstack.org/cgit/openstack/tripleo-puppet-elements>`_:
* `tripleo-puppet-elements <https://opendev.org/openstack/tripleo-puppet-elements>`_:
Puppet elements used to configure and deploy the overcloud. These
used during installation to set up the services.
* `puppet-tripleo <https://git.openstack.org/cgit/openstack/puppet-tripleo>`_:
* `puppet-tripleo <https://opendev.org/openstack/puppet-tripleo>`_:
Puppet is used to configure the services in TripleO. This repository
contains various puppet modules for doing this.
* `tripleo-quickstart <https://git.openstack.org/cgit/openstack/tripleo-quickstart>`_:
* `tripleo-quickstart <https://opendev.org/openstack/tripleo-quickstart>`_:
Quickstart is an Ansible driven deployment for TripleO used in CI. Most
developers also use this to stand up instances for development as well.
* `tripleo-quickstart-extras <https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras>`_:
* `tripleo-quickstart-extras <https://opendev.org/openstack/tripleo-quickstart-extras>`_:
Extended functionality for tripleo-quickstart allowing for end-to-end
deployment and testing.
* `tripleo-ui <https://git.openstack.org/cgit/openstack/tripleo-ui>`_:
* `tripleo-ui <https://opendev.org/openstack/tripleo-ui>`_:
The web based graphical user interface for deploying TripleO.
* `paunch <https://git.openstack.org/cgit/openstack/paunch>`_:
* `paunch <https://opendev.org/openstack/paunch>`_:
This is a library that is used to deploy containers. It is called from the
Heat templates during installation to deploy our containerized services.
* `kolla <https://git.openstack.org/cgit/openstack/kolla>`_:
* `kolla <https://opendev.org/openstack/kolla>`_:
We use the containers built by the Kolla project for services in TripleO.
Any new containers or additions to existing containers should be submitted
here.
* `diskimage-builder <https://git.openstack.org/cgit/openstack/diskimage-builder>`_:
* `diskimage-builder <https://opendev.org/openstack/diskimage-builder>`_:
Disk image builder is used to build our base images for the TripleO
deployment.

2
doc/source/developer/mistral_workflows/03-creating-new-cli-option.rst
View File

@ -80,5 +80,5 @@ until we receive a message from the Mistral workflow
**tripleo.undercloud_backup.v1.prepare_environment** that indicates if
the invoked workflow ended correctly.
.. _gerrit review: https://review.openstack.org/#/c/466213
.. _gerrit review: https://review.opendev.org/#/c/466213

2
doc/source/developer/mistral_workflows/05-tripleo-environment-variables.rst
View File

@ -22,4 +22,4 @@ For additional testing, you can use the `Python snippet`_ to call
Mistral client from the Undercloud node available in gist.github.com.
.. _Python snippet: https://gist.github.com/ccamacho/354f798102710d165c1f6167eb533caf#file-mistral_client_snippet-py
.. _instack_undercloud/undercloud.py: https://git.openstack.org/cgit/openstack/instack-undercloud/tree/instack_undercloud/undercloud.py
.. _instack_undercloud/undercloud.py: https://opendev.org/openstack/instack-undercloud/src/branch/master/instack_undercloud/undercloud.py

4
doc/source/developer/release.rst
View File

@ -9,7 +9,7 @@ it's suggested to read the OpenStack Release Management guide_.
Most of TripleO projects follows the cycle-trailing_ release model.
The details can be found on the releases repository_.
.. _repository: https://git.openstack.org/cgit/openstack/releases/tree/deliverables
.. _repository: https://opendev.org/openstack/releases/src/branch/master/deliverables
.. _cycle-trailing: https://releases.openstack.org/reference/release_models.html#cycle-trailing
@ -42,7 +42,7 @@ For other projects, there is no need to update anything since the release will b
https://docs.openstack.org/developer/puppet-openstack-guide/releases.html#how-to-release-puppet-modules
.. Note::
TripleO UI requires some specific changes to be released too, see https://review.openstack.org/#/c/460664/
TripleO UI requires some specific changes to be released too, see https://review.opendev.org/#/c/460664/
for an example.
Once this is done, you can submit a patch in openstack/releases and per project create or modify the YAML.

2
doc/source/developer/tht_walkthrough/changes-puppet-tripleo.rst
View File

@ -42,7 +42,7 @@ structure (``manifests/profile/base/time/ntp.pp``) as:
) {
#step assigned for core modules.
#(Check for further referencies about the configuration steps)
#http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/puppet/services/README.rst
#https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/puppet/services/README.rst
if ($step >= 2){
#We will call the NTP puppet class and assign our configuration values.
#If needed additional Puppet packages can be added/installed by using the repo tripleo-puppet-elements

10
doc/source/developer/tht_walkthrough/changes-tht.rst
View File

@ -31,7 +31,7 @@ purpose.
of the base configuration (such as rabbit credentials).
Using a base template in those cases means we don't need to
duplicate that configuration.
Refer to: https://review.openstack.org/#/c/313577/ for further details.
Refer to: https://review.opendev.org/#/c/313577/ for further details.
Also, refer to :ref:`duplicated-parameters` for an use-case description.
Changes list
@ -138,13 +138,13 @@ follows::
THT changes for all the different roles are covered in:
- https://review.openstack.org/#/c/310421/ (tripleo-heat-templates controller)
- https://review.opendev.org/#/c/310421/ (tripleo-heat-templates controller)
- https://review.openstack.org/#/c/330916/ (tripleo-heat-templates compute)
- https://review.opendev.org/#/c/330916/ (tripleo-heat-templates compute)
- https://review.openstack.org/#/c/330921/ (tripleo-heat-templates cephstorage)
- https://review.opendev.org/#/c/330921/ (tripleo-heat-templates cephstorage)
- https://review.openstack.org/#/c/330923/ (tripleo-heat-templates objectstorage)
- https://review.opendev.org/#/c/330923/ (tripleo-heat-templates objectstorage)
.. note::

12
doc/source/developer/tht_walkthrough/introduction.rst
View File

@ -45,22 +45,22 @@ Gerrit patches used in this example
The gerrit patches used to describe this walkthrough are:
- https://review.openstack.org/#/c/310725/ (puppet-tripleo)
- https://review.opendev.org/#/c/310725/ (puppet-tripleo)
- https://review.openstack.org/#/c/310421/ (tripleo-heat-templates controller)
- https://review.opendev.org/#/c/310421/ (tripleo-heat-templates controller)
- https://review.openstack.org/#/c/330916/ (tripleo-heat-templates compute)
- https://review.opendev.org/#/c/330916/ (tripleo-heat-templates compute)
- https://review.openstack.org/#/c/330921/ (tripleo-heat-templates cephstorage)
- https://review.opendev.org/#/c/330921/ (tripleo-heat-templates cephstorage)
- https://review.openstack.org/#/c/330923/ (tripleo-heat-templates objectstorage)
- https://review.opendev.org/#/c/330923/ (tripleo-heat-templates objectstorage)
Change prerequisites
~~~~~~~~~~~~~~~~~~~~~
The controller services are defined and configured via Heat resource chains. In
the proposed patch (https://review.openstack.org/#/c/259568) controller
the proposed patch (https://review.opendev.org/#/c/259568) controller
services will be wired to a new Heat feature that allows it to dynamically include
a set of nested stacks representing individual services via a Heat resource
chain. The current example will use this interface to decompose the controller

4
doc/source/developer/tht_walkthrough/summary.rst
View File

@ -5,9 +5,9 @@ References:
#. https://etherpad.openstack.org/p/tripleo-composable-roles-work
#. https://review.openstack.org/#/c/245804/2/specs/mitaka/composable-services-within-roles.rst
#. https://review.opendev.org/#/c/245804/2/specs/mitaka/composable-services-within-roles.rst
#. https://review.openstack.org/#/q/topic:composable_service
#. https://review.opendev.org/#/q/topic:composable_service
#. https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/template_deploy.html

22
doc/source/developer/tripleoclient_primer.rst
View File

@ -36,13 +36,13 @@ sections. First we see how to identify *where* in the tripleoclient code a given
command is defined, and then *how* the command works, highlighting a recurring
pattern common to all TripleO commands.
.. _python-tripleoclient: https://git.openstack.org/cgit/openstack/python-tripleoclient/
.. _tripleo-common: https://git.openstack.org/cgit/openstack/tripleo-common/
.. _overcloud_containers.yaml: https://git.openstack.org/cgit/openstack/tripleo-common/tree/container-images/overcloud_containers.yaml?id=827af753884e15326863ff2207b2ac95d4ad595b#n1
.. _Kolla: https://git.openstack.org/cgit/openstack/kolla
.. _tripleo-build-containers-centos-7: http://zuul.openstack.org/builds?job_name=tripleo-build-containers-centos-7
.. _build.sh.j2: https://git.openstack.org/cgit/openstack-infra/tripleo-ci/tree/playbooks/tripleo-buildcontainers/templates/build.sh.j2?id=69212e1cd8726396c232b493f1aec79480459666#n5
.. _setup.cfg: https://git.openstack.org/cgit/openstack/python-tripleoclient/tree/setup.cfg?id=73cc43898cfcc8b99ce736f734fc5b514f5bc6e9#n46
.. _python-tripleoclient: https://opendev.org/openstack/python-tripleoclient/
.. _tripleo-common: https://opendev.org/openstack/tripleo-common/
.. _overcloud_containers.yaml: https://opendev.org/openstack/tripleo-common/src/branch/master/container-images/overcloud_containers.yaml?id=827af753884e15326863ff2207b2ac95d4ad595b#n1
.. _Kolla: https://opendev.org/openstack/kolla
.. _tripleo-build-containers-centos-7: http://zuul.opendev.org/builds?job_name=tripleo-build-containers-centos-7
.. _build.sh.j2: https://opendev.org/openstack-infra/tripleo-ci/src/branch/master/playbooks/tripleo-buildcontainers/templates/build.sh.j2?id=69212e1cd8726396c232b493f1aec79480459666#n5
.. _setup.cfg: https://opendev.org/openstack/python-tripleoclient/src/branch/master/setup.cfg?id=73cc43898cfcc8b99ce736f734fc5b514f5bc6e9#n46
TripleO commands: *where*
@ -70,7 +70,7 @@ used in the tripleoclient namespace for this comand. For **overcloud_container_i
defined in a class called **BuildImage** inside the `tripleoclient/v1/container_image.py`_
file.
.. _`tripleoclient/v1/container_image.py`: https://git.openstack.org/cgit/openstack/python-tripleoclient/tree/tripleoclient/v1/container_image.py?id=0132e7d08240d8a9d5839cc4345574d44ec2b278#n100
.. _`tripleoclient/v1/container_image.py`: https://opendev.org/openstack/python-tripleoclient/src/branch/master/tripleoclient/v1/container_image.py?id=0132e7d08240d8a9d5839cc4345574d44ec2b278#n100
TripleO commands: *how*
-----------------------
@ -131,6 +131,6 @@ python namespace to find the definition of **build_images** in the
cmd = ['kolla-build']
...
.. _get_parser: https://git.openstack.org/cgit/openstack/python-tripleoclient/tree/tripleoclient/v1/container_image.py?id=0132e7d08240d8a9d5839cc4345574d44ec2b278#n119
.. _take_action: https://git.openstack.org/cgit/openstack/python-tripleoclient/tree/tripleoclient/v1/container_image.py?id=0132e7d08240d8a9d5839cc4345574d44ec2b278#n184
.. _`tripleo_common/image/kolla_builder.py`: https://git.openstack.org/cgit/openstack/tripleo-common/tree/tripleo_common/image/kolla_builder.py?id=3db41939a370ef3bbd2c6b60ca24e6e8e4b6e30a#n441
.. _get_parser: https://opendev.org/openstack/python-tripleoclient/src/branch/master/tripleoclient/v1/container_image.py?id=0132e7d08240d8a9d5839cc4345574d44ec2b278#n119
.. _take_action: https://opendev.org/openstack/python-tripleoclient/src/branch/master/tripleoclient/v1/container_image.py?id=0132e7d08240d8a9d5839cc4345574d44ec2b278#n184
.. _`tripleo_common/image/kolla_builder.py`: https://opendev.org/openstack/tripleo-common/src/branch/master/tripleo_common/image/kolla_builder.py?id=3db41939a370ef3bbd2c6b60ca24e6e8e4b6e30a#n441

2
doc/source/install/advanced_deployment/baremetal_overcloud.rst
View File

@ -1195,7 +1195,7 @@ Assuming an external network is available the server can then be allocated a flo
openstack server add floating ip test1 <IP>
.. _IronicConductor role shipped with TripleO: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/plain/roles/IronicConductor.yaml
.. _IronicConductor role shipped with TripleO: https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/roles/IronicConductor.yaml
.. _driver configuration guide: https://docs.openstack.org/ironic/latest/install/enabling-drivers.html
.. _driver-specific documentation: https://docs.openstack.org/ironic/latest/admin/drivers.html
.. _bare metal flavor documentation: https://docs.openstack.org/ironic/latest/install/configure-nova-flavors.html

2
doc/source/install/advanced_deployment/composable_services.rst
View File

@ -55,4 +55,4 @@ The same approach can be used for any role.
and thus control-plane services on this role may present problems during
major upgrades between releases.
.. _tripleo-heat-templates: https://git.openstack.org/openstack/tripleo-heat-templates
.. _tripleo-heat-templates: https://opendev.org/openstack/tripleo-heat-templates

4
doc/source/install/advanced_deployment/custom_networks.rst
View File

@ -119,6 +119,6 @@ The steps to define your custom networks are:
modify the ``network_data.yaml`` file in place, then deploy via
``--templates <copy of tht>``.
.. _tripleo-heat-templates: https://git.openstack.org/cgit/openstack/tripleo-heat-templates
.. _network_data.yaml: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/network_data.yaml
.. _tripleo-heat-templates: https://opendev.org/openstack/tripleo-heat-templates
.. _network_data.yaml: https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/network_data.yaml
.. _jinja2: http://jinja.pocoo.org/docs/dev/

4
doc/source/install/advanced_deployment/custom_roles.rst
View File

@ -63,7 +63,7 @@ The steps to define your custom roles configuration are:
2. Create a new role file with your custom role.
Additional details about the format for the roles file can be found in the
`README.rst <http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/roles/README.rst>`_
`README.rst <https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/roles/README.rst>`_
in the roles/ directory from `tripleo-heat-templates`. The filename should
match the name of the role. For example if adding a new role named `Galera`,
the role file name should be `Galera.yaml`. The file should at least contain
@ -137,5 +137,5 @@ cluster::
instead.
.. _tripleo-heat-templates: https://git.openstack.org/openstack/tripleo-heat-templates
.. _tripleo-heat-templates: https://opendev.org/openstack/tripleo-heat-templates
.. _jinja2: http://jinja.pocoo.org/docs/dev/

2
doc/source/install/advanced_deployment/extra_config.rst
View File

@ -112,7 +112,7 @@ SSH keys by accessing the nova metadata server, see
`/usr/share/openstack-tripleo-heat-templates/firstboot/userdata_example.yaml`
on the undercloud node or the tripleo-heat-templates_ repo.
.. _tripleo-heat-templates: https://git.openstack.org/openstack/tripleo-heat-templates
.. _tripleo-heat-templates: https://opendev.org/openstack/tripleo-heat-templates
Per-node extra configuration
----------------------------

2
doc/source/install/basic_deployment/os_tempest.rst
View File

@ -145,7 +145,7 @@ variables for controlling behaviour of `os_tempest`:
It runs `tempest.yaml` playbook which sets the rest of the `os_tempest`
variables needed for execution on top of an environment deployed by one of the
TripleO CI jobs. The
`content of the playbook can be seen here <https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/playbooks/tempest.yml>`_.
`content of the playbook can be seen here <https://opendev.org/openstack/tripleo-quickstart-extras/src/branch/master/playbooks/tempest.yml>`_.
If you want to set some of the variables mentioned above differently you need
to override them by adding those variables to your job definition.

4
doc/source/install/basic_deployment/tempest.rst
View File

@ -8,7 +8,7 @@ other specific tests useful in validating an OpenStack deployment.
Current State of Tempest
------------------------
Source code : https://git.openstack.org/cgit/openstack/tempest/
Source code : https://opendev.org/openstack/tempest/
Tempest Version release wise:
+++++++++++++++++++++++++++++
@ -173,7 +173,7 @@ configuration, the following is the default::
.. note::
Here is the list of
`validate-tempest role variables <http://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/tree/roles/validate-tempest/README.md>`_
`validate-tempest role variables <https://opendev.org/openstack/tripleo-quickstart-extras/src/branch/master/roles/validate-tempest/README.md>`_
which can be modified using extra-vars.

40
doc/source/install/basic_deployment/tempest_plugins.rst
View File

@ -5,80 +5,80 @@ Below is the detailed list of openstack services wise tempest plugins.
* Keystone
* RPM package name: python2-keystone-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/keystone-tempest-plugin
* Source Code: https://opendev.org/openstack/keystone-tempest-plugin
* Neutron
* RPM package name: python2-neutron-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/neutron-tempest-plugin
* Source Code: https://opendev.org/openstack/neutron-tempest-plugin
* Designate
* RPM package name: python2-designate-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/designate-tempest-plugin
* Source Code: https://opendev.org/openstack/designate-tempest-plugin
* Octavia
* RPM package name: python2-octavia-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/octavia-tempest-plugin
* Source Code: https://opendev.org/openstack/octavia-tempest-plugin
* Horizon
* RPM package name: python2-horizon-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/tempest-horizon
* Source Code: https://opendev.org/openstack/tempest-horizon
* Networking-l2gw
* RPM package: python2-networking-l2gw-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/networking-l2gw-tempest-plugin
* Source Code: https://opendev.org/openstack/networking-l2gw-tempest-plugin
* Kuryr
* RPM package: python2-kuryr-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/kuryr-tempest-plugin
* Source Code: https://opendev.org/openstack/kuryr-tempest-plugin
* patrole
* RPM package: python2-patrole-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/patrole
* Source Code: https://opendev.org/openstack/patrole
* Barbican
* RPM Package: python2-barbican-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/barbican-tempest-plugin
* Source Code: https://opendev.org/openstack/barbican-tempest-plugin
* nova-join
* RPM Package: python2-novajoin-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/novajoin-tempest-plugin
* Source Code: https://opendev.org/openstack/novajoin-tempest-plugin
* Sahara
* RPM package: python2-sahara-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/sahara-tests
* Source Code: https://opendev.org/openstack/sahara-tests
* zaqar
* RPM Package: python2-zaqar-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/zaqar-tempest-plugin
* Source Code: https://opendev.org/openstack/zaqar-tempest-plugin
* Heat
* RPM Package: python2-heat-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/heat-tempest-plugin
* Source Code: https://opendev.org/openstack/heat-tempest-plugin
* Mistral
* RPM package: python2-mistral-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/mistral-tempest-plugin
* Source Code: https://opendev.org/openstack/mistral-tempest-plugin
* TripleO-Common
* RPM package: python2-tripleo-common-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/tripleo-common-tempest-plugin
* Source Code: https://opendev.org/openstack/tripleo-common-tempest-plugin
* Manila
* RPM Package: python2-manila-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/manila-tempest-plugin
* Source Code: https://opendev.org/openstack/manila-tempest-plugin
* Telemetry
* RPM Package: python2-telemetry-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/telemetry-tempest-plugin
* Source Code: https://opendev.org/openstack/telemetry-tempest-plugin
* Cinder
* RPM package: python2-cinder-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/cinder-tempest-plugin
* Source Code: https://opendev.org/openstack/cinder-tempest-plugin
* Ironic
* RPM Package: python2-ironic-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/ironic-tempest-plugin
* Source Code: https://opendev.org/openstack/ironic-tempest-plugin
* EC2-API
* RPM Package: python2-ec2api-tests-tempest
* Source Code: http://git.openstack.org/cgit/openstack/ec2api-tempest-plugin
* Source Code: https://opendev.org/openstack/ec2api-tempest-plugin

2
doc/source/install/containers_deployment/3rd_party.rst
View File

@ -107,7 +107,7 @@ The `TripleO Heat Templates`_ repo is where most of the logic resides in the for
of heat templates. These templates define each service, the containers'
configuration and the initialization or post-execution operations.
.. _TripleO Heat Templates: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
.. _TripleO Heat Templates: https://opendev.org/openstack/tripleo-heat-templates
The docker templates can be found under the `docker` sub directory in the
`tripleo-heat-templates` root. The services files are under the

2
doc/source/install/containers_deployment/architecture.rst
View File

@ -113,7 +113,7 @@ The `TripleO Heat Templates`_ repo is where most of the logic resides in the for
of heat templates. These templates define each service, the containers'
configuration and the initialization or post-execution operations.
.. _TripleO Heat Templates: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
.. _TripleO Heat Templates: https://opendev.org/openstack/tripleo-heat-templates
Understanding container related files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1
doc/source/install/environments/baremetal.rst
View File

@ -142,7 +142,6 @@ the process, the validations will be run by the undercloud processes.
Refer to the Ansible section for running directly the validations
over baremetal nodes `validations_no_undercloud`_.
Configuration Files
^^^^^^^^^^^^^^^^^^^

2
doc/source/install/environments/virtualbmc.rst
View File

@ -137,6 +137,6 @@ To validate after updating deployment and verify everything is populated properl
openstack baremetal node validate $NODE_UUID_OR_NAME | grep power
.. _VirtualBMC: https://git.openstack.org/cgit/openstack/virtualbmc
.. _VirtualBMC: https://opendev.org/openstack/virtualbmc
.. _IPMI: https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface
.. _BMC: https://en.wikipedia.org/wiki/Baseboard_management_controller

44
doc/source/install/introduction/components.rst
View File

@ -43,7 +43,7 @@ diskimage-builder is an image building tool. It is used by
**How to contribute**
See the diskimage-builder `README.rst
<https://git.openstack.org/cgit/openstack/diskimage-builder/tree/README.rst>`_
<https://opendev.org/openstack/diskimage-builder/src/branch/master/README.rst>`_
for a further explanation of the tooling. Submit your changes via
OpenStack Gerrit (see `OpenStack Developer's Guide
<http://docs.openstack.org/infra/manual/developers.html>`_).
@ -52,7 +52,7 @@ OpenStack Gerrit (see `OpenStack Developer's Guide
* Upstream Project Documentation: http://docs.openstack.org/developer/diskimage-builder/
* Bugs: https://bugs.launchpad.net/diskimage-builder
* Git repository: https://git.openstack.org/cgit/openstack/diskimage-builder/
* Git repository: https://opendev.org/openstack/diskimage-builder/
dib-utils
@ -68,7 +68,7 @@ Submit your changes via OpenStack Gerrit (see `OpenStack Developer's Guide
**Useful links**
* Bugs: https://bugs.launchpad.net/diskimage-builder
* Git repository: https://git.openstack.org/cgit/openstack/dib-utils/
* Git repository: https://opendev.org/openstack/dib-utils/
os-\*-config
@ -100,10 +100,10 @@ development environment. Submit your changes via OpenStack Gerrit (see
* Git repositories:
* os-collect-config: https://git.openstack.org/cgit/openstack/os-collect-config
* os-refresh-config https://git.openstack.org/cgit/openstack/os-refresh-config
* os-apply-config https://git.openstack.org/cgit/openstack/os-apply-config
* os-net-config https://git.openstack.org/cgit/openstack/os-net-config
* os-collect-config: https://opendev.org/openstack/os-collect-config
* os-refresh-config https://opendev.org/openstack/os-refresh-config
* os-apply-config https://opendev.org/openstack/os-apply-config
* os-net-config https://opendev.org/openstack/os-net-config
tripleo-image-elements
^^^^^^^^^^^^^^^^^^^^^^
@ -119,7 +119,7 @@ Submit your changes via OpenStack Gerrit (see
**Useful links**
* Git repository: https://git.openstack.org/cgit/openstack/tripleo-image-elements
* Git repository: https://opendev.org/openstack/tripleo-image-elements
Installer
@ -144,7 +144,7 @@ Submit your changes via OpenStack Gerrit (see
**Useful links**
* Git repository: https://git.openstack.org/cgit/openstack/instack
* Git repository: https://opendev.org/openstack/instack
* Bugs: https://launchpad.net/tripleo
instack-undercloud
@ -160,7 +160,7 @@ Submit your changes via OpenStack Gerrit (see
**Useful links**
* Git repository: https://git.openstack.org/cgit/openstack/instack-undercloud
* Git repository: https://opendev.org/openstack/instack-undercloud
* Bugs: https://launchpad.net/tripleo
tripleo-incubator
@ -176,7 +176,7 @@ Submit your changes via OpenStack Gerrit (see
**Useful links**
* Documentation: http://docs.openstack.org/developer/tripleo-incubator/index.html
* Git repository: https://git.openstack.org/cgit/openstack/tripleo-incubator
* Git repository: https://opendev.org/openstack/tripleo-incubator
* Bugs: https://launchpad.net/tripleo
@ -243,7 +243,7 @@ development environment in a similar way to Ironic.
**Useful links**
* Source: https://git.openstack.org/cgit/openstack/virtualbmc
* Source: https://opendev.org/openstack/virtualbmc
* Bugs: https://bugs.launchpad.net/virtualbmc
@ -287,7 +287,7 @@ producing disk images ready to be configured by Puppet via Heat.
**Useful links**
* Upstream Project: https://git.openstack.org/cgit/openstack/heat-templates
* Upstream Project: https://opendev.org/openstack/heat-templates
* Bugs: https://bugs.launchpad.net/heat-templates
* Blueprints: https://blueprints.launchpad.net/heat-templates
@ -308,7 +308,7 @@ are deployed via Heat.
**Useful links**
* Upstream Project: https://git.openstack.org/cgit/openstack/tripleo-heat-templates
* Upstream Project: https://opendev.org/openstack/tripleo-heat-templates
* Bugs: https://bugs.launchpad.net/tripleo
* Blueprints: https://blueprints.launchpad.net/tripleo
@ -327,7 +327,7 @@ nova provides a cloud computing fabric controller.
**Useful links**
* Git repository: https://git.openstack.org/cgit/openstack/nova
* Git repository: https://opendev.org/openstack/nova
* Bugs: https://bugs.launchpad.net/nova
* Blueprints: https://blueprints.launchpad.net/nova
@ -368,7 +368,7 @@ for Puppet-enabled images.
**Useful links**
* Upstream Project: https://git.openstack.org/cgit/openstack/tripleo-puppet-elements
* Upstream Project: https://opendev.org/openstack/tripleo-puppet-elements
* Bugs: https://bugs.launchpad.net/tripleo
* Blueprints: https://blueprints.launchpad.net/tripleo
@ -396,7 +396,7 @@ command with consistent syntax and behaviour.
**Useful links**
* Upstream Project: http://git.openstack.org/cgit/openstack/python-openstackclient
* Upstream Project: https://opendev.org/openstack/python-openstackclient
* Bugs: https://bugs.launchpad.net/python-openstackclient
* Blueprints: https://blueprints.launchpad.net/python-openstackclient
* Human interface guide: http://docs.openstack.org/developer/python-openstackclient/humaninterfaceguide.html
@ -412,13 +412,13 @@ like node introspection, overcloud image building and uploading, etc.
* python-tripleoclient uses `tox <https://tox.readthedocs.org/en/latest/>`_
to manage the development environment, see the
`python-tripleoclient documentation
<http://git.openstack.org/cgit/openstack/python-tripleoclient/tree/CONTRIBUTING.rst>`_
<https://opendev.org/openstack/python-tripleoclient/src/branch/master/CONTRIBUTING.rst>`_
for details. Submit your changes via
`Gerrit <https://review.openstack.org/#/q/project:openstack/python-tripleoclient,n,z>`_.
`Gerrit <https://review.opendev.org/#/q/project:openstack/python-tripleoclient,n,z>`_.
**Useful links**
* Project: https://git.openstack.org/cgit/openstack/python-tripleoclient
* Project: https://opendev.org/openstack/python-tripleoclient
..
<GLOBAL_LINKS>
@ -432,7 +432,7 @@ TripleO UI is the web interface for TripleO.
**How to contribute**
* See the `documentation <http://git.openstack.org/cgit/openstack/tripleo-ui/tree/README.md>`_
* See the `documentation <https://opendev.org/openstack/tripleo-ui/src/branch/master/README.md>`_
for details.
@ -448,7 +448,7 @@ Pre and post-deployment validations for the deployment workflow.
**Useful links**
* Upstream Project: http://git.openstack.org/cgit/openstack/tripleo-validations/
* Upstream Project: https://opendev.org/openstack/tripleo-validations/
* Bugs: https://bugs.launchpad.net/tripleo/+bugs?field.tag=validations
* Documentation for individual validations: http://docs.openstack.org/developer/tripleo-validations/readme.html#existing-validations

4
doc/source/upgrade/developer/upgrades/fast_fw_upgrade.rst
View File

@ -74,7 +74,7 @@ to the equivalent `docker templates`_ for the Heat resource registry.
.. _Minor update: https://docs.openstack.org/tripleo-docs/latest/install/post_deployment/package_update.html
.. _upgrade_steps_playbook: https://github.com/openstack/tripleo-heat-templates/blob/82f128f15b1b1eb7bf6ac7df0c6d01e5619309eb/common/deploy-steps.j2#L528
.. _deploy_steps_playbook: https://github.com/openstack/tripleo-heat-templates/blob/82f128f15b1b1eb7bf6ac7df0c6d01e5619309eb/common/deploy-steps.j2#L382
.. _fast_forward_upgrade_playbook: https://review.openstack.org/#/c/499221/20/common/deploy-steps.j2@541
.. _fast_forward_upgrade_playbook: https://review.opendev.org/#/c/499221/20/common/deploy-steps.j2@541
.. _docker configuration and environment: https://docs.openstack.org/tripleo-docs/latest/install/containers_deployment/overcloud.html#preparing-the-environment
.. _docker templates: https://github.com/openstack/tripleo-heat-templates/blob/750fa306ce41c949928d5a3a7253aff99dd1af8f/environments/docker.yaml#L7-L58
.. _ceph-ansible: https://github.com/ceph/ceph-ansible
@ -98,7 +98,7 @@ config-download_ mechanism and written to disk as an ansible playbook.
The *fast_forward_upgrade_tasks* defined for a given service can use the
**step** and **release** variables to specify when a given task should be
executed. At a high level the fast_forward_upgrade_playbook consists of two
loops - there is a very good explanation in `/#/c/499221 <https://review.openstack.org/#/c/499221/>`_
loops - there is a very good explanation in `/#/c/499221 <https://review.opendev.org/#/c/499221/>`_
commit message, but an outer loop for the release (first Ocata tasks then Pike
tasks) and then an inner loop for the steps within each release.

2
doc/source/upgrade/developer/upgrades/links.rst
View File

@ -12,7 +12,7 @@
.. _tripleo-upgrade:
https://github.com/redhat-openstack/tripleo-upgrade
.. _integrate:
https://review.openstack.org/#/q/topic:link_tripleo_upgrade
https://review.opendev.org/#/q/topic:link_tripleo_upgrade
.. _James Slagle:
http://lists.openstack.org/pipermail/openstack-dev/2017-February/112993.html
.. _traas:

14
doc/source/upgrade/developer/upgrades/major_upgrade.rst
View File

@ -304,8 +304,8 @@ example:
# backup tht in case you want to revert - or just yum re-install ;)
sudo cp -r /usr/share/openstack-tripleo-heat-templates \
/usr/share/openstack-tripleo-heat-templates.ORIG
# Apply patch from gerrit e.g. https://review.openstack.org/#/c/563073/
curl -4sSL 'https://review.openstack.org/changes/563073/revisions/current/patch?download' | \
# Apply patch from gerrit e.g. https://review.opendev.org/#/c/563073/
curl -4sSL 'https://review.opendev.org/changes/563073/revisions/current/patch?download' | \
base64 -d | \
sudo patch -d /usr/share/openstack-tripleo-heat-templates/ -p1
@ -336,8 +336,8 @@ Patching python-tripleoclient:
git clone https://github.com/openstack/python-tripleoclient.git -b stable/queens ~/python-tripleoclient
pushd ~/python-tripleoclient
# Apply patches from gerrit e.g. https://review.openstack.org/#/c/564267
curl "https://review.openstack.org/changes/564267/revisions/current/patch" | \
# Apply patches from gerrit e.g. https://review.opendev.org/#/c/564267
curl "https://review.opendev.org/changes/564267/revisions/current/patch" | \
base64 --decode > /home/stack/"564267.patch"
patch -N -p1 -b -z .first < /home/stack/564267.patch
# Remove current version and re-install
@ -358,8 +358,8 @@ Patching tripleo-common:
# tripleo-common - clone from source, patch from gerrit and install
git clone https://github.com/openstack/tripleo-common -b stable/queens
pushd ~/tripleo-common
# Apply patches from gerrit e.g. https://review.openstack.org/#/c/562995
curl "https://review.openstack.org/changes/562995/revisions/current/patch" | \
# Apply patches from gerrit e.g. https://review.opendev.org/#/c/562995
curl "https://review.opendev.org/changes/562995/revisions/current/patch" | \
base64 --decode > /home/stack/"562995.patch"
patch -N -p1 -b -z .first < /home/stack/562995.patch
# Remove current version and re install
@ -383,4 +383,4 @@ package_update.yaml and so that is what we need to update here:
sudo systemctl restart openstack-mistral-executor.service
.. _rabbitmq_upgrade_tasks: https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/rabbitmq/rabbitmq-messaging-rpc-pacemaker-puppet.yaml#L305
.. _562995: https://review.openstack.org/#/c/562995
.. _562995: https://review.opendev.org/#/c/562995

2
doc/source/upgrade/developer/upgrades/minor_update.rst
View File

@ -150,7 +150,7 @@ providing these outputs in your composable service template:
* ``post_update_tasks`` -- these are executed after deployment tasks on
the node being updated.
.. _Paunch: https://git.openstack.org/cgit/openstack/paunch/tree/README.rst
.. _Paunch: https://opendev.org/openstack/paunch/src/branch/master/README.rst
Update tasks are generally meant to bring the service into a stopped
state (sometimes with pre-fetched new images, this is necessary for

4
doc/source/upgrade/fast_forward_upgrade.rst
View File

@ -104,7 +104,7 @@ performed.
.. code-block:: bash
git clone -b stable/newton \
https://git.openstack.org/openstack/tripleo-heat-templates tripleo-heat-templates-newton
https://git.opendev.org/openstack/tripleo-heat-templates tripleo-heat-templates-newton
3. Use a new `plan-environment.yaml` file. As undercloud CLI calls have been
upgraded, they will request that file. It needs to be on
@ -175,7 +175,7 @@ The Queens upgrade workflow essentially consists of the following steps:
Finally run a heat stack update, unsetting any upgrade specific variables
and leaving the heat stack in a healthy state for future updates.
.. _queens-upgrade-dev-docs: https://docs.openstack.org/tripleo-docs/latest/install/developer/upgrades/major_upgrade.html # WIP @ https://review.openstack.org/#/c/569443/
.. _queens-upgrade-dev-docs: https://docs.openstack.org/tripleo-docs/latest/install/developer/upgrades/major_upgrade.html # WIP @ https://review.opendev.org/#/c/569443/
Prepare your environment - Get container images
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2
doc/source/upgrade/major_upgrade.rst
View File

@ -68,7 +68,7 @@ The upgrade workflow essentially consists of the following steps:
Detailed infromation and pointers can be found in the relevant the
queens-upgrade-dev-docs_.
.. _queens-upgrade-dev-docs: https://docs.openstack.org/tripleo-docs/latest/install/developer/upgrades/major_upgrade.html # WIP @ https://review.openstack.org/#/c/569443/
.. _queens-upgrade-dev-docs: https://docs.openstack.org/tripleo-docs/latest/install/developer/upgrades/major_upgrade.html # WIP @ https://review.opendev.org/#/c/569443/
Prepare your environment files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~