The version of Redis installed by the current elements
uses a ppa that is stalled at 3.0.7. This seems to
have some issues that are fixed in later versions.
The recommended method of installing Redis is to compile
the code yourself, so the elements have been changed
to do this.
The version was bumped to 3.2.6 (latest stable) however
the Redis cluster tests were not reenabled as there still
seems to be an issue with them.
New config options were added to the template; these
may need to be updated to make sure all the new ones
are there.
Change-Id: I1a604b15ade815cdb51c5484d4285e504508a6c4
Partial-Bug: 1652964
When trove-integration was a thing, and was branchless, and not part
of the trove repository, we needed this kludge to get the guest
requirements. Now that trove-integration is no longer a thing, and the
image build is branched and part of the trove repository, we don't
need to keep requirements files which are version stamped.
The elements now just pick up either fedora-requirements.txt or
ubuntu-requirements.txt
This change will merge in master and get backported into stable/ocata.
Change-Id: I87b887befb2d12f607ffec919c79d462fbde42ca
Sometimes, trove image builds fail because of package authentication
issues. This is often times related to the inability to get to a key
server, and not indicative of anything more serious than that.
The (strongly discouraged in production use cases) workaround for this
is to pass the --allow-unauthenticated option to apt-get install.
I say 'Closes-Bug' below but I realize that this is a white lie. What
it fixes is only the Trove elements. The image build process uses
elements from other places (triple-o, for example). These can still
fail for the same reason.
There is a much bigger hammer that we can use if we need it, and that
is to throw the line 'APT::Get::AllowUnauthenticated "true";' into a
conf file in /etc/apt/apt.conf.d/.
If this hammer isn't big enough, we can revist later.
Change-Id: I009697332bb2a8e1e60b17c10944faed5c311da3
Closes-Bug:#1646856
Something appears to have caused the xenial guests to install all
python libraries into python 3.5 directories and therefore the guest
won't launch. This change forces pip2 and in theory should get around
that.
Moved Redis and PostgreSQL installs after the trove-dep ones.
Change-Id: I3bbe3bafa7ea3e627272103ac16a38f6a32a8a06
Partial-Bug: #1650382
Add the elements for building the MariaDB 10.1 guest image on Xenial.
A change was required to the service_candidates to allow for the
selection of the systemd unit file (mariadb.service) instead of the
old upstart script.
Change-Id: Iee0548e109f26c675b1410b6457b9e63ada9c0db
The main goal of this change is to add support for Xenial to
trove/integration and ensure the voting check jobs continue
to pass when switched to Xenial.
- It was decided that Trusty should continue to be supported
to aid in the developer transition to Xenial. Therefore,
the elements have been organized to accomplish this by making
"trusty" and "xenial" specific elements extend the already
existing "ubuntu" elements.
- We tried to do the initial work without impacting the core
Trove code therefore some choices were made - for example,
cluster delete doesn't work for PXC on Xenial (see [1]) so
the test that does this is skipped for PXC.
- Only Mysql, PXC, Postgresql and Redis were fixed for
Xenial and tested as these are the only voting jobs
currently. Future work should sort out the elements for the
rest of the datastores. Note that all of the datastores should
continue to function on Trusty.
- Previously, the "DISTRO" variable was hardcoded to "ubuntu".
This is no longer the case; DISTRO and RELEASE variables will
be automatically set to whatever the base OS is (for example,
if you are running trovestack on Xenial, DISTRO will be set
to "ubuntu" and RELEASE will be set to "xenial". These can
be overriden if needed.
[1] https://bugs.launchpad.net/trove/+bug/1645096
Change-Id: I8e1de6ef31f969ccee88c334a0d5ed03aabd1b51
Depends-On: I3831de12c999ef8818e80ecdb29f1d86ff8cd5c8
Attempting to build images fails now with an error because of a change
in the signing key for Percona packages.
Quick summary copied from [1]
Percona .deb packages are signed with a key that uses an algorithm now
considered weak. Starting with the next release, Debian and Ubuntu
packages are signed with a new key that uses the much stronger SHA-512
algorithm. All future package release will also contain the new
algorithm.
It’s important that you add the new key before the next release.
[1] https://www.percona.com/blog/2016/10/13/new-signing-key-for-percona-debian-and-ubuntu-packages/
Change-Id: I0420193982ebc5c9922eb388adb85da1423ab3f0
This commit changes trove-integration and the artifacts that were
brought over from that repository and brings them into the trove
repository.
The things (specifically) done in this commit are:
1. get rid of .gitreview; this is no longer a repository of its own,
it is a part of the trove repository.
2. Update the readme (README.md)
3. Make the elements work in this directory structure
4. Rename the elements and get rid of the name 'reddwarf', change the
name redstack to trovestack
5. Refactor all scripts and make them reflect the new directory
structure.
Change-Id: Iae67fe231b6c7964ca3f31fc593fc9fa4111d5be
This commit will merge into trove, the trove-integration tree as of
commit 9f92ca853f8aa2f72921e54682c918941a8f0919. This is in
preparation for making trove-integration go away.
In addition, it supresses any consideration of the integration
directory in the trove tox tests as it is understandably a small pile
of pooh and in need of much cleanup.
Change-Id: Ib7f2655c4c5ed86b5454708c04371ee55e37ec2d
Partially-Implements-Blueprint: eliminate-trove-integration-and-redstack
