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
parent
531fc152ee
commit
1791c1ed90
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -142,4 +142,4 @@ none
|
|||
References
|
||||
==========
|
||||
|
||||
https://github.com/stackforge/python-congressclient
|
||||
https://opendev.org/stackforge/python-congressclient
|
||||
|
|
|
|||
|
|
@ -188,4 +188,4 @@ Document the screenflow.
|
|||
References
|
||||
==========
|
||||
|
||||
https://github.com/stackforge/python-congressclient
|
||||
https://opendev.org/stackforge/python-congressclient
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue