* Fix pep8: ambiguous variable name
* Install Python 3.7 for trove guest image. oslo.concurrency requires
python 3.6 or newer. See
https://bugs.launchpad.net/tripleo/+bug/1861803
* Mark tempest job non-voting temporarily because of some tempest bugs.
Change-Id: I6d316779cc7220a855ce187437056b667bbe1f75
- Execute test groups in serial to make sure no more than 2 database
instance are created at the same time.
- Remove some unneccesary tests
- Remove unneeded datastore, e.g. 'Test_Datastore_1'
- Remove unsupported trovestack subcommands
- Move unsupported DIB elements to the 'deprecated-elements' folder
- Decrease default value of 'agent_call_high_timeout' to 5min
- Add initial_deplay for pooling task
- Use socket file to connect with database instead of using localhost
IP
Change-Id: Ie5030a671fbeb453eafa6cbe04e08da7b52e33c9
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
Allow the cloud admin to control the security groups on the management
port of Trove instance, a new config option `management_security_groups`
is introduced for that purpose.
Change-Id: I4b22b87d37792be700d4ec7f78a7ea479ddb5814
Story: 2006466
Task: 36395
The service tenant deployment model means Trove creates most of the
resources(vm, volume, security group, etc.) relating to a database
instance in the Trove service tenant rather than the end user.
With this deployment model, most of the related resources behind the
scenes are invisible to the user, which is a more secure deployment
model for either private or public cloud provider.
DevStack should follow this model as it will be recommended for Trove
deployment in production.
Changes included in this patch that are necessary in order to make that
happen:
- Add 'admin' role to Trove service user(username: trove, project:
service) in DevStack.
- Create Trove management network resources for Trove service user in
DevStack.
- Enable Trove remote client configuration by default in DevStack.
- Mainly use alt_demo user in alt_demo project for integration tests,
config trove user as the admin role user in integration tests.
- Disable the module related tests(module_groups) for now because of no
use cases but need effort to fix all the failed tests in the service
tenant model.
Story: #2005445
Task: #30489
Change-Id: I2efb69d3d50344914a875b773f62a227dba2ccaf
Ubuntu Trusty continues to get MySQL 5.6.
The selection of the MySQL version is based on the version
of Ubuntu that is installed. If the script trovestack is
invoked on Xenial, the version that is chosen is 5.7. If
it is invoked on Trusty, then version 5.6 is chosen.
The only thing that is eliminated is the dubious combination
of MySQL 5.6 on Ubuntu Xenial. This combination is probably
not supported by Ubuntu as it is down level from their
standard offering is probably not tested anywhere.
Note Xenial does not provide the 5.6 version of mysql. This
was accomplished by initializing the Apt repo with the
Trusty software repository.
The size of the root file system is increased from 3 to 4 GBs
as the Mysql Xenial image does not fit in 3 GBs. This has an
impact on the flavors that are used by Trove for testing as the
name of the flavor includes the size of the root file system.
This is turn caused a change to each of the db specific test
config files as the trove falvors are referenced in them.
Change-Id: I4f4e497208b8f4728580e48239a8ae208e0a96dd
Issue 1:
The os-testr 1.0.0 release had a couple of required config changes due
to it's internal usage of stestr.
This change to stestr changed the way tests were discovered by
os-testr and as a result the unit test run was picking up tempest
tests.
A regex is added to the py3base environment call of ostestr because
the use of --serial and --blacklist-file together is broken in stestr
and adding the regex parameter allows the blacklist-file to be
processed. The stestr issue is documented here [1].
Issue 2:
Cache dirs for PKI tokens have been removed for all services in
devstack under I5680376e70e74882e9fdb87ee1b95d5f40570ad7.
We must also remove the use here to pass the right parameters to
configure_auth_token_middleware.
Issue 3:
Keystone V2 APIs have been removed. When creating Nova and Glance
clients, the test code was either hard coding v2 Keystone or not
providing enough information for the V3 auth.
Issue 4:
Oslo context has deprecated parameters such as 'tenant', has removed
them from its constructor and is using a rename decorator to handle
them. As such, the code and test case to check for unrecognized
parameters to TroveContext and Context is erroneously removing the
tenant parameter. Oslo context has also changed the from_dict method
since the original code to remove parameters was introduced into
Trove. The new method signature and code should already provide most
or all of the protections against incompatibility the original code
was attempting to provide. The fix for this issue is to change
TroveContext's from_dict method to use the kwargs to handle its own
__init__ parameters and be more in line with what Nova is doing in
its RequestContext subclass.
Issue 5:
Jobs run as jenkins on Zuul v2 but run as user zuul on Zuul v3.
Issue 6:
Ignore one case of pylint E1101 in the Ceilometer notification
code base.
[1] https://github.com/mtreinish/stestr/issues/103
Change-Id: Ic55187b0d73d4c572d7f8332882b4f455a6177c8
When running in the gate environment, there's no need to start
services. Also, it is harder to dertermine whether the services are
wsgi'ed or not and that has been causing intermittent gate failures.
Change-Id: Ibe6a96a9319becf2053d26180fb7e6835a4e3a97
Nova Networking was deprecated in Newton and some of the API calls
that were part of NN were still in use by Trove. With the arrival of
python-novaclient 8.0.0, this caused a failure.
Nova also deprecated the image pass through capability. The management
API uses some of that to test whether an image id is valid or
not. This change fixes the management API, and the attendant scenario
tests.
Depends-On: I142f97d691fa55e9824714c9c224f998ad72337e
Change-Id: I2f2a12207581a94fb8561a6d65a3a79b4a29b063
Closes-Bug: #1690936
Trove's test setup used identity_admin to get to keystone. This no
longer exists in the CI.
Change-Id: I6dc2e620631e124c7c69b45c6702da1cfaf091c2
Closes-Bug: 1688063
Trove's code was setup to use :5000 and :35357 for keystone's auth end
points. Change that to reflect the new settings that are /identity/
and /identity_admin/. See also [1]
[1] https://review.openstack.org/#/c/456344/
Change-Id: I3d6f6649430ee40879de15fee0b215dc32e8b666
Related: I46294fb24e3c23fa19fcfd7d6c9ee8a932354702
It seems as if the current image for MySQL is not too big for its
flavors of test.small-3. These need to be changed to test.small-4 to fix
the gate.
The defaults for PXC and Percona were also changes, just to make
sure (MariaDB was already there).
Change-Id: Id5be526a0418db5d00cbf5cbceb4993274989e72
Closes-Bug: #1656707
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