From fd9f1540ce3eb627f9e58924fa85d461fb06b977 Mon Sep 17 00:00:00 2001 From: gujin Date: Mon, 27 May 2019 13:52:02 +0800 Subject: [PATCH] Replace git.openstack.org URLs with opendev.org URLs 1. Replace git.openstack.org URLs with opendev.org URLs 2. Remove unncessary "==" Change-Id: Ib2b91a6826bc7a4c72e30dfcdf1c34295a396407 --- README.rst | 4 ++-- specs/newton/template.rst | 2 +- specs/queens/configuration-files-validation.rst | 4 ++-- specs/rocky/alternative-engine-z3.rst | 4 ++-- specs/template.rst | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/README.rst b/README.rst index 1e7eacf..6bc089a 100644 --- a/README.rst +++ b/README.rst @@ -7,9 +7,9 @@ Team and repository tags .. Change things from this point on -================================== +================================= OpenStack Congress Specifications -================================== +================================= This git repository is used to hold approved design specifications for additions to the Congress project. Reviews of the specs are done in gerrit, using a similar diff --git a/specs/newton/template.rst b/specs/newton/template.rst index 8c693e5..a4f396d 100644 --- a/specs/newton/template.rst +++ b/specs/newton/template.rst @@ -158,7 +158,7 @@ Each API method which is either added or changed should have the following think about when defining their policy. Example JSON schema definitions can be found in the Nova tree -http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 +https://opendev.org/openstack/nova/src/branch/master/nova/api/openstack/compute/schemas Note that the schema should be defined as restrictively as possible. Parameters which are required should be marked as such and diff --git a/specs/queens/configuration-files-validation.rst b/specs/queens/configuration-files-validation.rst index 5615dab..8349501 100644 --- a/specs/queens/configuration-files-validation.rst +++ b/specs/queens/configuration-files-validation.rst @@ -4,9 +4,9 @@ http://creativecommons.org/licenses/by/3.0/legalcode -========================================== +======================================== OpenStack Configuration Files Validation -========================================== +======================================== https://blueprints.launchpad.net/congress/+spec/configuration-files-validation diff --git a/specs/rocky/alternative-engine-z3.rst b/specs/rocky/alternative-engine-z3.rst index 815b0b8..ca97b54 100644 --- a/specs/rocky/alternative-engine-z3.rst +++ b/specs/rocky/alternative-engine-z3.rst @@ -4,9 +4,9 @@ http://creativecommons.org/licenses/by/3.0/legalcode -========================================== +=================================== Z3 as an alternative Datalog engine -========================================== +=================================== https://blueprints.launchpad.net/congress/+spec/alternative-engine-z3 diff --git a/specs/template.rst b/specs/template.rst index 8c693e5..a4f396d 100644 --- a/specs/template.rst +++ b/specs/template.rst @@ -158,7 +158,7 @@ Each API method which is either added or changed should have the following think about when defining their policy. Example JSON schema definitions can be found in the Nova tree -http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/v3 +https://opendev.org/openstack/nova/src/branch/master/nova/api/openstack/compute/schemas Note that the schema should be defined as restrictively as possible. Parameters which are required should be marked as such and