| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Change-Id: Ifee8620a41e439b028e0a4d65164a75a100ce4d9
|
|/
|
|
| |
Change-Id: If48ef016c6fb7a875ceabc9f106e4cd85858d147
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I9662c4c23f3d2879d78e26fe4b32a6f55b6cfb99
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
A new field named ``service_status_updated`` is added to the instance
API response which e.g. could be used to validate if the instance
'HEALTHY' status is stale or not.
Change-Id: Iabcfad81343a71304b843b3a7778486253220d20
|
|/
|
|
| |
Change-Id: Ic1d4982a479c2154d7ddcc807d863e2a37fea506
|
|
|
|
| |
Change-Id: I9391b0e50ae37c1fc40268cba566a72fba0ce329
|
|
|
|
| |
Change-Id: I3606540f8d22999c3832acf42bcf73033e44a62a
|
|
|
|
| |
Change-Id: I4c2057e2bde8fd1169ca52a15ccca66740e9f069
|
|
|
|
|
|
|
|
|
|
|
| |
- 'HEALTHY' means the db service is responsive, 'ACTIVE' means the db
service is alive.
- Remove the CI job fakemodetests, but will add similar testing task in
the future.
- Fix the periodic CI job
- Remove MongoDB and related jobs
Change-Id: I5abe9091ba203297dc87db5fba139179166321f7
|
|
|
|
| |
Change-Id: I2108f2c6bf067ce228829de9c4e7e47005acf358
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Deal with the situation when Trove fails to look for the Nova server
when waiting for the db instance ACTIVE
Change-Id: I484d45f24176c89d999864d3eb1c48860b3038bd
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I11456aaeb2d417dbae6bdb0e51944aa122c521e0
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
Change-Id: I87f3eba550326abcef1985a001a358125b6820a8
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch will fix following issues:
- Existed logs xbstream
- '@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.
Change-Id: I0968cd794801285fa6effd5da2770e1270e3cfb2
Story: #2006656
Task: #36903
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| | |
Enable the tests in CI as well.
Change-Id: Ie9706d26355bd325baf50ec874f05e6904768a1a
|
|/
|
|
| |
Change-Id: I6e10744f86f19f3c29babc07fda77936c95022ff
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OpenStack is dropping the py2.7 support in ussuri cycle.
Trove is ready with python 3 and ok to drop the
python 2.7 support.
Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support
Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Change-Id: I6b448747c873bfc9c0138c0f7e3ca67ddce02dee
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch will solve some following items:
- Support python3/ pip3
- Permit redis is running with guest-agent service
Tested with standalone, replicate and cluster successfully.
Change-Id: I81b72fae1c31ce2995232b52460d0ad0d6f894be
|
| |
| |
| |
| |
| |
| | |
Fix the current CI issue as well.
Change-Id: I7daafa68a03a3bf88c3651b6cab8c58cf5256b29
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This patch will auto-process with `pip-and-virtualenv`
element when use `guest-agent` in python3. We also can add
this element in disk-image-create cli which instead of
this patch to fix following issue:
2019-09-12 09:19:58.674 | + python3 -m virtualenv /opt/guest-agent-venv
2019-09-12 09:19:58.752 | /usr/bin/python3: No module named virtualenv
Change-Id: I21090320ba7396979cee31431de7198150dd763e
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I7beb6849abbfc889bae29668deb4ba7ae93df91d
|
|/
|
|
|
|
|
|
|
| |
- Trove supports MariaDB 10.4
- From MariaDB 10.3, Mariabackup is used instead of Percona XtraBackup
for backup functionality
- Some log improvements
Change-Id: Ibaa6fd7273b98451097b32fb6b881008a236be9f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When building the guest image for dev_mode=true, the controller IP
address is injected to the image in order for the guest-agent to
download Trove code during initialization. As a result, we have to build
guest image each time in the Trove CI because the image build relies on
the devstack host IP address.
If we could remove the dependency, we can build the image(in
devmode=true) for a specific datastore once and use that image for all
related CI jobs, which could save some time for Trove CI.
Fix the current CI issue as well.
Change-Id: If23f4f179a6ab72cfb35e4c45d55142fedb76498
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Rename TROVE_DISABLE_IMAGE_SETUP to TROVE_ENABLE_IMAGE_BUILD to avoid
double negative definition.
Change-Id: Iede80c39bb2a7aaf3c0453bd67f85375fa5ee76c
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: I179005a5bcf2a2c01ecae068a400503b412cd9e2
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: Icf86fd2a7d2692707449cfb11edbd936b0b79aa6
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
The current admin credential config options are confusing
Change-Id: I92c15c065edf364b955f2243b3599e0b8cae8b4f
|
|/
|
|
|
|
|
|
|
|
| |
- Explicity specify branch name for building non-dev image
- Use branch name for building dev image in devstack
- Update the doc
Candidate backport for stable/train
Change-Id: I4d2fe38fac34c75b42234fa7a20aba51e6dc1c4e
|
|
|
|
|
|
|
|
|
| |
Backport candidate for stable/train
Story: 2006664
Task: 36926
Change-Id: If0991e0cef40ca78752fcd509d8438e90c9557bc
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
DevStack is deploying Trove in service tenant model, for swift backed
instance backup, the swift container should be transparent to the end
users.
Story: 2006647
Task: 36883
Change-Id: I5859f4c9911fc2c129c8f23611c6607044fbc145
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This issue was occurring with percona database (v5.6).
Error logs:
`An error occurred preparing datastore: (pymysql.err.InternalError)
(1372, 'Password hash should be a 41-digit hexadecimal number'`
Tested with re-enable root function for both v5.6 and v5.7.
Change-Id: Ied67c7c243d3f8c644708548cce71ea2aa3cf2e7
Story: #2006546
Task: #36629
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Even though those are debug level logs, it doesn't make sense for the
operators. If it's timeout or error occurs, the operator could see
the VM status and service status from the CLI.
Change-Id: I3fc9ff9e9343c1c884eece4955f15766230ff9a0
|
|/ /
| |
| |
| | |
Change-Id: I7874d498eb80c0b5cda802acb76e5fe399770e6a
|