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/kilo/horizon-create-policies.rst b/specs/kilo/horizon-create-policies.rst index 7bee63d..f0d6cb4 100644 --- a/specs/kilo/horizon-create-policies.rst +++ b/specs/kilo/horizon-create-policies.rst @@ -160,7 +160,7 @@ References ========== Datalog Policy Language: -https://github.com/stackforge/congress/blob/master/doc/source/policy.rst#2-datalog-policy-language +https://opendev.org/stackforge/congress/blob/master/doc/source/policy.rst#2-datalog-policy-language Node-RED: http://nodered.org diff --git a/specs/kilo/horizon-datasource-status.rst b/specs/kilo/horizon-datasource-status.rst index 57d901f..432e158 100644 --- a/specs/kilo/horizon-datasource-status.rst +++ b/specs/kilo/horizon-datasource-status.rst @@ -142,4 +142,4 @@ none References ========== -https://github.com/stackforge/python-congressclient +https://opendev.org/stackforge/python-congressclient diff --git a/specs/kilo/horizon-integration.rst b/specs/kilo/horizon-integration.rst index f94e095..03274bd 100644 --- a/specs/kilo/horizon-integration.rst +++ b/specs/kilo/horizon-integration.rst @@ -188,4 +188,4 @@ Document the screenflow. References ========== -https://github.com/stackforge/python-congressclient +https://opendev.org/stackforge/python-congressclient diff --git a/specs/kilo/persistent-storage-for-api.rst b/specs/kilo/persistent-storage-for-api.rst index 948ea07..cf1a41f 100644 --- a/specs/kilo/persistent-storage-for-api.rst +++ b/specs/kilo/persistent-storage-for-api.rst @@ -125,5 +125,5 @@ References ========== http://alembic.readthedocs.org/en/latest/ -https://github.com/openstack/neutron/blob/master/neutron/db/migration/README +https://opendev.org/openstack/neutron/blob/master/neutron/db/migration/README 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..a757e4b 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 @@ -342,7 +342,7 @@ Dependencies We will depend on oslo-config-generator config-files, which can be used to describe OS services config-files. -https://github.com/openstack/oslo-specs/blob/master/specs/juno/oslo-config-generator.rst +https://opendev.org/openstack/oslo-specs/blob/master/specs/juno/oslo-config-generator.rst We rely extensively on the oslo-config lib. diff --git a/specs/rocky/alternative-engine-z3.rst b/specs/rocky/alternative-engine-z3.rst index 815b0b8..d77ae44 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 @@ -307,8 +307,8 @@ Documentation should at least mention: References ========== -[1] https://github.com/Z3Prover/z3 +[1] https://opendev.org/Z3Prover/z3 -[2] https://github.com/Orange-OpenSource/octant +[2] https://opendev.org/Orange-OpenSource/octant [3] https://specs.openstack.org/openstack/congress-specs/specs/rocky/explicit-data-types diff --git a/specs/rocky/explicit-data-types.rst b/specs/rocky/explicit-data-types.rst index 5fc0c01..b2b6db4 100644 --- a/specs/rocky/explicit-data-types.rst +++ b/specs/rocky/explicit-data-types.rst @@ -673,6 +673,6 @@ References A relevant type system for a Z3-based datalog solver: -- https://github.com/Orange-OpenSource/octant/blob/master/doc/source/user/index.rst +- https://opendev.org/Orange-OpenSource/octant/blob/master/doc/source/user/index.rst -- https://github.com/Orange-OpenSource/octant/blob/master/octant/datalog_primitives.py +- https://opendev.org/Orange-OpenSource/octant/blob/master/octant/datalog_primitives.py 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