Here, the "--drievaudit" option is added to swift-recon tool. This
feature gives the statistics for the system-wide drive errors flagged
by swift-drive-audit. An example of the output is as follows:
(verbose mode)
commit 7e64c811fe9ecae738474239a9f73e3c6f95ddea
Author: Alistair Coles <email address hidden>
Date: Wed Feb 25 17:33:44 2015 +0000
Enable in-process functional test policy to be configured
Currently the in-process tests build a 2 replica, 4 partition,
2 device object ring. This patch allows an alternative policy
and ring to be specified for testing via environment variables
that may optionally be set.
SWIFT_TEST_IN_PROCESS_CONF_DIR - This points the test setup to a
directory which may have a swift.conf file and ring file. The
test setup will then prefer these conf files over the samples
in '/etc'.
SWIFT_TEST_POLICY - This causes the in-process test to
use the specified policy from the swift.conf file and its
associated ring for testing (first copying the conf and ring file
and modifying device parameters to suit in-process testing). If
not set, the tests will use the default policy.
The in-process tests now start sufficient object servers for the
ring file being tested against.
This should allow in-process functional testing of various policies
and rings (e.g. EC policies) without needing to reconfigure an SAIO
for each test scenario.
The refactoring of the in_process test setup code should also
allow easier addition of other 'hard-coded' test policies/rings
in the future.
commit 9ae0a0702c4a32407b1d00e93bd1be01e2ec26bc
Author: Kota Tsuyuzaki <email address hidden>
Date: Fri Mar 20 00:59:15 2015 -0700
Fix a lack of method arguments at tempauth
This fixes a kind of trivial issue with TypeError caused by a lack
of method argument at calling.
When using 'Authorization' header with tempauth, tempauth calls
_get_user_groups with 3 arguments (includes self) on current code
but the method requires 4 arguments so it will go to fail with 500.
This patch fixes to take correct arguments and adds an unit test
for the case.
All non-keyword arguments are converted to strings and written to
the stream, the argument "sys.stderr" should be given keyword
"file" as keyword argument.
commit 99a3d1a1c5d9591eed5378cf83af78578b01b386
Author: Kota Tsuyuzaki <email address hidden>
Date: Fri Mar 13 04:39:16 2015 -0700
Fix the prefix of messages caputured from stderr
Swift caputures both sys.stdout and sys.stderr messages and
transfers them to syslog. However, whole of the messages
uses the "STDOUT:" prefix, currently.
It will be quite confusable for debugging purpose because we
cannot make sure whether "Swift didn't caputure stderr" or
"Swift captured stderr but didn't show it" when we want to log
some stderr messages.
This patch enables to allow a new prefix "STDERR:" and use it
for sys.stderr.
commit 16b435a4a8ae12f456a55872fd8ebe21b0841704
Author: Kota Tsuyuzaki <email address hidden>
Date: Mon Feb 23 00:26:30 2015 -0800
Fix ContainerBroker to use policy-0 in default
Fix ContainerBroker to initialize as policy-0 on policy_stat
table in default when storage_policy_index argument is NOT given.
Current ContainerBroker makes policy-1 stats in default because
the "None" value will be passed through to the last function of
db access query (i.e. a query like as "INSERT INTO policy_stat
(storage_policy_index) VALUES (None)" will appear) which results
in a row "(1, 0, 0)" (the first value is the policy index) by
the PRIMARY KEY constraint on sqlite.
In worst case, container db keeps two policies, and then, ContainerBroker.get_info
might return invalid (non-touched) policy_stat information as container information.
(See tests in detail)
When using ContainerBroker with no storage_policy_index argument,
it should always act policy-0 simply.
Note that this patch doesn't affect immediately Swift behavior because
current swift ensures to use policy-0 on "Container-Server" when invalid
policy (includes None) is given. However, we should recheck also in
ContainerBroker for safety to prevent the unfortunate behavior above.
Reviewed: https:/ /review. openstack. org/167429 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=5b11780a108 b6024310efa1b85 20b62ca1b318ef
Committed: https:/
Submitter: Jenkins
Branch: feature/ec
commit a288d05ca5d4c66 dab36df40b4216e 2ed87e5a91
Author: OpenStack Proposal Bot <email address hidden>
Date: Tue Mar 24 06:06:33 2015 +0000
Imported Translations from Transifex
For more information about this automatic import see: /wiki.openstack .org/wiki/ Translations/ Infrastructure
https:/
Change-Id: I6ae0dd0c34ac1d 7173acacdd0dd48 96619592e0c
commit 0a4679366210094 18a9c94f636b33b fb6d947a89
Author: Lorcan <email address hidden>
Date: Thu Mar 12 15:40:39 2015 +0000
Add swift-recon feature to track swift-drive-audit error count
This is a follow-on from a previous commit which added recon info /review. openstack. org/#/c/ 122468/).
for swift-drive-audit (https:/
Here, the "--drievaudit" option is added to swift-recon tool. This
feature gives the statistics for the system-wide drive errors flagged
by swift-drive-audit. An example of the output is as follows:
(verbose mode)
swift-recon --driveaudit -v ======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ====== ======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ====== 1.2.3.4: 6000/recon/ driveaudit: {'drive_ audit_errors' : 14} 1.2.3.5: 6000/recon/ driveaudit: {'drive_ audit_errors' : 0} 1.2.3.6: 6000/recon/ driveaudit: {'drive_ audit_errors' : 37} 1.2.3.7: 6000/recon/ driveaudit: {'drive_ audit_errors' : 101} 1.2.3.8: 6000/recon/ driveaudit: {'drive_ audit_errors' : 0} audit_errors] low: 0, high: 101, avg: 30.4, total: 152, Failed: 0.0%, no_result: 0, reported: 5 ======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ======
===
--> Starting reconnaissance on 5 hosts
===
[2015-03-11 17:13:39] Checking drive-audit errors
-> http://
-> http://
-> http://
-> http://
-> http://
[drive_
===
Change-Id: Ia16c52a9d613ee b3de1a5a428d88d d1233631912
commit 23d0842dec25090 5f68df601926ba8 228392b322
Author: Thiago da Silva <email address hidden>
Date: Tue Feb 17 16:55:34 2015 -0500
Refactoring the PUT method
Extracting large chunks of the PUT method into smaller
methods to improve maintainability and reuse of code.
Based on the work that Clay Gerrard started: /review. openstack. org/#/c/ 77812/
https:/
Co-Authored-By: Clay Gerrard <email address hidden>
Change-Id: Id479fc5b159a27 82361ac4a6e4a6d 8bbaee4fe85
Signed-off-by: Thiago da Silva <email address hidden>
commit c3d2602c60d8a21 8409c9f95bef252 e4811cbd29
Author: Mitsuhiro SHIGEMATSU <email address hidden>
Date: Sat Mar 21 08:42:23 2015 +0900
Fix typo in swift/test/ unit/account/ test_backend. py
Change-Id: I6cab1105990194 71b4005f1584fc2 6fa2a85d02e
commit 7e64c811fe9ecae 738474239a9f73e 3c6f95ddea
Author: Alistair Coles <email address hidden>
Date: Wed Feb 25 17:33:44 2015 +0000
Enable in-process functional test policy to be configured
Currently the in-process tests build a 2 replica, 4 partition,
2 device object ring. This patch allows an alternative policy
and ring to be specified for testing via environment variables
that may optionally be set.
SWIFT_ TEST_IN_ PROCESS_ CONF_DIR - This points the test setup to a
directory which may have a swift.conf file and ring file. The
test setup will then prefer these conf files over the samples
in '/etc'.
SWIFT_ TEST_POLICY - This causes the in-process test to
use the specified policy from the swift.conf file and its
associated ring for testing (first copying the conf and ring file
and modifying device parameters to suit in-process testing). If
not set, the tests will use the default policy.
The in-process tests now start sufficient object servers for the
ring file being tested against.
This should allow in-process functional testing of various policies
and rings (e.g. EC policies) without needing to reconfigure an SAIO
for each test scenario.
The refactoring of the in_process test setup code should also
allow easier addition of other 'hard-coded' test policies/rings
in the future.
Change-Id: I24f5a13de3d296 b400da1691dcb53 423a9f8a463
commit 9ae0a0702c4a324 07b1d00e93bd1be 01e2ec26bc
Author: Kota Tsuyuzaki <email address hidden>
Date: Fri Mar 20 00:59:15 2015 -0700
Fix a lack of method arguments at tempauth
This fixes a kind of trivial issue with TypeError caused by a lack
of method argument at calling.
When using 'Authorization' header with tempauth, tempauth calls user_groups with 3 arguments (includes self) on current code
_get_
but the method requires 4 arguments so it will go to fail with 500.
This patch fixes to take correct arguments and adds an unit test
for the case.
Closes- Bug:1434465
Change-Id: Ibf00c41fa8e5cf daf49bc4d571e57 5d7f229ebfe
commit 15b83f67d2fc664 5a5e68ce923ca9a 2d4d1b9805
Author: Alistair Coles <email address hidden>
Date: Wed Mar 18 12:43:03 2015 +0000
Test swift-object-info opens meta and ts files
Adds a unit test to verify the change made in [1], i.e. that object- info will read from .meta and .ts files as well
swift-
as .data files.
[1] change I43966d371218ad 39414e9282cde57 9e48370a2a7
Change-Id: I82dde36e3a96db 1a21cfe9a4cca0d 941e543dfd0
Related-Bug: 1425679
commit 3f1feaee4215dde 618431571983c64 d0290bbea0
Author: OpenStack Proposal Bot <email address hidden>
Date: Wed Mar 18 06:11:23 2015 +0000
Imported Translations from Transifex
For more information about this automatic import see: /wiki.openstack .org/wiki/ Translations/ Infrastructure
https:/
Change-Id: I2e0a6053fec208 b3eea9a68416fdc 616da0631a9
commit 3d3db0ab789f37a 69fc178eeb74c8c c61e4c6c1b
Author: Christian Schwede <email address hidden>
Date: Fri Mar 13 13:19:44 2015 +0000
Bump PyECLib version to >= 1.0.3
ECPyECLibEx ception has been removed in 1.0.1, among other
API/error handling enhancements in 1.0.3. Let's make sure
the right version is used.
Change-Id: Ie6e0c1b491017d d5096b14c23b610 abc22b03d6a
commit fdb2ec0cc742845 7a836a23f4b1834 8e037e6805
Author: Jiangmiao Gao <email address hidden>
Date: Mon Mar 16 23:30:37 2015 +0800
Add the missing "file" keyword for print
All non-keyword arguments are converted to strings and written to
the stream, the argument "sys.stderr" should be given keyword
"file" as keyword argument.
Change-Id: I1f9c4e41ed7a1d 3246eae9179fd92 21c0a834292
commit 51a8f9c64fa16a2 625066e406bb948 9aae67cb7f
Author: OpenStack Proposal Bot <email address hidden>
Date: Mon Mar 16 06:10:17 2015 +0000
Imported Translations from Transifex
For more information about this automatic import see: /wiki.openstack .org/wiki/ Translations/ Infrastructure
https:/
Change-Id: I0058932520e008 aa4bde7ce34d6c9 f25424684b4
commit 99a3d1a1c5d9591 eed5378cf83af78 578b01b386
Author: Kota Tsuyuzaki <email address hidden>
Date: Fri Mar 13 04:39:16 2015 -0700
Fix the prefix of messages caputured from stderr
Swift caputures both sys.stdout and sys.stderr messages and
transfers them to syslog. However, whole of the messages
uses the "STDOUT:" prefix, currently.
It will be quite confusable for debugging purpose because we
cannot make sure whether "Swift didn't caputure stderr" or
"Swift captured stderr but didn't show it" when we want to log
some stderr messages.
This patch enables to allow a new prefix "STDERR:" and use it
for sys.stderr.
Change-Id: Idf4649e9860b77 c3600a5cd0a3e0b d674b31fb4f
commit 9baafe7f305147c 70d004402ebb05a 22db85bc18
Author: Ricardo Ferreira <email address hidden>
Date: Fri Mar 6 21:18:48 2015 +0000
Allow swift-object-info to inspect .meta and .ts files
Removing the check for ".data" extension makes it check
*any* file for metadata, so it works with .meta and .ts
filetypes.
Change-Id: I43966d371218ad 39414e9282cde57 9e48370a2a7 Bug:1425679
Closes-
commit 16b435a4a8ae12f 456a55872fd8ebe 21b0841704
Author: Kota Tsuyuzaki <email address hidden>
Date: Mon Feb 23 00:26:30 2015 -0800
Fix ContainerBroker to use policy-0 in default
Fix ContainerBroker to initialize as policy-0 on policy_stat policy_ index argument is NOT given.
table in default when storage_
Current ContainerBroker makes policy-1 stats in default because policy_ index) VALUES (None)" will appear) which results
the "None" value will be passed through to the last function of
db access query (i.e. a query like as "INSERT INTO policy_stat
(storage_
in a row "(1, 0, 0)" (the first value is the policy index) by
the PRIMARY KEY constraint on sqlite.
In worst case, container db keeps two policies, and then, ContainerBroker .get_info
might return invalid (non-touched) policy_stat information as container information.
(See tests in detail)
When using ContainerBroker with no storage_ policy_ index argument,
it should always act policy-0 simply.
Note that this patch doesn't affect immediately Swift behavior because
current swift ensures to use policy-0 on "Container-Server" when invalid
policy (includes None) is given. However, we should recheck also in
ContainerBroker for safety to prevent the unfortunate behavior above.
Change-Id: If64f0c94c069a2 cc3140c99f21b8d 371c183e28a