summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* changelog for queens backportsqueens-em2.17.1John Dickinson2019-02-132-0/+21
| | | | Change-Id: Ieaec857eba9321f2aefd63e3db9b413e8b35fcbb
* Merge "Use eventlet.patcher.original to get Python select module in get_hub" ↵Zuul2019-01-152-1/+42
|\ | | | | | | into stable/queens
| * Use eventlet.patcher.original to get Python select module in get_hubRomain de Joux2019-01-032-1/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | get_hub function was added in commit b155da42 with the idea to bypass eventlet automatic hub selection that prefers epoll if available by default. Since version 0.20.0 eventlet removed select.poll() function in its patched select module (eventlet.green.select), see: - https://github.com/eventlet/eventlet/commit/614a20462 So if eventlet monkey patching is done before a get_hub() call (as now in wsgi.py since commit c9410c7d) if we use 'import select' we get the eventlet version that don't have poll attribute. To prevent that we use eventlet.patcher.original function to get python select module to test if poll() is available on current platform. Change-Id: I69b3db3951b3d3b6583845978deb2883492e7f0f Closes-Bug: 1804627 (cherry picked from commit 4809884d9f20eb0be6df9840e4e6a75577fecc4c)
* | copy: Stop hanging per-request data on middleware instanceTim Burke2018-12-111-12/+9
|/ | | | | | Change-Id: Ib7b208669e900b84a7759819ef76b7b5b7ce8c9a Closes-Bug: 1774719 (cherry picked from commit 9ef2a828166aece6b374a97b0777b90c359fdebd)
* Move legacy-swift-dsvm-functional job in-treeTim Burke2018-09-084-20/+65
| | | | | | | | | | | Note that there's no swift-dsvm-functional-identity-v3-only because as of the Queens release, that's the *only* way Keystone gets deployed. Also, remove legacy jobs - see I8b353cba66b22de42ae42954ec44e5802224fc23. Depends-On: https://review.openstack.org/600916 Change-Id: I49d963b98f3df21fea0db24c83553ef873ad73c8 (cherry picked from commit 1d6521944597b0271817ca7eaebd51348df61e41)
* Merge "Attempt to fix pep8" into stable/queensZuul2018-08-310-0/+0
|\
| * Attempt to fix pep8Thiago da Silva2018-08-301-1/+1
| | | | | | | | | | | | | | | | | | Test B109 was removed from bandit in release 1.5.0[1] [1] - https://github.com/PyCQA/bandit/commit/d93eed549242013ca10f6fc990dd4234b69958f7 Change-Id: I57ea610b924c2140b7572762c44cbc6510d0f549 (cherry picked from commit fc04dc1cf20335b7efe9548c5b5243fae0b5a620)
* | import zuul job settings from project-configNguyen Hai2018-08-302-2/+90
|/ | | | | | | | | | | | | | | | | | | | This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. Because this patch is generated by a script, there may be some cosmetic changes to the layout of the YAML file(s) as the contents are normalized. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I9ad73265adc673d4ec4f7d412081e07c2cf55715 Story: #2002586 Task: #24337
* Merge "py36: Fix test_get_logger_sysloghandler_plumbing" into stable/queensZuul2018-08-031-1/+9
|\
| * py36: Fix test_get_logger_sysloghandler_plumbingTim Burke2018-07-241-1/+9
| | | | | | | | | | Change-Id: Ibdb9e2bbec1c962d930a3f69fc95a8c562ac13b7 (cherry picked from commit 1318bacc177d060f95b244cc2a1075fe43d4699a)
* | Fix SLO delete for accounts with non-ASCII names.Timur Alperovich2018-07-252-2/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If an account contains non-ASCII characters, currently SLO delete code will fail, as get_slo_segments() method receives a unicode object, but UTF-8 encoded account name. Attempting to concatenate the strings fails with a UnicodeError, as it tries to use the ASCII codec to decode the UTF-8 encoded account name. This patch allows accounts with non-ASCII characters in their names to delete SLOs. Change-Id: I619d41e62c16b25bd5f58d300a3dc71aa4dc75c2 (cherry picked from commit 0aad95005d03651da79071dd24354f0a54122ab6)
* | Merge "Update UPPER_CONSTRAINTS_FILE for stable/queens" into stable/queensZuul2018-07-241-1/+1
|\ \
| * | Update UPPER_CONSTRAINTS_FILE for stable/queensOpenStack Release Bot2018-02-071-1/+1
| | | | | | | | | | | | Change-Id: Ib23eb38b7850298499d2e91ff05a1371d1851994
* | | Deprecate auth_uri optionwangqi2018-05-155-6/+6
| |/ |/| | | | | | | | | | | | | | | | | Option auth_uri from group keystone_authtoken is deprecated in Queens [1]. Use option www_authenticate_uri from group keystone_authtoken. [1]https://review.openstack.org/#/c/508522/ Change-Id: I43bbc8b8c986e54a9a0829a0631d78d4077306f8 (cherry picked from commit 708b24aef11f8a78f5bbc7c17d3199f8f8fc74c5)
* | Imported Translations from ZanataOpenStack Proposal Bot2018-03-1410-1980/+130
| | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I57295c307ae1c80142a7da382aec9ea018a21213
* | Merge "Update install-guide URLs to point to stable/queens" into stable/queensZuul2018-03-087-11/+11
|\ \
| * | Update install-guide URLs to point to stable/queensTim Burke2018-02-087-11/+11
| |/ | | | | | | Change-Id: I7b2dd19f18cbfac3bc3ea763cd3333e3fb68f1cd
* | Fix flakey test_check_delete_headers_sets_delete_atTim Burke2018-03-011-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | It was rare (saw it once in 10k runs running locally), but it's ocassionally blown up in the gate [1]. With this, no fails locally even after 100k runs. [1] http://logs.openstack.org/11/538011/3/gate/swift-tox-py27/06c06f0/job-output.txt.gz#_2018-02-07_03_29_09_578389 Change-Id: I7701d2db2ec82b48559c5b74a2e08c4403fd5dec Related-Change: Ia126ad6988f387bbd2d1f5ddff0a56d457a1fc9b (cherry picked from commit 5b30c1f8115f2a85407b836be47d8376832b4f7b)
* | Move eventlet patch before call to loadappThiago da Silva2018-02-262-18/+15
|/ | | | | | | | | | | | | | | | | Ran into an eventlet bug[0] while integration Swift/Barbican in TripleO. It is very similar to a previous bug related to keystonemiddleware[1]. Suggestion from urllib3[2] is to patch eventlet "as early as possible". Traceback[3] shows that urllib3 is being imported before the eventlet patch, so moved the patch to before the loadapp call. [0] - http://paste.openstack.org/show/658046/ [1] - https://bugs.launchpad.net/swift/+bug/1662473 [2] - https://github.com/shazow/urllib3/issues/1104 [3] - https://gist.github.com/thiagodasilva/12dad7dc4f940b046dd0863b6f82a78b Change-Id: I74e580f31349bdefd187cc5d6770a7041a936bef (cherry picked from commit c9410c7dd482cc1faefdfd9d9c83d225e7d28e8f)
* Update .gitreview for stable/queensOpenStack Release Bot2018-02-071-0/+1
| | | | Change-Id: Ic8919696145e1829c283283f9847097e84301e51
* Merge "authors/changelog updates for 2.17.0 release"2.17.0Zuul2018-02-024-2/+234
|\
| * authors/changelog updates for 2.17.0 releaseJohn Dickinson2018-02-024-2/+234
| | | | | | | | Change-Id: I577d169022916676a20a9ac24c7cc7b63ae46778
* | Merge "Refactor expirer unit tests"Zuul2018-02-021-226/+127
|\ \ | |/ |/|
| * Refactor expirer unit testsKazuhiro MIYAHARA2018-01-311-226/+127
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In expirer's unit tests, fake InternalClient classes are defined and its instance simulates expirer's task queue behaviors. To make review for expirer's task queue update patch [1] easy, this patch refactors the implementation of the fake InternalClient classes. In this patch, unit tests are refactored by the following two approaches: #1: Summarizing duplicated fake InternalClient implementation #2: Make task account name variable The #2 approach is for multiple task accounts in [1]. The patch [1] will be rebased after this patch merged. [1]: https://review.openstack.org/#/c/517389 Change-Id: I10a7151cfdd43460ad38c47f672d3c31b77e7990
* | Merge "Remove some cruft from ratelimit tests"Zuul2018-02-011-39/+0
|\ \
| * | Remove some cruft from ratelimit testsSamuel Merritt2018-01-311-39/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tests were carefully setting up a mock for the 'http_connect' function in the ratelimit module, but there is no such function imported by the ratelimit module. As far as I can tell, this has been the case since the ratelimit middleware first appeared in 72d40bd (Mon Oct 4 14:11:48 2010 -0700). Change-Id: If047184c6435aa1647050f50b499dc9feff4318d
* | | Merge "Add support for data segments to SLO and SegmentedIterable"Zuul2018-02-016-144/+702
|\ \ \
| * | | Add support for data segments to SLO and SegmentedIterableJoel Wright2018-01-316-144/+702
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch updates the SLO middleware and SegmentedIterable to add support for user-specified inlined-data segments. Such segments will contain base64-encoded data to be added before/after an object-backed segment within an SLO. To accommodate the potential extra data we increase the default SLO maximum manifest size from 2MiB to 8MiB. The default maximum number of segments remains 1000, but this will only be enforced for object-backed segments. This patch is a prerequisite for a future patch enabling the download of large objects as tarballs. The TLO patch will be added as a dependent patch later. UpgradeImpact ============= During a rolling upgrade, an updated proxy may write a manifest that out-of-date proxies will not be able to read. This will resolve itself once the upgrade completes on all nodes. Change-Id: Ib8dc216a84d370e6da7d6b819af79582b671d699
* | | | Merge "Imported Translations from Zanata"Zuul2018-02-0114-355/+2224
|\ \ \ \
| * | | | Imported Translations from ZanataOpenStack Proposal Bot2018-01-3114-355/+2224
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I6e420ea5241838192571dd9d857cca4056699314
* | | | Merge "tempurl: Make the digest algorithm configurable"Zuul2018-02-016-82/+328
|\ \ \ \ | |/ / / |/| | |
| * | | tempurl: Make the digest algorithm configurableTim Burke2018-01-316-82/+328
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ... and add support for SHA-256 and SHA-512 by default. This allows us to start moving toward replacing SHA-1-based signatures. We've known this would eventually be necessary for a while [1], and earlier this year we've seen SHA-1 collisions [2]. Additionally, allow signatures to be base64-encoded, provided they start with a digest name followed by a colon. Trailing padding is optional for base64-encoded signatures, and both normal and "url-safe" modes are supported. For example, all of the following SHA-1 signatures are equivalent: da39a3ee5e6b4b0d3255bfef95601890afd80709 sha1:2jmj7l5rSw0yVb/vlWAYkK/YBwk= sha1:2jmj7l5rSw0yVb/vlWAYkK/YBwk sha1:2jmj7l5rSw0yVb_vlWAYkK_YBwk= sha1:2jmj7l5rSw0yVb_vlWAYkK_YBwk (Note that "normal" base64 encodings will require that you url encode all "+" characters as "%2B" so they aren't misinterpretted as spaces.) This was done for two reasons: 1. A hex-encoded SHA-512 is rather lengthy at 128 characters -- 88 isn't *that* much better, but it's something. 2. This will allow us to more-easily add support for different digests with the same bit length in the future. Base64-encoding is required for SHA-512 signatures; hex-encoding is supported for SHA-256 signatures so we aren't needlessly breaking from what Rackspace is doing. [1] https://www.schneier.com/blog/archives/2012/10/when_will_we_se.html [2] https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html Change-Id: Ia9dd1a91cc3c9c946f5f029cdefc9e66bcf01046 Related-Bug: #1733634
* | | | Merge "Replace Chinese punctuation with English punctuation"Zuul2018-01-315-86/+86
|\ \ \ \
| * | | | Replace Chinese punctuation with English punctuationgaofei2018-01-255-86/+86
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Curly quotes(Chinese punctuation) usually input from Chinese input method. When read from english context, it makes some confusion. Change-Id: Ibd50299ee287c56ec4759ea8ff53d47d006144f8
* | | | | Merge "Disallow fractional replicas in EC policies"Zuul2018-01-315-20/+77
|\ \ \ \ \
| * | | | | Disallow fractional replicas in EC policiesTim Burke2018-01-295-20/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: I873d7bf7de54e4b1dccdafc8a61f03c09a65dfbc Closes-Bug: 1554391 Closes-Bug: 1677547
* | | | | | Merge "Increase name-length limits for internal accounts"Zuul2018-01-314-35/+91
|\ \ \ \ \ \
| * | | | | | Increase name-length limits for internal accountsTim Burke2017-10-134-35/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Double account and container name-length limits for accounts starting with auto_create_account_prefix (default: '.') -- these are used internally by Swift, and may need to have some prefix followed by a user-settable value. Related-Change: Ice703dc6d98108ad251c43f824426d026e1f1d97 Change-Id: Ie1ce5ea49b06ab3002c0bd0fad7cea16cea2598e
* | | | | | | Merge "Remove the deprecated "giturl" option"Zuul2018-01-301-4/+0
|\ \ \ \ \ \ \ | |_|/ / / / / |/| | | | | |
| * | | | | | Remove the deprecated "giturl" optionzhang.lei2018-01-151-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From openstackdocstheme 1.18.0, valid Git URLs can be retrieved by openstackdocstheme[1], we do not need giturl option anymore. [1] https://review.openstack.org/532163 Change-Id: I579cebae6486d250915f936f0c1c61008471c089
* | | | | | | Merge "Fix bulk heartbeating when emitting XML"Zuul2018-01-272-7/+12
|\ \ \ \ \ \ \
| * | | | | | | Fix bulk heartbeating when emitting XMLTim Burke2017-10-102-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we would set eventlet.minimum_write_chunk_size *after* we emit the XML declaration. As a result, eventlet thinks it should buffer the entire response, rendering our attempts at heartbeating useless. Change-Id: Idb58c6cc982cc221fed5fc837afd06aa958d9ad4
* | | | | | | | Merge "Add container-reconciler to source doc tree"Zuul2018-01-261-0/+10
|\ \ \ \ \ \ \ \
| * | | | | | | | Add container-reconciler to source doc treeTim Burke2018-01-171-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change-Id: I98e7e55839e5697d975af0a4756fd09933af1c5f
* | | | | | | | | Merge "Add a small sleep when trying to predict X-Timestamp"Zuul2018-01-251-0/+4
|\ \ \ \ \ \ \ \ \ | |_|_|_|_|_|_|_|/ |/| | | | | | | |
| * | | | | | | | Add a small sleep when trying to predict X-TimestampTim Burke2017-12-181-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing test works fine if you're running the tests on an all-in-one, but is pretty brittle if you aren't running them on the one and only proxy-server they're hitting. Add 0.1s sleep to allow *some* clock slippage between client and server. Change-Id: Iacd08e9f703d08d0092b5e8eb53fe287ba1d1596
* | | | | | | | | Merge "Reset state every iteration to avoid stale reference"Zuul2018-01-251-1/+1
|\ \ \ \ \ \ \ \ \
| * | | | | | | | | Reset state every iteration to avoid stale referenceClay Gerrard2018-01-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you get a valid but unexpected response status you have to continue the loop. If you don't reset resp = None some kinds of exceptions might get re-raised as with the wrong error. Change-Id: I5751dfbc176155bea63103a64fd8d4db62323e60
* | | | | | | | | | Merge "Add pipeline modification test for previously-recommended pipelines"Zuul2018-01-241-0/+164
|\ \ \ \ \ \ \ \ \ \
| * | | | | | | | | | Add pipeline modification test for previously-recommended pipelinesTim Burke2018-01-091-0/+164
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This includes every pipeline from etc/proxy-server.conf-sample since we switched from swauth to tempauth in 1.4.1. As much as anything, I view this as a canary for auto-insertion changes, so we can (somewhat easily) see where new middlewares will be placed when upgrading from old swifts. Change-Id: I117937ab6ce28f3bc219e809f07b563c45fc486f Related-Change: I88678fddc7a25b0f065b33eb26047321d0db4d38
View Lorry Controller Status