diff --git a/.gitreview b/.gitreview index e4751bc8..0f46736f 100644 --- a/.gitreview +++ b/.gitreview @@ -1,4 +1,4 @@ [gerrit] -host=review.openstack.org +host=review.opendev.org port=29418 project=openstack/heat-specs.git diff --git a/specs/backlog/heat-property-group.rst b/specs/backlog/heat-property-group.rst index 07e7c1e9..ed60756a 100644 --- a/specs/backlog/heat-property-group.rst +++ b/specs/backlog/heat-property-group.rst @@ -162,7 +162,7 @@ Milestones Currently moved to backlog due to no community's interest. Workable PoC placed here: -https://review.openstack.org/#/q/topic:bp/property-group +https://review.opendev.org/#/q/topic:bp/property-group Work Items ---------- diff --git a/specs/backlog/resource-capabilities.rst b/specs/backlog/resource-capabilities.rst index 787eba43..bd66296c 100644 --- a/specs/backlog/resource-capabilities.rst +++ b/specs/backlog/resource-capabilities.rst @@ -51,7 +51,7 @@ For example, consider this workflow: created. The topic of this spec is steps 3 and 4 above. -https://review.openstack.org/#/c/197199 discusses step 5. The other steps +https://review.opendev.org/#/c/197199 discusses step 5. The other steps are already possible. The discussion below focuses on the TripleO use case, since that is what is @@ -306,7 +306,7 @@ not the options related to a valid composition. .. rubric:: References .. [1] http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/csd03/TOSCA-Simple-Profile-YAML-v1.0-csd03.html#_Toc419746122 -.. [2] https://review.openstack.org/#/c/197199 +.. [2] https://review.opendev.org/#/c/197199 Alternatives ------------ diff --git a/specs/juno/reorg-autoscaling-group.rst b/specs/juno/reorg-autoscaling-group.rst index eb7d8f15..d4a8d89e 100644 --- a/specs/juno/reorg-autoscaling-group.rst +++ b/specs/juno/reorg-autoscaling-group.rst @@ -193,7 +193,7 @@ No new dependencies to other libraries will be introduced. This work may disturb several on-going work related to AutoScalingGroups. The following work will have to be rebased on this change. -#. https://review.openstack.org/110379 Scaling group scale-down plugpoint -#. https://review.openstack.org/105644 LaunchConfiguration bdm -#. https://review.openstack.org/105907 Balancing ScalingGroup across AZs +#. https://review.opendev.org/110379 Scaling group scale-down plugpoint +#. https://review.opendev.org/105644 LaunchConfiguration bdm +#. https://review.opendev.org/105907 Balancing ScalingGroup across AZs diff --git a/specs/juno/stack-lifecycle-plugpoint.rst b/specs/juno/stack-lifecycle-plugpoint.rst index d178baf4..8a61131d 100644 --- a/specs/juno/stack-lifecycle-plugpoint.rst +++ b/specs/juno/stack-lifecycle-plugpoint.rst @@ -99,7 +99,7 @@ Implementation A patch comprising a full implementation of the blueprint -(https://review.openstack.org/#/c/89363/) is already being +(https://review.opendev.org/#/c/89363/) is already being reviewed, under the old pre-spec process. Assignee(s) @@ -117,7 +117,7 @@ Target Milestone for completion: Work Items ---------- -Implementation: https://review.openstack.org/#/c/89363/ +Implementation: https://review.opendev.org/#/c/89363/ diff --git a/specs/kilo/add-pciport-resource.rst b/specs/kilo/add-pciport-resource.rst index 5d42280f..a3aede11 100644 --- a/specs/kilo/add-pciport-resource.rst +++ b/specs/kilo/add-pciport-resource.rst @@ -87,7 +87,7 @@ Target Milestone for completion: Work Items ---------- -* modify OS::Neutron::Port https://review.openstack.org/#/c/129353/ +* modify OS::Neutron::Port https://review.opendev.org/#/c/129353/ Dependencies ============ diff --git a/specs/kilo/ceilometer-gnocchi-alarm.rst b/specs/kilo/ceilometer-gnocchi-alarm.rst index 0976b253..4cdbc872 100644 --- a/specs/kilo/ceilometer-gnocchi-alarm.rst +++ b/specs/kilo/ceilometer-gnocchi-alarm.rst @@ -133,4 +133,4 @@ None References ---------- -* https://review.openstack.org/#/c/153291/ +* https://review.opendev.org/#/c/153291/ diff --git a/specs/kilo/stack-lifecycle-scheduler-hint.rst b/specs/kilo/stack-lifecycle-scheduler-hint.rst index 62446a3f..2af8a4e3 100644 --- a/specs/kilo/stack-lifecycle-scheduler-hint.rst +++ b/specs/kilo/stack-lifecycle-scheduler-hint.rst @@ -33,8 +33,8 @@ resource within a heat stack. It is out of scope for this spec, but worth noting that cinder scheduler hints are now supported by heat and may need similar treatment. See -https://review.openstack.org/#/c/126282/ and -https://review.openstack.org/#/c/126298/ +https://review.opendev.org/#/c/126282/ and +https://review.opendev.org/#/c/126298/ Proposed change @@ -78,7 +78,7 @@ Assignee(s) ----------- A patch comprising a full implementation of the blueprint -(https://review.openstack.org/#/c/96889/) is already being +(https://review.opendev.org/#/c/96889/) is already being reviewed, under the old pre-spec process. Primary assignee: @@ -93,7 +93,7 @@ Target Milestone for completion: Work Items ---------- -Implementation: https://review.openstack.org/#/c/96889/ +Implementation: https://review.opendev.org/#/c/96889/ Documentation: Add good documentation to heat in tree docs diff --git a/specs/kilo/stack-tags.rst b/specs/kilo/stack-tags.rst index 5dede649..7f41e740 100644 --- a/specs/kilo/stack-tags.rst +++ b/specs/kilo/stack-tags.rst @@ -82,7 +82,7 @@ Work Items - Add a "tags" parameter to stack-create (engine and API). Note: Tag names must not contain a comma, as specified in the spec: - https://review.openstack.org/#/c/155620/ + https://review.opendev.org/#/c/155620/ - Add ability to update stack tags during stack-update (engine and API). It should be possible to remove all tags from a stack. diff --git a/specs/kilo/versioned-objects.rst b/specs/kilo/versioned-objects.rst index 621f1f6e..03634f1a 100644 --- a/specs/kilo/versioned-objects.rst +++ b/specs/kilo/versioned-objects.rst @@ -28,7 +28,7 @@ We are looking to improve the way we deal with versioning (of all sorts db/rpc/rest/templates/plugins). Nova has come up with the idea of versioned objects, that Ironic has also now used. This has now been proposed as an oslo library: -https://review.openstack.org/#/c/127532/ +https://review.opendev.org/#/c/127532/ https://etherpad.openstack.org/p/kilo-crossproject-upgrades-and-versioning diff --git a/specs/liberty/heat-python34-support.rst b/specs/liberty/heat-python34-support.rst index bab500ef..883b2f60 100644 --- a/specs/liberty/heat-python34-support.rst +++ b/specs/liberty/heat-python34-support.rst @@ -108,4 +108,4 @@ test-requirements.txt - mox: needs to be replaced by mox3 until we move to mock completely. [1] https://bitbucket.org/ianb/pastedeploy/commits/f30a7d518c6a79fcddfbe3f622337f81e41cb6a5 -[2] https://review.openstack.org/#/c/174738/ +[2] https://review.opendev.org/#/c/174738/ diff --git a/specs/liberty/nested-validation.rst b/specs/liberty/nested-validation.rst index 4d8c8f11..cc9ab72e 100644 --- a/specs/liberty/nested-validation.rst +++ b/specs/liberty/nested-validation.rst @@ -46,7 +46,7 @@ For example, consider this workflow: capabilities/options. These are the first major choices a user will make, to determine the nested stack implementations for each type. 4. The user selects a nested stack choice for each one that has more than one - choice (note https://review.openstack.org/#/c/196656/ discusses approaches + choice (note https://review.opendev.org/#/c/196656/ discusses approaches for this selection to be made programmatically via the choices made in (3)) 5. Reinspect given those major options for the full set of parameters such that the user may be prompted for mandatory and optional parameters, including diff --git a/specs/liberty/upgrade-tests.rst b/specs/liberty/upgrade-tests.rst index 42b2cb83..f4ea8827 100644 --- a/specs/liberty/upgrade-tests.rst +++ b/specs/liberty/upgrade-tests.rst @@ -98,4 +98,4 @@ Work Items Dependencies ============ -Grenade external plugin mechanism https://review.openstack.org/#/c/185050 +Grenade external plugin mechanism https://review.opendev.org/#/c/185050 diff --git a/specs/mitaka/event-transport.rst b/specs/mitaka/event-transport.rst index 5cebed98..af34fe32 100644 --- a/specs/mitaka/event-transport.rst +++ b/specs/mitaka/event-transport.rst @@ -84,4 +84,4 @@ Work Items Dependencies ============ -- Event message format: https://review.openstack.org/231382 +- Event message format: https://review.opendev.org/231382 diff --git a/specs/mitaka/mark-unhealthy.rst b/specs/mitaka/mark-unhealthy.rst index 8639819a..3fc40944 100644 --- a/specs/mitaka/mark-unhealthy.rst +++ b/specs/mitaka/mark-unhealthy.rst @@ -138,7 +138,7 @@ inaccurately, in reviews as "SOAP in ReST clothing"). The main driver behind it seems to be a belief that projects will be unwilling to implement a fully ReSTful interface like that proposed here. -.. _proposed guidelines: https://review.openstack.org/#/c/234994/ +.. _proposed guidelines: https://review.opendev.org/#/c/234994/ We could re-use the existing signal API instead of adding a new endpoint. However, that would mean a mix of responsibility in handling signals between @@ -159,7 +159,7 @@ Instead of defining a particular state transition, we could allow the user to set arbitrary resource states. This is a giant can of worms. This proposal is an alternative to the one presented in -https://review.openstack.org/#/c/212205/ which involved mechanisms to place the +https://review.opendev.org/#/c/212205/ which involved mechanisms to place the member IDs of various types of scaling groups under user control. This proposal is both more generic and more relevant to the future convergence plans than that one. diff --git a/specs/newton/convergence-migrate-stacks.rst b/specs/newton/convergence-migrate-stacks.rst index d705f724..7047425e 100644 --- a/specs/newton/convergence-migrate-stacks.rst +++ b/specs/newton/convergence-migrate-stacks.rst @@ -86,7 +86,7 @@ Work Items - add the new command to heat-manage. - add code to stack.py to do the migration. - unit tests. -- functional tests: https://review.openstack.org/#/c/230292/ +- functional tests: https://review.opendev.org/#/c/230292/ Dependencies ============ diff --git a/specs/newton/devstack-plugin.rst b/specs/newton/devstack-plugin.rst index dc7a1c9c..936a0a1d 100644 --- a/specs/newton/devstack-plugin.rst +++ b/specs/newton/devstack-plugin.rst @@ -21,7 +21,7 @@ http://docs.openstack.org/developer/devstack/plugins.html By enabling this plugin, we just need to properly set up devstack local[rc] file to be able to setup heat. A good example is ironic one: -https://review.openstack.org/#/q/topic:ironic-devstack-plugin +https://review.opendev.org/#/q/topic:ironic-devstack-plugin Proposed change =============== diff --git a/specs/newton/migrate-to-use-aodh.rst b/specs/newton/migrate-to-use-aodh.rst index f9bacd96..9b16f9d9 100644 --- a/specs/newton/migrate-to-use-aodh.rst +++ b/specs/newton/migrate-to-use-aodh.rst @@ -20,12 +20,12 @@ Problem description =================== Ceilometer has moved all the alarming code and subsystem to the Aodh project: -https://review.openstack.org/#/c/196552 -https://review.openstack.org/#/c/197161 +https://review.opendev.org/#/c/196552 +https://review.opendev.org/#/c/197161 Although now we can use ceilometer-client to redirect to Aodh endpoint when creating alarm resources: -https://review.openstack.org/#/c/202938 +https://review.opendev.org/#/c/202938 But there are some reasons I believe we should to migrate to use Aodh service directly: diff --git a/specs/templates/backlog-template.rst b/specs/templates/backlog-template.rst index 29e23ada..95c8b8bd 100644 --- a/specs/templates/backlog-template.rst +++ b/specs/templates/backlog-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/kilo-template.rst b/specs/templates/kilo-template.rst index 572bbfcd..8f853642 100644 --- a/specs/templates/kilo-template.rst +++ b/specs/templates/kilo-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/liberty-template.rst b/specs/templates/liberty-template.rst index 69822070..b8f7f5e4 100644 --- a/specs/templates/liberty-template.rst +++ b/specs/templates/liberty-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/mitaka-template.rst b/specs/templates/mitaka-template.rst index c4406f03..04b29be2 100644 --- a/specs/templates/mitaka-template.rst +++ b/specs/templates/mitaka-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/newton-template.rst b/specs/templates/newton-template.rst index 05e19ac9..451d7619 100644 --- a/specs/templates/newton-template.rst +++ b/specs/templates/newton-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/ocata-template.rst b/specs/templates/ocata-template.rst index d1f97144..05e368ca 100644 --- a/specs/templates/ocata-template.rst +++ b/specs/templates/ocata-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/pike-template.rst b/specs/templates/pike-template.rst index c21ab5b7..431f7bea 100644 --- a/specs/templates/pike-template.rst +++ b/specs/templates/pike-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/queens-template.rst b/specs/templates/queens-template.rst index f95fbef7..1cf05500 100644 --- a/specs/templates/queens-template.rst +++ b/specs/templates/queens-template.rst @@ -45,7 +45,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------ diff --git a/specs/templates/rocky-template.rst b/specs/templates/rocky-template.rst index 0e40c6c2..326ed045 100644 --- a/specs/templates/rocky-template.rst +++ b/specs/templates/rocky-template.rst @@ -44,7 +44,7 @@ the semantics of what happens when a client calls into the API, then you should add the APIImpact flag to the commit message. Specifications with the APIImpact flag can be found with the following query: -https://review.openstack.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z +https://review.opendev.org/#/q/status:open+project:openstack/heat-specs+message:apiimpact,n,z Alternatives ------------