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
This commit is contained in:
gujin 2019-05-27 13:52:02 +08:00
parent 531fc152ee
commit fd9f1540ce
5 changed files with 8 additions and 8 deletions

View File

@ -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

View File

@ -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

View File

@ -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

View File

@ -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

View File

@ -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