Go to file

licanwei d0681dd2ba Add a force field to audit

As now, Watcher doesn't allow to launch a new audit when there
is actionplan ongoing. This patch gives the choice to User,
if User set force when launching audit, Watcher will execute the
audit even other actionplan is ongoing.

Change-Id: I276ebcee0b09bfc6f27ec39f43ba2ecd230db2b2
Implements: blueprint add-force-field-to-audit

2019-04-25 17:17:23 +08:00

doc/source

Solve the error: 'Sphinx' object has no attribute 'info'

2019-04-04 17:44:18 +08:00

priorities

Add Train priorities

2019-04-15 08:42:48 +02:00

specs

Add a force field to audit

2019-04-25 17:17:23 +08:00

tests

Provide a more dynamic Actions management solution

2016-01-08 10:53:54 +01:00

.gitignore

Add Stein series and move approved Rocky specs as implemented

2018-09-12 18:03:05 +00:00

.gitreview

Added .gitreview

2015-10-23 11:59:37 +00:00

.stestr.conf

Switch to stestr

2018-07-10 11:22:34 +07:00

.zuul.yaml

import zuul job settings from project-config

2018-08-22 18:13:12 +09:00

LICENSE

Setup watcher-specs repository

2015-11-10 06:28:39 -06:00

README.rst

Update links in README

2017-08-04 11:13:23 +08:00

requirements.txt

Solve the error: 'Sphinx' object has no attribute 'info'

2019-04-04 17:44:18 +08:00

setup.cfg

Change openstack-dev to openstack-discuss

2018-12-04 17:30:29 +08:00

setup.py

Setup watcher-specs repository

2015-11-10 06:28:39 -06:00

test-requirements.txt

Switch to stestr

2018-07-10 11:22:34 +07:00

tox.ini

Remove stestr from requirements.txt

2018-12-05 13:28:49 +03:00

README.rst

Team and repository tags

README

Watcher Specifications

This git repository is used to hold approved design specifications for additions to the Watcher project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself. For specific policies around specification review, refer to the end of this document.

The layout of this repository is:

specs/<release>/

Where there are two sub-directories:

specs/<release>/approved: specifications approved, but not yet implemented specs/<release>/implemented: implemented specifications