summaryrefslogtreecommitdiff
path: root/requirements.txt
Commit message (Collapse)AuthorAgeFilesLines
* [goal] Deprecate the JSON formatted policy fileGhanshyam Mann2020-12-261-5/+5
| | | | | | | | | | | | | | | | | | As per the community goal of migrating the policy file the format from JSON to YAML[1], we need to do two things: 1. Change the default value of '[oslo_policy] policy_file'' config option from 'policy.json' to 'policy.yaml' with upgrade checks. 2. Deprecate the JSON formatted policy file on the project side via warning in doc and releasenotes. Also replace policy.json to policy.yaml ref from doc and tests. [1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html Change-Id: I790409da69df8479ad2fe152b15c32ba45067c23
* Support mysql 8.0Lingxian Kong2020-10-231-0/+1
| | | | | | | | | | | | | | | | | | | | * MySQL 5.7 and MySQL 8.0 need different percona-xtrabackup package version. Added Percona XtraBackup 8 support for MySQL 8.x backup and restore. * Construct different backup container image names for MySQL 5.7 and MySQL 8.0 based on the default option value. * Two docker images are uploaded for backup/restore: openstacktrove/db-backup-mysql5.7:1.0.0 and openstacktrove/db-backup-mysql8.0:1.0.0. Trove guest agent can automatically choose the approriate one based on the datastore version. * Added option "secure-file-priv=NULL" in MySQL config template to fix https://github.com/docker-library/mysql/issues/541. * Stop using IDENTIFIED BY in GRANT clause (also REVOKE). Starting with MySQL 8 creating a user implicitly using the GRANT command is not supported. Story: #2008275 Task: #41143 Change-Id: Ibdec63324b1b39ba9b8a38dbe529da17bbb06767
* Remove six usage and basestring checkwangzihao2020-10-161-1/+0
| | | | | | | | | | | | | | | | | | Remove basestring check. Remove six Replace the following items with Python 3 style code. - six.string_types - six.int2byte - six.indexbytes - six.add_metaclass - six.StringIO - six.text_type - six.integer_types - six.binary_type - six.BytesIO - six.reraise Change-Id: I4fb9033d152963c504ceb4d5c4d08f934ee4accb
* PostgreSQL supportLingxian Kong2020-09-011-0/+1
| | | | Change-Id: I7c77b210f5a1438739daebffea104eda3bda1a45
* Remove translation sections from setup.cfgmelissaml2020-05-271-1/+0
| | | | | | | These translation sections are not needed anymore, Babel can generate translation files without them. Change-Id: Ic81e52b5cf6c64d752358ab29a1f9a55bf25c88c
* Merge "Cap jsonschema 3.2.0 as the minimal version"Zuul2020-05-271-1/+1
|\
| * Cap jsonschema 3.2.0 as the minimal versionHervé Beraud2020-05-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1]. Python 3.8 is part of the victoria supported runtimes [2] so we now force to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure that everything works with python 3 in general. [1] https://github.com/Julian/jsonschema/pull/627 [2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria Change-Id: I511faa17b27eac827922957e4b36108da0dcd0c8
* | Datastore containerizationLingxian Kong2020-05-271-0/+1
|/ | | | | | | | | | | | | Significant changes: * Using docker image to install datastore. * Datastore image is common to different datastores. * Using backup docker image to do backup and restore. * Support MariaDB replication * Set most of the functional jobs as non-voting as nested virtualization is not supported in CI. Change-Id: Ia9c97a63a961eebc336b70d28dc77638144c1834
* Add python-troveclient in requirements.txtLingxian Kong2020-03-151-0/+1
| | | | Change-Id: I2bd0d81171df85c05423e19ab2e4afa82fcf880e
* [ussuri][goal] Drop python 2.7 support and testingGhanshyam Mann2019-12-051-1/+0
| | | | | | | | | | | | | | | | OpenStack is dropping the py2.7 support in ussuri cycle. Trove is ready with python 3 and ok to drop the python 2.7 support. Complete discussion & schedule can be found in - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html - https://etherpad.openstack.org/p/drop-python2-support Ussuri Communtiy-wide goal: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html Change-Id: I6b448747c873bfc9c0138c0f7e3ca67ddce02dee
* Fix tox debug modeMinmin Ren2019-05-131-1/+1
| | | | | | | | | | | | | - add oslotest in test-requirement.txt for fixing tox debug mode failed. - Update jsonschema/sphinx following the global-requirments.txt to pass zuul requirements-check job. (See: https://review.openstack.org/649789 https://review.opendev.org/#/c/657890/) Change-Id: I5f2cabc35415cac3c4e81afa9084cbd8677ccd22 Story: #2005615 Task: #30862
* Add trove-status upgrade check command frameworkwhoami-rajat2018-10-221-0/+1
| | | | | | | | | | | This adds basic framework for trove-status upgrade check commands. For now it has only "check_placeholder" check implemented. Real checks can be added to this tool in the future. Change-Id: Idfeab4c06cba6f841c17ab6e255a29e8707bfa55 Story: 2003657 Task: 26162
* Remove pycrypto from requirementsFan Zhang2018-06-141-1/+0
| | | | | | | | | | Remove pycrypto completely from requirements and fix the related tests. Closes-Bug: #1749574 Depends-On: I5c0c1a238023c116af5a84d899e629f1c7c3513f Change-Id: Ibfedd9e2ab0a5e78959108112f57103a089f02d1 Signed-off-by: Fan Zhang <zh.f@outlook.com>
* Merge "Switch to cryptography from pycrypto"Zuul2018-06-131-0/+1
|\
| * Switch to cryptography from pycryptoZhao Chao2018-06-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PyCrypto isn't active developed for quite a while, cryptography is recommended instead. This patch does this migration, but still keeps pycrytpo as a fallback solution. Random generation is also migrated to os.urandom as the cryptography document suggests: https://cryptography.io/en/latest/random-numbers/ Closes-Bug: #1749574 Change-Id: I5c0c1a238023c116af5a84d899e629f1c7c3513f Co-Authored-By: Fan Zhang <zh.f@outlook.com> Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
* | Fix lower-constraints and uncap eventlet10.0.0.0b1Zhao Chao2018-04-121-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | The 'requirements-check' gate job will validate requirements.txt and test-requirements.txt against lower-constraints.txt, i.e. the minimum version should match between lower-constraints and requirements. The change in lower-constraints.txt is produced by fix-lower-constraints.py script from the requirements repo, and 'enum34' is added mannually. This patch also include the commit about 'uncap eventlet' to make the 'requirements-check' actually working, because the change has been already merged in the requirements repo. The original commit message by Doug Hellmann is kept as below for futher referrence: We will manage the eventlet version using constraints now. See the thread starting at http://lists.openstack.org/pipermail/openstack-dev/2018-April/129096.html for more details. Co-Authored-By: Doug Hellmann <doug@doughellmann.com> Change-Id: I61a6904ea433e570420ccd46281162ff174a5737 Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
* Updated from global requirementsOpenStack Proposal Bot2018-03-261-1/+1
| | | | Change-Id: I9cae682c6b028752340dd0efb18a8980d12ec0b8
* Updated from global requirementsOpenStack Proposal Bot2018-03-151-1/+1
| | | | Change-Id: Ie5b55091c64b7672267cfb052bb3fe2243b95fba
* Updated from global requirementsOpenStack Proposal Bot2018-03-101-2/+2
| | | | Change-Id: I78782d3acb01c83b402a667905bfe7fbcbd10f4d
* Updated from global requirementsOpenStack Proposal Bot2018-01-161-2/+2
| | | | Change-Id: Ifbd10f0c2453f3de97240770cb141eda5d9397e3
* Updated from global requirementsOpenStack Proposal Bot2017-12-231-4/+4
| | | | Change-Id: I16e9d66f27bb0fb192804668dd33597b7167844f
* Updated from global requirementsOpenStack Proposal Bot2017-11-291-1/+1
| | | | Change-Id: I52601c01c210a2117e51e8e6f7b54416b493bef1
* Updated from global requirementsOpenStack Proposal Bot2017-11-161-1/+1
| | | | Change-Id: I8c7e2ae3d7e7d1e268f0dac430cd6ad51f66430a
* Updated from global requirementsOpenStack Proposal Bot2017-11-131-2/+2
| | | | Change-Id: I28fe5569a671fb65fcedb9821d13b171edf96b53
* Updated from global requirementsOpenStack Proposal Bot2017-10-231-23/+23
| | | | Change-Id: If697cc5a442bcd2c3720be28024642a97b773bea
* Updated from global requirementsOpenStack Proposal Bot2017-07-141-3/+3
| | | | Change-Id: I39a3891e016f4d8c1ee955c9670b3b11bead8988
* Updated from global requirementsOpenStack Proposal Bot2017-06-091-1/+1
| | | | Change-Id: Ib2f8f902b3b2be921510bd95c92fc0e997e1141f
* Updated from global requirementsOpenStack Proposal Bot2017-06-081-1/+1
| | | | Change-Id: I18fb55e558d11beb135d049ed8fb941f4cdca8fd
* Updated from global requirementsOpenStack Proposal Bot2017-06-081-3/+3
| | | | Change-Id: I6f1d1e967b7cb6993294f984c995051351a7fadd
* Updated from global requirementsOpenStack Proposal Bot2017-05-311-10/+9
| | | | Change-Id: Id6c203a23f3992a978730146e4ab4d28e43c3452
* Updated from global requirementsOpenStack Proposal Bot2017-04-241-1/+1
| | | | Change-Id: I80932d354d61591a8fc1be0a94ad4df1fa3e37a1
* Updated from global requirementsOpenStack Proposal Bot2017-04-071-9/+9
| | | | Change-Id: Ib95e50140f81e6630f45e98b62e9ac4fd87bd524
* we now need to have dib installed explicitlyAmrith Kumar2017-03-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dib is now going to have to be installed explicitly for us to actually run the gate. the old method of just cloning the repo won't work with dib v2. There are other ways to accomplish this but I'm choosing this approach knowing that it isn't ideal. First, what's the downside? This means that dib gets installed wherever trove control plane is installed. Is that necessary, NO. Is it the end of the world, NO. What are the options? - do what Octavia did and have a second requirements.txt in a folder called diskimage-create. Would this work, yes but we don't have such a mechanism right now and nothing would keep this requirements.txt file in sync with g-r that I know of. - hardcode the pip install command somewhere in the devstack plugin. yes, this would work but this would also have no ability to sync with g-r. So, while the solution proposed here isn't ideal, it strikes me as not bad, and much less risk than the other two options. We also need to figure out where the elements are and fix the path for disk-image-create. Some pep8 failures appears to have crept in as well, those are addressed. Change-Id: Ic64d91e082102057417995a0f6851d03b9e0ca74
* Updated from global requirementsOpenStack Proposal Bot2017-03-021-6/+6
| | | | Change-Id: I6d5572bb49cd5f245af59f87ce40f8f9a858e85d
* Updated from global requirements7.0.0.0b3OpenStack Proposal Bot2017-01-241-2/+2
| | | | Change-Id: I705dd4d0774dd373da725b7451de521a35a574f6
* Merge "Remove netifaces useless requirement"Jenkins2017-01-061-1/+0
|\
| * Remove netifaces useless requirementBertrand Lallau2017-01-041-1/+0
| | | | | | | | | | | | | | This patch cleans up the requirements.txt list to remove netifaces module actually replaced by oslo_utils. Change-Id: I556ff34c7740352a5da25d5e6b6556741b0ecd1f
* | Updated from global requirementsOpenStack Proposal Bot2017-01-051-1/+1
|/ | | | Change-Id: I6ab1bd4a064bf6a7cdc9a691fe3683ff7e51e3bb
* Updated from global requirementsOpenStack Proposal Bot2016-12-231-3/+3
| | | | Change-Id: Iac67b16cee3dbaa8f9f35a7c26eddc4eba14e562
* Updated from global requirementsOpenStack Proposal Bot2016-12-221-4/+4
| | | | Change-Id: Ife09e2bd4d02c115e6bed4da065a687218c44da6
* Add support for Oslo Policies to TrovePetr Malik2016-12-061-0/+1
| | | | | | | | | | | | | | | | | | The Oslo Policy library provides support for RBAC policy enforcement across all OpenStack services. Update the devstack plugin to copy the default policy file over to /etc/trove in the gate environments. Note: Not adding a rule for 'reset-password' instance action as that API was discontinued years ago and is now just waiting for removal (Bug: 1645866). DocImpact Co-Authored-By: Ali Adil <aadil@tesora.com> Change-Id: Ic443a4c663301840406cad537159eab7b0b5ed1c Implements: blueprint trove-policy
* Updated from global requirementsOpenStack Proposal Bot2016-11-301-1/+1
| | | | Change-Id: Ifbc96b3c70eccb840a21305872e16796b2fad794
* Updated from global requirementsOpenStack Proposal Bot2016-11-241-1/+1
| | | | Change-Id: Ia76fbc6a497156f031aee412407c6d3e1c85d6b0
* Updated from global requirementsOpenStack Proposal Bot2016-11-181-3/+3
| | | | Change-Id: Ib18d150231c79ee179f2efd86a762751ef0f32f6
* Merge "Multi-Region Support"Jenkins2016-11-181-0/+1
|\
| * Multi-Region SupportMorgan Jones2016-11-041-0/+1
| | | | | | | | | | | | | | | | | | | | This is an initial attempt at supporting multiple regions. It should handle the mechanics of deploying an instance/volume to a remote region. Additional changes may be required to allow the guest agent on the instance to connect back to the originating region. Co-Authored-By: Petr Malik <pmalik@tesora.com> Change-Id: I780de59dae5f90955139ab8393cf7d59ff3a21f6
* | Merge "Add pycrypto to the requirements file"Jenkins2016-11-101-0/+1
|\ \
| * | Add pycrypto to the requirements fileMatt Fischer2016-11-081-0/+1
| |/ | | | | | | | | | | | | pycrypto is missing from the requirements file but is used in several places. Change-Id: I96b6650c675f639cae3c0529ffcd8fee6a142176
* | Updated from global requirementsOpenStack Proposal Bot2016-11-081-2/+2
|/ | | | Change-Id: I938c6c50fb1c925f6fd201421b4af06fc09401e3
* Updated from global requirementsOpenStack Proposal Bot2016-10-271-2/+2
| | | | Change-Id: I37a40532c3bb3b3a148b9a98438696eba06ed2c3
View Lorry Controller Status