From 087efe1a96c23a1f199a513245f6f1a717947699 Mon Sep 17 00:00:00 2001 From: zhulingjie Date: Tue, 23 Apr 2019 16:59:45 +0800 Subject: [PATCH] Replace git.openstack.org URLs with opendev.org URLs Change-Id: I76d9981c4d0f437f72a442f14c2b2f60e00b4dfc --- doc/source/developing_guides/rally_on_gates.rst | 6 +++--- doc/source/operating_guides/upgrades_guide.rst | 2 +- heat/tests/test_provider_template.py | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/source/developing_guides/rally_on_gates.rst b/doc/source/developing_guides/rally_on_gates.rst index 5909fe7acf..61fe237d35 100644 --- a/doc/source/developing_guides/rally_on_gates.rst +++ b/doc/source/developing_guides/rally_on_gates.rst @@ -57,7 +57,7 @@ Check performance or how to detect regression The easiest way of using Rally is to execute already existing scenarios. One of the examples is presented in patch -https://review.openstack.org/#/c/279450/ . In this patch was executed scenario +https://review.opendev.org/#/c/279450/ . In this patch was executed scenario already existing in Rally ``HeatStacks.create_and_delete_stack``. During executing this scenario Rally creates and then, when stack is created, delete Heat stack. All existing scenarios can be found here: @@ -94,7 +94,7 @@ is disabled (e.g. Patch Set 7). The follow results were gotten: In the next patch set (Patch Set 8) was updated by adding Depends-On reference to commit message. It let to execute the same test with patch for devstack, -which turns on caching (https://review.openstack.org/#/c/279400/). +which turns on caching (https://review.opendev.org/#/c/279400/). The results for this case were: +------------------+----------+----------+----------+--------+------+ @@ -130,7 +130,7 @@ Compare output API performance Another example of using Rally job is writing custom Rally scenarios in Heat repository. There is an example of this is presented on review: -https://review.openstack.org/#/c/270225/ +https://review.opendev.org/#/c/270225/ It's similar on the first example, but requires more Rally specific coding. New tasks in ``heat-fakevirt.yaml`` use undefined in Rally repository diff --git a/doc/source/operating_guides/upgrades_guide.rst b/doc/source/operating_guides/upgrades_guide.rst index 9d13cad994..e1dfa08253 100644 --- a/doc/source/operating_guides/upgrades_guide.rst +++ b/doc/source/operating_guides/upgrades_guide.rst @@ -153,6 +153,6 @@ References .. _cold-upgrades: https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html -.. _spec about rolling upgrades: https://review.openstack.org/#/c/407989/ +.. _spec about rolling upgrades: https://review.opendev.org/#/c/407989/ .. _RabbitMQ: http://www.rabbitmq.com/management.html diff --git a/heat/tests/test_provider_template.py b/heat/tests/test_provider_template.py index a1f7060f4c..7f56564b5e 100644 --- a/heat/tests/test_provider_template.py +++ b/heat/tests/test_provider_template.py @@ -739,7 +739,7 @@ class ProviderTemplateTest(common.HeatTestCase): """Test that templates are registered correctly. Test that templates persisted in the database prior to - https://review.openstack.org/#/c/79953/1 are registered correctly. + https://review.opendev.org/#/c/79953/1 are registered correctly. """ env = {'resource_registry': {'http://example.com/test.template': None, 'resources': {}}}