Rename review.openstack.org to review.opendev.org

There are many references to review.openstack.org, and while the
redirect should work, we can also go ahead and fix them.

Change-Id: I0d46b1a4e00c1775ea5e38d39e87bed99f6bbb2e

doc/source/reference/process.rst

@@ -185,8 +185,8 @@ Final Library Release (week before Milestone-3)
 
 #. Update the feature list and allowed stable branch names in
    devstack-gate for the new stable branch. For
-   example, https://review.openstack.org/362435 and
-   https://review.openstack.org/363084
+   example, https://review.opendev.org/362435 and
+   https://review.opendev.org/363084
 
 #. Allow the ``stable/$series`` branch to be requested with each library final
    release if they know they are ready. Do not require branching at this point
@@ -317,13 +317,13 @@ RC1 week
    projects, devstack-gate and tempest, in the tempest repo. Configure tempest
    to run them on all changes, voting. Configure tempest to run them as
    periodic bitrot jobs as well. All this can be done in one tempest patch,
-   for example, see https://review.openstack.org/521888.
+   for example, see https://review.opendev.org/521888.
    Configure devstack-gate to run the new jobs in check pipeline only,
-   non-voting, for example see https://review.openstack.org/545144.
+   non-voting, for example see https://review.opendev.org/545144.
 
 #. Remind the QA PTL to add the new branch to the list of branches in the
    periodic-stable job templates in openstack-zuul-jobs. For example, see
-   https://review.openstack.org/545268/.
+   https://review.opendev.org/545268/.
 
 Between RC1 and Final
 =====================
@@ -412,7 +412,7 @@ Final Release
 
 #. Mark series as released on releases.o.o, by updating doc/source/index.rst
    and doc/source/$series/index.rst.
-   See https://review.openstack.org/#/c/381006 for an example.
+   See https://review.opendev.org/#/c/381006 for an example.
 
    .. note::
 

doc/source/reference/reviewer_guide.rst

@@ -27,7 +27,7 @@ development work is going to happen.
 
 For the stable series we have an arrangement with the
 `stable-maint-core
-<https://review.openstack.org/#/admin/groups/530,members>`_ team that
+<https://review.opendev.org/#/admin/groups/530,members>`_ team that
 if a deliverable has the ``stable:follows-policy`` tag we don't
 approve it until they have had a chance to review it (usually the
 Monday after the request is submitted). Releases for deliverables that

doc/source/reference/using.rst

@@ -71,7 +71,7 @@ repository.
      version to fix the target branch, e.g. stable/juno, but don't
      increment the minor version to avoid it being used in a different
      branch, like stable/kilo.  Someone from the `stable-maint-core
-     <https://review.openstack.org/#/admin/groups/530,members>`_ team
+     <https://review.opendev.org/#/admin/groups/530,members>`_ team
      should +1 a change like this before it's approved.
 
 * Do not increment version numbers artificially to maintain

openstack_releases/cmds/find_gerrit_acl_issues.py

@@ -78,7 +78,7 @@ class GerritClient(object):
         # strip off first few chars because 'the JSON response body starts with
         # a magic prefix line that must be stripped before feeding the rest of
         # the response body to a JSON parser'
-        # https://review.openstack.org/Documentation/rest-api.html
+        # https://review.opendev.org/Documentation/rest-api.html
         # print(response.text)
         return json.loads(response.text[5:])
 

tools/aclmanager.py

@@ -35,7 +35,7 @@ from openstack_releases import deliverable
 # https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
 urllib3.disable_warnings()
 
-GERRIT_URL = 'https://review.openstack.org/'
+GERRIT_URL = 'https://review.opendev.org/'
 
 EXCEPTIONS = ['openstack/release-test']
 

watched_queries.yml

@@ -21,7 +21,7 @@ template: |
   [{status}] {subject}
       Updated: {updated}
       Topic: {topic}
-      https://review.openstack.org/{_number}
+      https://review.opendev.org/{_number}
 
 # The query items need a title, to be displayed above the output, and
 # a query string. The query string can include {branch} and {project},