This commit is part of a series to retire the Packaging Deb
project. Step 2 is to remove all content from the project
repos, replacing it with a README notification where to find
ongoing work, and how to recover the repo if needed at some
future point (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
Change-Id: I1d47486e0f1e920f35b8492abd3a042582cd1017
This change introduces new datastore option "icmp" to
configure whether to permit ICMP. It helps users to
check DB instance health in different way from access
DB ports.
DocImpact
Closes-Bug: #1485884
Change-Id: I61edeb38ded5543b7976a01363108a7b5b4fc5b5
Updated CONTRIBUTING.rst to reflect discussions at mid-cycle regarding
abandonment of changes that are languishing in the gerrit review
system.
Change-Id: Ie9d22b01d09c2cdb250abd0596c0216ec457df4d
The code responsible for pulling the last GTID reference from
snapshot backup restored to the replica only handled the case
where the GTID reference contained one gtid. There are common
replication use cases where the GTID reference in the file is
comma separated list of GTID references. Change the code from
using the CSV reader to just read the entire file and split it
on tabs. This will guarantee that we get the full list of GTID
references in the file.
Change-Id: Ibbde5a4daa9741e1b997a618288bf6d469356bfe
Closes-bug: 1604914
Currently, devstack/plugin.sh adds port 22 to mysql's tcp_ports in
trove-taskmanager.conf.
This commit adds port 22 to other DB's tcp_ports.
This helps users who use devstack for development purpose.
Change-Id: I3c7c0b050c2983c9b2cb2c4b7f8f08d9a8b42f9c
It looks like these two unit tests pass on Python 3: remove them from
blacklist-py3.txt.
Partially implements: blueprint trove-python3
Change-Id: I230055c1aa0786290f9cae44f81861d91850d87b
* Use encodeutils.exception_to_unicode() to get the message of
exceptions. On Python 3, the message attribute of exceptions has
been removed.
* NamedTemporaryFile: open files in text mode, not in binary mode.
* test_dbaas: set rowcount in execute() mocks to avoid comparison
with a mock which now raises a TypeError on Python 3.
* replace "rowcount <= limit" with
"limit is not None and rowcount <= limit" to avoid comparison
between int and None (TypeError on Python 3)
* Replace urllib.quote() with six.moves.urllib.parse.quote
* blacklist-py3.txt: remove guestagent.test_dbaas to run it
on Python 3
Partially implements: blueprint trove-python3
Change-Id: Ibdd34485ce4f2fb3572dcd7f57cbf9e5b6f42a13
If you run the py27 tox tests then attempt to run the py34 tests,
the following error will occur:
py34 runtests: commands[0] | ostestr
--blacklist_file=blacklist-py3.txt
db type could not be determined
running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --list
The test run didn't actually run any tests
This happens because the apparently the times.dbm file generated
by py27 is not compatible with py34. The converse is not true though -
if you run py34 first, py27 will work.
The work-around is to delete the file, which is what is now done
before running every tox test. Once the bug has been fixed, the
work-around can be removed.
This was originally noticed in python-troveclient, however it
also manifests in the Trove project.
coverage.xml was also added to the .gitignore file as it
was appearing in the git list of modified files.
Change-Id: I312b3879c764b7b803d35e0bb62f0f47291f6693
Closes-Bug: #1565928
The backup scenario tests currently only
verify data in the helper database.
We should also make sure no other databases
are created or deleted in the process.
Also removed a leftover mixin class.
That code was not used anywhere.
Also change the base instance name pattern
to allow selecting the name by double-clicking it.
(Linux bash stops at ':', and Mac equvalent stops at
':' and '-'. Windows shell always selects the whole
thing.)
Change-Id: I01ad0472bde59a95c619fb881cef976937b79fa6
The Trove tempest plugin was created in this commit:
Ibad5502cdca0e34cca4b5bc8a7106611f7393cf2. The tests however was
not working because the plugin specific configuration variables
was not being set correctly. This particular issue has been
fixed in this changeset. Using the following commands:
tox -e all-plugin -- trove.tests.tempest.tests.api
4/5 tests pass. Will look into the failing test in a different
changeset.
Change-Id: Iad34209adb120e63cebbf12939baf30c5f017844
Partial-Bug: #1597857
Cluster tests rely on the instance flavor to be set
already. This works when the single instance tests
run before (they initialize it) but not when
running cluster tests standalone.
Make cluster tests retrieve the flavor themselves.
Change-Id: I8bac99fecc9508bb5452169836e8c28a3e3a92b5