they are not maintained for a long time, and trove already switch
the tests to templest.
This commit removes the usage of them. more details see story.
Story: 2010882
Task: 48606
Depends-On: https://review.opendev.org/c/openstack/trove/+/914228
Change-Id: Ie021e0bd708cf8ed13853dea632312af38190205
Functional tests are executed by trovestack script, which uses python
in default OS version which is 2.7.
This change wraps python in tox and executes trovestack int_tests in
virtual enviroment, starting them in python3.
Any future python version change could be managed by tox framework.
Change-Id: I3a849978241d3d0669ef9e1c802ff504ac3c32cb
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
Slow query time should be configurable on per-instance basis
via the existing configuration group mechanism (see the bug).
We need to deprecate the existing global conf property first.
The property has been deprecated on all datastores.
Validation rules have been updated on those that
support log retrieval as well:
- MySQL: long_query_time
- Percona: long_query_time
- Percona XtraDB Cluster: long_query_time
- PostgreSQL: log_min_duration_statement
- MariaDB: long_query_time
The logging settings will be saved with lower 'priority' than
any user settings. This will ensure the user settings
(if present) always override the global value.
Once the deprecated options go away we can again apply
the logging settings at the system level.
Change-Id: I9c28ceb933b6819b8e96556584b2e26cab2155fb
DocImpact: Document deprecated properties
Partial-Bug: 1542485
The replication scenario tests were broken into separate
parts to facilitate parallel runs in the gate.
The verify_data helper was also enhanced to retry so that
arbitrary sleeps are no longer necessary to ensure that
data has time to replicate.
Additional data was also added/verified once the replication
network is back to its original configuration.
Partial-Bug: #1571092
Change-Id: I78bc945b36b1abba19e102cc2742984bd2375513
The currently used property has different validation rules
accross MySQL-like datastores. Use a value that will
be always invalid.
Change-Id: Iaca3f4839ee83f8e25063a04f53bff8f501d96c2
The scenario tests need to have the group classes broken
up to allow interleaving of the different parts of the tests
so that the gate can finish in a reasonable amount of time.
The runners, however, need to be the same for each main group,
thus allowing state to be preserved between groups of the same
feature. The creation of runners was refactored to allow for this.
The module tests were also modified to use the new paradym, which
allowed the removal of the global varaibles in the runner.
Dependencies on tests.api were also removed.
Change-Id: I66fcb2bce8c6cbc99c9ff071c242e4741500056d
Partial-Bug: #1571092
The vertica root enable extension has a similar pattern that other
datastores can use for enabling root. (i.e. pxc) Made a few changes to
abstract this logic to a cluster centric root enable controller and
still allowed the specific vertica changes to its own extension.
Adding the scenario test to verify that the root user can connect and
see the added initial data. Also added a delete of the root restore
instance.
Unit tests added for coverage.
Implements: blueprint pxc-root-enable
Change-Id: I7b59914487bedd5b0f3b40dcae6c07024920365e
Implements log file retrieval from the guest agent. The contents
of the log file are pushed up to a swift container as a series of
objects that represent a subset of the lines in the log.
The following trove CLI commands are now supported:
trove log-list <instance> : lists log files available on guest
trove log-enable <instance> <log> : enables writing to log file
trove log-disable <instance> <log>: disables writing to log file
trove log-publish <instance> <log>: publishes updates to swift container
trove log-discard <instance> <log>: discards published logs
trove log-tail <instance> <log> : displays last lines of log
trove log-save <instance> <log> : saves the entire log to a file
Log declarations and scenario tests were added for MySQL and
PostgreSQL.
Co-Authored-By: Morgan Jones <morgan@tesora.com>
Co-Authored-By: Alex Tomic <atomic@tesora.com>
Co-Authored-By: Peter Stachowski <peter@tesora.com>
Implements: blueprint datastore-log-operations
Change-Id: I16c3bba4a3183d05af2971be6ba56110105797a6
Adding a helper client for MySQL will enable int-tests
involving actual data operations.
The test_helper.py file was also modified to push
more boiler-plate code into the base class, as it has
become apparent that only one 'add' 'remove' and 'verify'
method is probably adecuate for most datastores (given
the right sane parameters). The Redis helper was also
cleaned up to use the new format.
Change-Id: Iff34ca0b922adc9eea8b3861b05adf0251109221
Co-Authored-By: Petr Malik <pmalik@tesora.com>
Co-Authored-By: Peter Stachowski <peter@tesora.com>
Add generic integration tests for instance create.
Also moved some global constants to the base runner.
Note: Did some additional cleanup work on other test groups as well.
Broke down some negative tests into more self-contained units.
Added a comment string on tests that did not have it.
Had to fix database_actions test to work for users defining
hosts (like MySQL users).
Change-Id: I7c1413fa5742c276454e26ebbbeae8e02569a392
wu.chunyang