This ensures that the options from the oslo.db library are picked up
by oslo-config-generator.
Also, update .gitignore so that the sample config file is ignored by
git.
Change-Id: I6ab051fd1c8034d9697b1caab9c1fda64a3275c3
1. app.wsgi is a python script and should be end with py extension.
2. Generate trove-wsgi script which is needed by kolla to support
https and ipv6.
3. Ignore build directory in git
4. update docs
Change-Id: Ibbd6ecb8db25aa3a443d3f526f4cf6d418eb26f3
A new entrypoint in setup.cfg and a config file are added for
using olso.policy helper script to generate the sample file.
A new tox target also is added to simplify the environment
setting up. Now policy sample file can be generated
automatically, so the in-repo sample file is no longer needed.
Co-Authored-By: Andrew Laski <andrew@lascii.com>
Partial-Implements: blueprint policy-in-code
Change-Id: Ic336fa154ccc05b5e9db3a8e751a484b1cc5aa9c
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
This change will help ignore all files which formated .coverage.*
files. These files will occured when perform following CLI:
tox -ecover
Change-Id: I8c75b4eefd562f1496b56818ca8df9a8ce067327
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
This commit cleans up a couple of issues with Trove's tox.ini.
1. something that was reported to me by Matthew Treinish who
observed that the tox jobs are oddly bundled together.
This is important because infra's reporting is unable to generate some
useful metrics and tracking of trove's jobs because of the way they
are tied together.
2. with the cleanup of docs, apidocs is no longer a directory and can
be cleaned up, similarly api-ref is a thing and should be handled in
.gitignore.
3. that py27 used to use testr, switched it to using ostestr. I've
retained it for coverage.
4. the sqlite db needs to be deleted between runs because we otherwise
fail (on a developer configuration) because some tests intentionally
appear to leave stuff around.
5. I've set all ostestr jobs to run with --serial because there are
clearly cases where multiple tests can attempt to setup the DB at the
same time and get into trouble. Till we can fix those (if we feel it
is worthwhile) it is more reliable to run ostestr in --serial mode. It
only takes 2.5 minutes. This includes the cover jobs which runs with
--no-parallel.
An infra change will follow that will enable testing jobs.
Change-Id: I0a971c6ef6c1a4669490f2aa0e67c795fe86e190
Closes-Bug: 1618098
Closes-Bug: 1618149
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
setuptools uses an .eggs folder as a cache to avoid multiple
downloads. git should ignore this directory as it will never
be added to the repo.
Change-Id: I49714b769ce42d45cf14c4c8f4c10ae40e638f4b
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
Reasons
- .gitignore contains IDE specific ignores
- IDE specific ignores should be setup using
global gitignore on local box.
for eg. create a .gitignore locally and use ...
git config --global core.excludesfile .gitignore
Changes
- Removed .idea generated by IntelliJ.
- Removed .DS_Store generated by Mac OS.
- Removed .project generated by Eclipse.
- Removed .pydevproject generated by PyDev.
- Removed atlassian-ide-plugin.xml
generated by Atlassian IDE.
Change-Id: I902e980834716edb8a30ca58df520fd3fc0f73aa
Closes-Bug: #1257279
This commit adds code to register taskmanager as a fake endpoint.
This allows the fake daemon to work again.
Fixes bug 1238901
Change-Id: Icb7c97cad3d76dc36a38126eb7f8b5929dc0d591
Added initial sphinx/docutils documentation for Trove. Also made
corresponding changes to setup.cfg so that OpenStack CI is able
to build the Trove developer docs.
Fixes blueprint: trove-dev-docs
Change-Id: I900ffd2c0b661fb7642fa06c08ee92892eb176f0
There was already an entry for reddwarf.egg*, but this is no
longer valid after some of the name changes.
Change-Id: Ib348879a2e22cb44dc50de34961ce18b1a2ce576
This will correctly report the status of the mysql process where the pid file is not in the default location
bug 1096212
Change-Id: Iab83b1c1c67baed7473373f978691d5895e5f4f0
* Updated logging,cfg,setup to new oslo
* Split out the paste ini from the conf files
* Modified reddwarf-api/server to use new modules
* Modified reddwarf-manage to use new cfg
* Added rpc helper for rpc services
* Modified reddwarf-taskmanager to use rpc helper
* Modified reddwarf-guestagent to use new rpc helper
* Fixed guestagent api to use rpc proxy
* Fixed taskmanager module to conform to new rpc
* Updated guestagent manager/pkg to use new rpc
* Updated api paste to use keystoneclient auth_token
* Updated managers to use periodic tasks
Implements: blueprint reddwarf/upgrade-oslo
Change-Id: I9ad1b441eca855a4304454014ae746ec51bef8f3
The tests come from the Reddwarf Integration repository. wsgi_intercept
is used to allow the test code to hit the server code directly. It also
properly sets up the SqlLite database before each run.
* Adds an "event simulator" which queues up functions that would
normally be spawned with eventlet. The various sleep functions are
then swapped with a method that runs these faux-events.
* Adds many of the Reddwarf Integration tests. The idea is these
could still run in a richer, real environment, but are running here
enables us to quickly check feature breaks for each commit and
lowers the learning curve necessary to test the API. The downside
is some of these tests still have artifacts of their origins, such
as (unused) classes to connect to MySQL databases. Some more work
will be necessary to separate the "real mode" functionality of these
tests further.
Implements: blueprint tox-tests
Change-Id: I9857f265c1cb46832906ef5e6a0c7bb4a092e637
* Changed reddwarf.conf.test to reflect local mode.
* Updated fake keystone. Any token is treated as the tenant ID, and any tenant id starting with "admin" is treated as an admin.
* update gitignore with log file from tests
* update the tenant id on the client
* change database to instance module
* added some logging in the api calls
* configuration of nova client values
* expanding the create instance api data input
* added all the fields to the view and added exceptions to be thrown correctly
* added a few things to .gitignore
* adding some testing tests
* Copying ssh keys from the host to the image
* Added a bootstrap_init.sh which does the scp work to the instance
* Finished the bootstrap.sh so it will upload to glance
* Added a service images table for identifing the current image on create
* Added some dummy guest-agent code for testing purposes
* Added a delete method, which is not finished
Takashi Kajinami