The switch to XtraBackup 2.3 was causing an issue on RHEL/Centos
related to is using the "mysql" user instead of "trove". The fix on
Ubuntu was to move the os_admin credentials to ~trove/.my.cnf. While
this is a better place to write the credentials anyway (i.e. they
shouldn't be stored in server my.cnf) this doesn't solve the whole
issue on Centos. This commit changes the XB backup strategy to pass
the user/password in on the innobackupex command line.
Also, it was noticed that the "socket" option wasn't being specified
in the config.template. This is causing some client connections,
such as XB to fail connect because it can't locate the socket.
Forcing the server/client to write/read the socket from a known
location fixes this.
Change-Id: Iea941ce60179ef4dc5c403c2fc374cc8eb7d1617
Closes-bug: 1649592
With this email[0], you must migrate API reference docs into RST. The
conf.py and the tox environment are also cribbed from nova.
Still need to retain the install_command in tox.ini, otherwise the
api-ref job fails.
[0] http://lists.openstack.org/pipermail/openstack-dev/2016-May/093765.html
Co-Authored-By: Anne Gentle <agentle@cisco.com>
Co-Authored-By: Amrith Kumar <amrith@tesora.com>
Change-Id: I3315261aa18729fa7a6aa79d4a1d6c24de1e2c6b
Service manager cannot properly manage the MySQL
process if the pid file / socket are not defined
for the mysql_safe process.
Also rename 'pid_file' to 'pid-file', default for
both 5.6 and 5.7 and the only name accepted in the
'mysql_safe' section.
Update MySQL derivatives: MySQL, Percona and PXC.
Change-Id: I44441144a74e01d3c816ca72b2da4aa351dbd46c
Closes-Bug: 1605385
The data type information was lost in conversions.
IniCodec should deserialize Python objects (like other codecs).
guestagent_utils.to_bytes should return byte values as ints.
* The IniCodec is also used by Cassandra.
Tested with both MySQL and Cassandra scenario tests.
Change-Id: Ibb703b3db6814fc0c9ea4c6d96399f6c881cea03
Closes-Bug: 1599656
Note that the option name has changed.
Also removed an unnecessary commented line.
Change-Id: I963724e553baf0870c95aecd1cabc8cbba3da422
Closes-Bug: 1580315
Added the route action for disabling the root user in the extensions.
Modified the resource extension to allow the generation of a DELETE
route on the resource itself.
Implemented root-disable on the mysql guest. Added not implemented
error messages for all other datastores.
Change-Id: I52519b86c47694c554b624d1d2fbe7a001af55fc
Partially implements: blueprint root-disable
Depends-On: I27831eb361c2b219a9623f152b9def73a2865d67
Replace the sqlalchemy engine and session management with an oslo.db
facade. This does the work transparently and fixes connection
mismanagement.
The changes involve:
- modifying the sqlalchemy session script to use oslo_db functions
- adding the oslo_db engine configuration parameters
- tweaking the faked tests to pass*
* the faked tests are sensitive to sleep calls and oslo_db uses a
sleep(0) hack which was causing issues. The coverage of the tests was
not affected.
Implements: blueprint move-to-oslo-db
Change-Id: I59f1fc0fe1551b9a815a51e6a620fabf060b013f
'lost+found' directories are no longer needed in the ignored list.
Include 'performance_schema' system database (by default ON in >=5.6.6).
Set 'performance_schema = ON' in default Trove configuration template and
add a validation rule for it so that users can turn it OFF if they so
desire.
Change-Id: Iecc114594091eabf8a0664e066b9de22f95d1e81
Closes-Bug: 1486721
Related-Bug: 1370646
Having the mysql datadir located at root of a mounted volume
(which happens with volume support enabled) causes problems for
backup/restore and resize. Mysql decides that the "lost+found"
directory, which the operating system puts at the root of each
file system, is actually a mysql "database".
This change causes the guest agent to move the datadir into a
sub-directory called "data" on the mounted volume.
Change-Id: Ica628012a5708374d73e5394e370da2514300939
Co-Authored-By: Simon Chang <schang@tesora.com>
Closes-bug: 1370646
Calculations for certain config parameters was resulting in zero
if a value < 512 was used as ram for flavors to boot guest instance.
Replaced '//' by '/' and the result is again casted to integer value
as needed by mysql configurations.
// implies divide two numbers and return
the truncated integer result.
whereas
/ implies divide two numbers and return value
will be a floating point number.
Updated default instance configuration response json.
Change-Id: Icfc84a4cb380264670aa4e31f372eb39a6e87c7c
Closes-Bug: #1440358
The owners of maven.research.rackspacecloud.com/ seem to have introduced
a 301 redirect permanent from http -> https URLs on around Jan 10th.
This has broken the master/trove check builds since that time.
Maven, when running in the infrastructure CI environment, fails to
follow these redirects.
This code change simply refers to the maven software repositories using
https URLs.
Local testing of this change against Tesora's downstream CI found that
it may be necessary to purge the broken/cached file from the bare-trusty
CI build machines ala:
rm /home/jenkins/.m2/repository/com/rackspace/cloud/api/wadl-tools/1.0.9
(continued..) /wadl-tools-1.0.9.jar
Closes-Bug: #1412949
Change-Id: I2dece05c74ad18a96fa05791e368ff7283a5e4e5
This allows operating on Nova flavors with non-integer ids
by adding a new str_id field to the view that always contains the
unicode flavor id. The current id field will now contain a value
only when the flavor's id can be cast to int, otherwise it will be
None. Validation of flavor id when querying a flavor or creating an
instance has been updated to include non-empty strings in addition to
integers.
This will require a patch to python-troveclient to properly fallback
to str_id in absence of the integer id:
https://review.openstack.org/#/c/123301/
Change-Id: Ie9cfefc6127bc76783cdf9668636342d7590b308
Closes-bug: #1333852
* Added Incremental backup test and resulting sample files.
* Fixed the example generator tests to actually fail when api
changes.
* Added changes since the last example generation was run.
* Added a --fix-examples flag to the example generator to
automatically correct the sample files.
Change-Id: I7ac355c80b251b0eccd3bd5b8d76d2287c255705
Closes-Bug: #1398119
Update pom.xml for building the database-api document to follow the
conventions used by the OpenStack documentation team:
* Remove "review" from published guide
* Disable Disqus
* Use latest clouddocs-maven-plugin (2.0.2)
* Fix canonicalURL so that it points to the current location
* Fix formatting and whitespace of file
Remove hardcoded publication date from cdb-devguide, this gets
generated at build time.
Update doc-test.conf for pom.xml change.
Change-Id: I90eb16917edbb99d99147c4a8116f5bcf28e6975
By hosting the docs here we'll be able to better maintain that
developers are being mindful of changes or even occassionally writing
documentation for new API features. This should also allow us to
autogenerate the snippets.
Change-Id: I0111bcd38341b1736a47b0a3d3e6ff96d2ca1c58
Lingxian Kong