72 Commits

Author SHA1 Message Date
OpenStack Proposal Bot
ad52b42736 Updated from global requirements
Change-Id: Ia4c1d4198011f7f2664fc38f30d49ffa29693761
2016-05-14 03:56:46 +00:00
OpenStack Proposal Bot
74db0b6142 Updated from global requirements
Change-Id: I044fd9edd8859cbb532d344c48ca8902c711e3c8
2016-04-28 16:11:23 +00:00
OpenStack Proposal Bot
4ee0e8d618 Updated from global requirements
Change-Id: I2712cf7f0a99ea5f3415fb61f673c6c9b9c716c5
2016-04-10 18:22:36 +00:00
ricolin
8f630a8bda Add fixtures into test-requirements
We have broken gate, because we have no limitation to fixtures,
and the new version is incompatible to us.
We need to add fixtures into test-requirements to make
sure that we always up to date with global requirements.
Closes-Bug: #1567731

Change-Id: Ib0cac0c217db195ce3723cee3f09d26e6be9f0ea
2016-04-08 13:18:30 +08:00
OpenStack Proposal Bot
f1da4f0539 Updated from global requirements
Change-Id: I6d515ab8f3c1ab9f1ebef6eb1aeb36c827b5f6b8
2016-03-28 19:26:55 +00:00
Pavlo Shchelokovskyy
dd50ac6352 Create integration tests requirements on the fly
The problem of integration tests was that they use their own
requirements.txt that is unable to auto-sync with global requirements.

This patch removes dedicated requirements.txt and replaces it with a
stub file listing names (and possibly versions) of the packages needed.
Then a special script parses this stub file, and for every package
that is present in main project requirements files it pulls the versions
from main project requirements, generating and installing requirements
for the integration tests on the fly.

This will help keeping requirements for the integration tests always in
sync with main project requirements.

Change-Id: Ie79338cc10cc101fbf15b51c7923e3a7b8e4fbb4
Closes-Bug: #1490866
2016-03-25 13:40:50 +00:00
OpenStack Proposal Bot
fe58289da0 Updated from global requirements
Change-Id: I353e5d614df107067f6b249f225108a39fa0d439
2016-02-12 20:24:50 +00:00
OpenStack Proposal Bot
1d50cca3b2 Updated from global requirements
Change-Id: I53efb54055e3ea93d8a4d9b64a9f76197cf81a24
2016-02-10 21:53:09 +00:00
OpenStack Proposal Bot
9d5b67f103 Updated from global requirements
Change-Id: I71c62c9b5a2a67123aae6ed0c91ce242a6e56a15
2016-02-04 18:54:34 +00:00
OpenStack Proposal Bot
b445f42ff0 Updated from global requirements
Change-Id: Ic3cea0d80668a9c8dd5e4d131f0763b72e3445dd
2016-01-17 01:10:25 +00:00
OpenStack Proposal Bot
8cc95ba77d Updated from global requirements
Change-Id: Ia5cee4cab51ebbd8badd07092b70d27a7a12e39f
2015-12-03 15:03:08 +00:00
ricolin
46a102c2d1 Add reno for release notes management
Change-Id: I8ffe53af594150529c325814cf55812268193172
2015-12-01 15:04:39 +00:00
OpenStack Proposal Bot
d94b75032c Updated from global requirements
Change-Id: I3b7a451159937d50924b5b31330d91709d6c4f3e
2015-11-20 04:54:32 +00:00
Bertrand Lallau
85ad621c60 Move kombu as a test dependency only
oslo.messaging has kombu in its own requirements, so kombu
is not needed in requirements.txt.
Instead it was moved to test-requirements.txt file because
it is explicitly imported for functionnal tests.

Change-Id: I952263f1d2c61a3b700824914da499b1ece91b78
2015-11-17 23:07:17 +01:00
Sergey Kraynev
a7368fb68e Add testresources used by oslo.db fixture
If we use oslo.db fixtures, we'll need these 2 packages or
the next version of oslo.db release will break us.

Change-Id: I71f001c8b75ad52e68ccab8f07cd8946772fd03b
Closes-Bug: #1503501
2015-10-12 09:38:28 +00:00
Sirushti Murugesan
0d8dd9f06a Switch to mox3
mox is outdated and unmaintained. Switch to using mox3 instead.

Change-Id: I05ba92da6cbbf97c6a572c46e8d625c56b3a4db9
2015-10-02 13:05:51 +05:30
OpenStack Proposal Bot
a5b2f399f7 Updated from global requirements
Change-Id: I99cec6ea47a47af38ff2b842be870777a27d042e
2015-09-07 15:13:52 +00:00
Chandan Kumar
61a7bad996 Removing unused dependency: discover
Change-Id: I29718a45ce50d85b8425ea75795e7c1ccf53776e
2015-08-28 19:53:10 +05:30
OpenStack Proposal Bot
e809aad4ba Updated from global requirements
Change-Id: I0eb24197516cf19bf3019e8b7110ecfc3e30175d
2015-08-18 01:33:37 +00:00
OpenStack Proposal Bot
53c47c7047 Updated from global requirements
Change-Id: I3d5e510ff33d3a7fa4583b57b09a2f70af44c83f
2015-08-04 00:53:02 +00:00
OpenStack Proposal Bot
68cf89dff3 Updated from global requirements
Change-Id: I5b03ed38bee5ca00fbab6116cb9b2a4b0d1e677a
2015-07-31 16:36:54 +00:00
Jenkins
583fa18120 Merge "Move qpid-python to test-requirements" 2015-07-28 09:43:06 +00:00
OpenStack Proposal Bot
e46bb38f7e Updated from global requirements
Change-Id: I5b2d8cce3e53f0375ef2ffcd2775e2e9e613f7d6
2015-07-23 04:38:27 +00:00
OpenStack Proposal Bot
575094697f Updated from global requirements
Change-Id: I9bd04a4e0c97c6a5f58977146a8961f6fc8d2a3e
2015-07-18 16:04:35 +00:00
OpenStack Proposal Bot
09c8a4c159 Updated from global requirements
Change-Id: Id1d516edc130dbff51909daab03536017a471542
2015-07-15 07:33:24 +00:00
Jenkins
e8c661f736 Merge "tox environment for bandit" 2015-07-13 20:29:18 +00:00
Dirk Mueller
a5c7da576c Move qpid-python to test-requirements
qpid-python is only needed if the qpid backend is actually used.
when it is part of requirements.txt, loading of heat-engine
(which is done via stevedore) fails as it forcefully requires
qpid-python then. However heat seems to work just fine without it.

Change-Id: I1c49ec709995da145849d8616fe7207908637fb9
2015-07-13 10:21:36 +02:00
OpenStack Proposal Bot
5f57b514ca Updated from global requirements
Change-Id: I8e0be09fe385bb98cde61b091bb85cad9db31a03
2015-07-12 15:17:51 +00:00
Ryan Brown
5c91051200 tox environment for bandit
Add a tox environment for bandit so it can be run as a gate job
eventually. As-is, there are no high severity issues detected in heat.

Change-Id: Iab098a1d8bac5c95d67e6867ad5249987c3a786e
2015-07-08 09:13:35 -04:00
Sirushti Murugesan
cdfcd61a1d Override mox in sys.modules to mox3 in a py3 env
partial blueprint heat-python34-support

Change-Id: Iabb0435254ce07163f979160b312fc0e5d9e8a97
2015-07-02 11:41:49 +05:30
OpenStack Proposal Bot
995b32bdbb Updated from global requirements
Change-Id: I97e79c84b36b11962cf50a393f9645115b3886e7
2015-06-22 21:57:19 +00:00
Jeremy Stanley
f6e34c9017 Switch from MySQL-python to PyMySQL
As discussed in the Liberty Design Summit "Moving apps to Python 3"
cross-project workshop, the way forward in the near future is to
switch to the pure-python PyMySQL library as a default.

https://etherpad.openstack.org/p/liberty-cross-project-python3

Also set the OS_TEST_DBAPI_ADMIN_CONNECTION override variable so
that oslo.db opportunistic detection will know to use PyMySQL until
I12b32dc097a121bd43991bc38dd4d289b65e86c1 makes it the default
behavior.

Change-Id: I17e052215ce6e1604cdda848ccc20862452ccbc7
Co-Authored-By: Victor Sergeyev <vsergeyev@mirantis.com>
2015-06-18 18:05:44 +00:00
OpenStack Proposal Bot
97d1860782 Updated from global requirements
Change-Id: I2b39844045bb0d012ecfa6a2a6948bb60c1fbc20
2015-04-23 17:54:51 +00:00
Joe Gordon
3eb0fd1771 Move to hacking 0.10
Release notes: http://lists.openstack.org/pipermail/openstack-dev/2015-January/054165.html

Remove deleted hacking rules from toxini (H803)

Change-Id: I97965ec81e6eaf771f74b6044945f23fae395ba5
2015-03-24 11:46:35 -07:00
OpenStack Proposal Bot
23241cdb54 Updated from global requirements
Change-Id: I8ce8ac155c6254a71d032ea5a34c5a7c988f55a8
2015-03-21 00:08:40 +00:00
Julien Danjou
c889bf64ee Remove lockfile from requirements
It is not used anymore by Heat.

Change-Id: I1095084e7ecdaac5655f7f4cd78473be49d17d8a
2015-01-29 17:43:34 +01:00
Pavlo Shchelokovskyy
46e5897c3e Update oslo-hacking and disable failing checks
This also brings in newer versions of flake8, pyflakes and pep8,
with new and updated checks.
Some of them fail on our current code base, so first those failing are
disabled.
Most of them will be enabled one-by-one in subsequent patches.

Change-Id: Ib5fc4640b33c238ddb4e59a441c6710f607296b1
2015-01-05 11:58:01 +02:00
OpenStack Proposal Bot
6dc3f62e88 Updated from global requirements
Change-Id: I358cfce5ec233c17b128d3740d9e104178296ae2
2014-11-20 14:05:21 +00:00
OpenStack Proposal Bot
c9e338929b Updated from global requirements
Change-Id: I45ba9a7dc5a4575654363c5722b777f6ce5e4068
2014-11-18 19:39:01 +00:00
OpenStack Proposal Bot
e5c002d5dc Updated from global requirements
Change-Id: Iadaba02241b4f5fe36537288a321f2101d14c30c
2014-11-08 14:19:07 +00:00
OpenStack Proposal Bot
d6a2d3dbc3 Updated from global requirements
Change-Id: Ic65b03156f50b70045153938a3a7e35fa3856e66
2014-10-28 03:33:44 +00:00
OpenStack Proposal Bot
ce2cc9f6f6 Updated from global requirements
Change-Id: I692c2943b2d3edefd219051c38333bdb6a3c885c
2014-10-11 22:31:36 +00:00
Steve Baker
f3b8e93238 Support classes for heat integration tests
These support classes started as a forklift of the classes needed
to run tempest scenario orchestration tests.

The original tempest code has been pared back to provide the
small subset required by heat integration tests. From this point on
these support classes can evolve to the specific needs of the
integration tests.

There is some unused code (especially in remote_client) which has
been left in as it may become useful in the future, and is already
extremely well reviewed and tested from being developed for tempest.

The script heat_integrationtests/generate_sample.sh will generate
an up-to-date heat_integrationtests/heat_integrationtests.conf.sample
file which can be copied to
heat_integrationtests/heat_integrationtests.conf
to override default configuration values. A local ConfigOpts is created
for each test to avoid any potential interaction with heat's
global CONF. Configuration options for credentials default to
being sourced from the environment.

The default tox testenv now excludes tests in heat_integrationtests.
A new testenv called "integration" will only run tests in
heat_integrationtests.

Integration tests will fail if preconditions are not met, including
a keystone endpoint, credentials and glance containing the expected
named image.

Devstack gate hooks have been moved to heat_integrationtests now that
the name of the package has been decided.

Change-Id: I174429c16bb606c5c325ee8b62c6e600ea77a6e6
Partial-Blueprint: functional-tests
2014-09-24 09:02:20 +12:00
OpenStack Proposal Bot
e138570153 Updated from global requirements
Change-Id: Iafa34405877d0b8c7e91275a3edee87523c5fc16
2014-09-18 22:56:06 +00:00
OpenStack Proposal Bot
a13f486831 Updated from global requirements
Change-Id: I6efe9af9eb42420a7ff4a14adecba54d6fb170b3
2014-09-15 16:58:40 +00:00
Andreas Jaeger
3ebd84bf3c warn against sorting requirements
And do not check for sorted files.

Change-Id: I64ae9191863564e278a35d42ec9cd743a233028e
Closes-Bug: 1365061
2014-09-03 22:28:34 +02:00
Victor Sergeyev
1e1423e106 Run migration tests on PostgreSQL and MySQL
Refactored migration tests due to use OpportunisticTestCase.
This change allows tests use database ``openstack_citest`` only
for connection to the database backend - for each migration test
a new database, with a random name, will be created. This will avoid
migration tests of race conditions and reduce tests interaction.
Added MySQL-python and psycopg2 to test-requirements, because we need
some database connectors to run tests on PostgreSQL and MySQL.

``test_migrations.conf`` file was removed, because we create test
database for migration test, so we no longer need test database
credentials.

Some migrations scripts was modified to ensure, that they executed
with a single DB connection.

Removed get_table() method - we can use a similar function from
oslo.db.sqlalchemy.utils module.

This patch also add "forward compatibility" with the next version of oslo.db
- class BaseMigrationsTestCase was removed from master, so we should
avoid of it's usage and signature of method _walk_versions() from class
test_migrations.WalkVersionsMixin

Co-Authored-By: Roman Podoliaka <rpodolyaka@mirantis.com>

Change-Id: Ia503f01fdf2df00cce7212fcc9e0b6cc98ad6520
2014-08-19 08:24:28 +03:00
OpenStack Proposal Bot
b020f9be10 Updated from global requirements
Change-Id: I8947fe9a024ed9ac546473b21546584961b422e8
2014-07-02 23:54:00 +00:00
Steve Baker
c3f594242b Sync version of sphinx from requirements
This allows the xml builder to be invoked, which is only
available in sphinx 1.2

Change-Id: Ide5cc535d9f087a7674a90a45445eb7e6009f35a
2014-05-28 11:54:37 +12:00
huangtianhua
4b57d14559 Add glanceclient to heat
To enable implementation of a glance image resource, we first need to add
access to glanceclient in heat.

Change-Id: Ie0623e0307f6d3163ae584ceab89453f71f48053
Implements: blueprint glance-image
2014-05-08 10:11:28 +08:00