openstack/watcher-specs
Code Issues Proposed changes

update git.openstack.org to opendev

Browse Source 
Fix line length in recently passed to spec to build with the url changes

Co-Authored-By: chenker <chen.ke14@zte.com.cn>
Co-Authored-By: Dantali0n <info@dantalion.nl>

Depends-on: I98d4c3e9924346b826e5267b0b7c6b73f86741aa
Change-Id: If2f80f65bb37656d0604b6565bbdd33be2c80cc0
This commit is contained in:
liuwei 2019-04-29 13:58:09 +08:00 committed by chenker
parent bcbfca2567
commit 776f221fb8
11 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/backlog-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/mitaka-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/mitaka/implemented/watcher-add-actions-via-conf.rst
View File

@ -483,7 +483,7 @@ IRC discussions:
* Action point related to `TaskFlow`_: http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-09-13.59.html
* A lot of exchanges regarding Actions and Workflow management in the Git
reviews related to the Watcher glossary: https://review.openstack.org/#/c/246370/
reviews related to the Watcher glossary: https://review.opendev.org/#/c/246370/
History

2
specs/ocata-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/pike-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/queens-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/rocky-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/stein-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

2
specs/train-template.rst
View File

@ -74,7 +74,7 @@ Some notes about using this template:
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/watcher-specs+message:apiimpact,n,z
https://review.opendev.org/#/q/status:open+project:openstack/watcher-specs+message:apiimpact,n,z
Problem description

22
specs/train/approved/global-datasource-preference.rst
View File

@ -22,11 +22,11 @@ Problem description
===================
The datasources available to Watcher differs per OpenStack deployment so there
can not be a standard preference that will work for all deployments. Configuring
which datasources are preferred is essential to correctly deploying Watcher,
however, the datasource preference needs to be defined per strategy. As a result
the datasource preference will have to be configured many times which can lead
to errors and costs more time.
can not be a standard preference that will work for all deployments.
Configuring which datasources are preferred is essential to correctly deploying
Watcher, however, the datasource preference needs to be defined per strategy.
As a result the datasource preference will have to be configured many times
which can lead to errors and costs more time.
Use Cases
----------
@ -41,9 +41,9 @@ Proposed change
===============
Allow specifying of global datasource order by exposing new configuration
parameter. This parameter will be part of a new group labeled watcher_datasource
. The datasource parameter for strategies remains available and overrides
the globally configured datasources.
parameter. This parameter will be part of a new group labeled
watcher_datasource. The datasource parameter for strategies remains available
and overrides the globally configured datasources.
::
@ -53,9 +53,9 @@ the globally configured datasources.
Alternatives
------------
Try datasources but ensure that if they are not properly configured an error is
raised and an alternative datasource is tried. Major downside of this approach
is that it will create a lot of errors in some scenarios.
Try datasources but ensure that if they are not properly configured an error
is raised and an alternative datasource is tried. Major downside of this
approach is that it will create a lot of errors in some scenarios.
Data model impact
-----------------

2
tox.ini
View File

@ -9,7 +9,7 @@ skipsdist = True
basepython=python3
usedevelop = True
setenv = VIRTUAL_ENV={envdir}
install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt} {opts} {packages}
install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE:https://opendev.org/openstack/requirements/raw/branch/master/upper-constraints.txt} {opts} {packages}
deps = -r{toxinidir}/test-requirements.txt
whitelist_externals = find
commands =