Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: I0e40eb0e5267d1cdd0ec1195424743310f3c39f8
Because 2.5.1 is the version available on RHEL/CentOS 7.
This is done by replacing the use of psycopg2.sql module.
Change-Id: Ie83ca2b3cd439649878517fa0fbc2a4381ad018d
Closes-Bug: 1823095
This commit adds Tacker driver and unit tests. Which creates
corresponding datasource on service startup and allows congress
to maintain Tacker's VNF and VNFD data via populating data to tables
vnfs and vnfds respectively. Based on which rules
can be created and actions can be executed on tacker service.
Change-Id: I281e8ff508dd066514694419c5aae6a991ab307c
Partially-Implements: blueprint add-tacker-datasource-driver
New PollingJsonIngester class which polls API end points as defined
in YAML configs and populates configured postgreSQL database with
JSON data.
Change-Id: I8d22cf8d2da1b1c2e99b8e0cd2d60f3ef71e2def
partially-implements: bp json-data-model
This commit adds the functionality of congress-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.
Change-Id: I27204c1c2dce2443eaa18a85144cbc892d61b551
Story: 2003657
Task: 26125
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I37f96444426f006ff5d6491106b168a81a7c09ea
Action execution allows using policy to trigger data source client
methods. But some of these methods require a python structure as input,
which cannot be constructed by the congress policy language.
With this patch, the policy language can construct JSON/YAML strings,
which get loaded as python structure before passing to the data source
client methods.
Because there is no automated way to know which arguments to which
methods are non-scalar structures, the functionality requires a
data source driver to specify that information in
self.method_structured_args.
The patch also other related changes:
- specifies the desired structured arguments for the
neutronv2 drivers
- omits the neutron client update_* made redundant by the special
update_resource_attr action.
- updates a policy library to make use of the feature
Depends-On: I34d1a392d4539ede01666002cfa301c21f9cd4bd
Change-Id: I33860ffdcda3e0bc67e488ff2b35bba57241cf02
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I6c115612ac6ee56f2199c654a844fed8723ca666
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>