forked from openstack/swift
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGELOG
1683 lines (1062 loc) · 61.5 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
swift (2.6.0)
* Dependency changes
- Updated minimum version of eventlet to 0.17.4 to support IPv6.
- Updated the minimum version of PyECLib to 1.0.7.
* The ring rebalancing algorithm was updated to better handle edge cases
and to give better (more balanced) rings in the general case. New rings
will have better initial placement, capacity adjustments will move less
data for better balance, and existing rings that were imbalanced should
start to become better balanced as they go through rebalance cycles.
* Added container and account reverse listings.
A GET request to an account or container resource with a "reverse=true"
query parameter will return the listing in reverse order. When
iterating over pages of reverse listings, the relative order of marker
and end_marker are swapped.
* Storage policies now support having more than one name.
This allows operators to fix a typo without breaking existing clients,
or, alternatively, have "short names" for policies. This is implemented
with the "aliases" config key in the storage policy config in
swift.conf. The aliases value is a list of names that the storage
policy may also be identified by. The storage policy "name" is used to
report the policy to users (eg in container headers). The aliases have
the same naming restrictions as the policy's primary name.
* The object auditor learned the "interval" config value to control the
time between each audit pass.
* `swift-recon --all` now includes the config checksum check.
* `swift-init` learned the --kill-after-timeout option to force a service
to quit (SIGKILL) after a designated time.
* `swift-recon` now correctly shows timestamps in UTC instead of local
time.
* Fixed bug where `swift-ring-builder` couldn't select device id 0.
* Documented the previously undocumented
`swift-ring-builder pretend_min_part_hours_passed` command.
* The "node_timeout" config value now accepts decimal values.
* `swift-ring-builder` now properly removes devices with zero weight.
* `swift-init` return codes are updated via "--strict" and "--non-strict"
options. Please see the usage string for more information.
* `swift-ring-builder` now reports the min_part_hours lockout time
remaining
* Container sync has been improved to more quickly find and iterate over
the containers to be synced. This reduced server load and lowers the
time required to see data propagate between two clusters. Please see
http://swift.openstack.org/overview_container_sync.html for more details
about the new on-disk structure for tracking synchronized containers.
* A container POST will now update that container's put-timestamp value.
* TempURL header restrictions are now exposed in /info.
* Error messages on static large object manifest responses have been
greatly improved.
* Closed a bug where an unfinished read of a large object would leak a
socket file descriptor and a small amount of memory. (CVE-2016-0738)
* Fixed an issue where a zero-byte object PUT with an incorrect Etag
would return a 503.
* Fixed an error when a static large object manifest references the same
object more than once.
* Improved performance of finding handoff nodes if a zone is empty.
* Fixed duplication of headers in Access-Control-Expose-Headers on CORS
requests.
* Fixed handling of IPv6 connections to memcache pools.
* Continued work towards python 3 compatibility.
* Various other minor bug fixes and improvements.
swift (2.5.0, OpenStack Liberty)
* Added the ability to specify ranges for Static Large Object (SLO)
segments.
* Replicator configs now support an "rsync_module" value to allow
for per-device rsync modules. This setting gives operators the
ability to fine-tune replication traffic in a Swift cluster and
isolate replication disk IO to a particular device. Please see
the docs and sample config files for more information and
examples.
* Significant work has gone in to testing, fixing, and validating
Swift's erasure code support at different scales.
* Swift now emits StatsD metrics on a per-policy basis.
* Fixed an issue with Keystone integration where a COPY request to a
service account may have succeeded even if a service token was not
included in the request.
* Ring validation now warns if a placement partition gets assigned to the
same device multiple times. This happens when devices in the ring are
unbalanced (e.g. two servers where one server has significantly more
available capacity).
* Various other minor bug fixes and improvements.
swift (2.4.0)
* Dependency changes
- Added six requirement. This is part of an ongoing effort to add
support for Python 3.
- Dropped support for Python 2.6.
* Config changes
- Recent versions of Python restrict the number of headers allowed in a
request to 100. This number may be too low for custom middleware. The
new "extra_header_count" config value in swift.conf can be used to
increase the number of headers allowed.
- Renamed "run_pause" setting to "interval" (current configs with
run_pause still work). Future versions of Swift may remove the
run_pause setting.
* Versioned writes middleware
The versioned writes feature has been refactored and reimplemented as
middleware. You should explicitly add the versioned_writes middleware to
your proxy pipeline, but do not remove or disable the existing container
server config setting ("allow_versions"), if it is currently enabled.
The existing container server config setting enables existing
containers to continue being versioned. Please see
http://swift.openstack.org/middleware.html#how-to-enable-object-versioning-in-a-swift-cluster
for further upgrade notes.
* Allow 1+ object-servers-per-disk deployment
Enabled by a new > 0 integer config value, "servers_per_port" in the
[DEFAULT] config section for object-server and/or replication server
configs. The setting's integer value determines how many different
object-server workers handle requests for any single unique local port
in the ring. In this mode, the parent swift-object-server process
continues to run as the original user (i.e. root if low-port binding
is required), binds to all ports as defined in the ring, and forks off
the specified number of workers per listen socket. The child, per-port
servers drop privileges and behave pretty much how object-server workers
always have, except that because the ring has unique ports per disk, the
object-servers will only be handling requests for a single disk. The
parent process detects dead servers and restarts them (with the correct
listen socket), starts missing servers when an updated ring file is
found with a device on the server with a new port, and kills extraneous
servers when their port is found to no longer be in the ring. The ring
files are stat'ed at most every "ring_check_interval" seconds, as
configured in the object-server config (same default of 15s).
In testing, this deployment configuration (with a value of 3) lowers
request latency, improves requests per second, and isolates slow disk
IO as compared to the existing "workers" setting. To use this, each
device must be added to the ring using a different port.
* Do container listing updates in another (green)thread
The object server has learned the "container_update_timeout" setting
(with a default of 1 second). This value is the number of seconds that
the object server will wait for the container server to update the
listing before returning the status of the object PUT operation.
Previously, the object server would wait up to 3 seconds for the
container server response. The new behavior dramatically lowers object
PUT latency when container servers in the cluster are busy (e.g. when
the container is very large). Setting the value too low may result in a
client PUT'ing an object and not being able to immediately find it in
listings. Setting it too high will increase latency for clients when
container servers are busy.
* TempURL fixes (closes CVE-2015-5223)
Do not allow PUT tempurls to create pointers to other data.
Specifically, disallow the creation of DLO object manifests via a PUT
tempurl. This prevents discoverability attacks which can use any PUT
tempurl to probe for private data by creating a DLO object manifest and
then using the PUT tempurl to head the object.
* Ring changes
- Partition placement no longer uses the port number to place
partitions. This improves dispersion in small clusters running one
object server per drive, and it does not affect dispersion in
clusters running one object server per server.
- Added ring-builder-analyzer tool to more easily test and analyze a
series of ring management operations.
- Stop moving partitions unnecessarily when overload is on.
* Significant improvements and bug fixes have been made to erasure code
support. This feature is suitable for beta testing, but it is not yet
ready for broad production usage.
* Bulk upload now treats user xattrs on files in the given archive as
object metadata on the resulting created objects.
* Emit warning log in object replicator if "handoffs_first" or
"handoff_delete" is set.
* Enable object replicator's failure count in swift-recon.
* Added storage policy support to dispersion tools.
* Support keystone v3 domains in swift-dispersion.
* Added domain_remap information to the /info endpoint.
* Added support for a "default_reseller_prefix" in domain_remap
middleware config.
* Allow SLO PUTs to forgo per-segment integrity checks. Previously, each
segment referenced in the manifest also needed the correct etag and
bytes setting. These fields now allow the "null" value to skip those
particular checks on the given segment.
* Allow rsync to use compression via a "rsync_compress" config. If set to
true, compression is only enabled for an rsync to a device in a
different region. In some cases, this can speed up cross-region
replication data transfer.
* Added time synchronization check in swift-recon (the --time option).
* The account reaper now runs faster on large accounts.
* Various other minor bug fixes and improvements.
swift (2.3.0, OpenStack Kilo)
* Erasure Code support (beta)
Swift now supports an erasure-code (EC) storage policy type. This allows
deployers to achieve very high durability with less raw capacity as used
in replicated storage. However, EC requires more CPU and network
resources, so it is not good for every use case. EC is great for storing
large, infrequently accessed data in a single region.
Swift's implementation of erasure codes is meant to be transparent to
end users. There is no API difference between replicated storage and
EC storage.
To support erasure codes, Swift now depends on PyECLib and
liberasurecode. liberasurecode is a pluggable library that allows for
the actual EC algorithm to be implemented in a library of your choosing.
As a beta release, EC support is nearly fully feature complete, but it
is lacking support for some features (like multi-range reads) and has
not had a full performance characterization. This feature relies on
ssync for durability. Deployers are urged to do extensive testing and
not deploy production data using an erasure code storage policy.
Full docs are at http://swift.openstack.org/overview_erasure_code.html
* Add support for container TempURL Keys.
* Make more memcache options configurable. connection_timeout,
pool_timeout, tries, and io_timeout are all now configurable.
* Swift now supports composite tokens. This allows another service to
act on behalf of a user, but only with that user's consent.
See http://swift.openstack.org/overview_auth.html for more details.
* Multi-region replication was improved. When replicating data to a
different region, only one replica will be pushed per replication
cycle. This gives the remote region a chance to replicate the data
locally instead of pushing more data over the inter-region network.
* Internal requests from the ratelimit middleware now properly log a
swift_source. See http://swift.openstack.org/logs.html for details.
* Improved storage policy support for quarantine stats in swift-recon.
* The proxy log line now includes the request's storage policy index.
* Ring checker has been added to swift-recon to validate if rings are
built correctly. As part of this feature, storage servers have learned
the OPTIONS verb.
* Add support of x-remove- headers for container-sync.
* Rings now support hostnames instead of just IP addresses.
* Swift now enforces that the API version on a request is valid. Valid
versions are configured via the valid_api_versions setting in swift.conf
* Various other minor bug fixes and improvements.
swift (2.2.2)
* Data placement changes
This release has several major changes to data placement in Swift in
order to better handle different deployment patterns. First, with an
unbalance-able ring, less partitions will move if the movement doesn't
result in any better dispersion across failure domains. Also, empty
(partition weight of zero) devices will no longer keep partitions after
rebalancing when there is an unbalance-able ring.
Second, the notion of "overload" has been added to Swift's rings. This
allows devices to take some extra partitions (more than would normally
be allowed by the device weight) so that smaller and unbalanced clusters
will have less data movement between servers, zones, or regions if there
is a failure in the cluster.
Finally, rings have a new metric called "dispersion". This is the
percentage of partitions in the ring that have too many replicas in a
particular failure domain. For example, if you have three servers in a
cluster but two replicas for a partition get placed onto the same
server, that partition will count towards the dispersion metric. A
lower value is better, and the value can be used to find the proper
value for "overload".
The overload and dispersion metrics have been exposed in the
swift-ring-build CLI tools.
See http://docs.openstack.org/developer/swift/overview_ring.html
for more info on how data placement works now.
* Improve replication of large out-of-sync, out-of-date containers.
* Added console logging to swift-drive-audit with a new log_to_console
config option (default False).
* Optimize replication when a device and/or partition is specified.
* Fix dynamic large object manifests getting versioned. This was not
intended and did not work. Now it is properly prevented.
* Fix the GET's response code when there is a missing segment in a
large object manifest.
* Change black/white listing in ratelimit middleware to use sysmeta.
Instead of using the config option, operators can set
"X-Account-Sysmeta-Global-Write-Ratelimit: WHITELIST" or
"X-Account-Sysmeta-Global-Write-Ratelimit: BLACKLIST" on an account to
whitelist or blacklist it for ratelimiting. Note: the existing
config options continue to work.
* Use TCP_NODELAY on outgoing connections.
* Improve object-replicator startup time.
* Implement OPTIONS verb for storage nodes.
* Various other minor bug fixes and improvements.
swift (2.2.1)
* Swift now rejects object names with Unicode surrogates.
* Return 403 (instead of 413) on unauthorized upload when over account
quota.
* Fix a rare condition when a rebalance could cause swift-ring-builder
to crash. This would only happen on old ring files when "rebalance"
was the first command run.
* Storage node error limits now survive a ring reload.
* Speed up reading and writing xattrs for object metadata by using larger
xattr value sizes. The change is moving from 254 byte values to 64KiB
values. There is no migration issue with this.
* Deleted containers beyond the reclaim age are now properly reclaimed.
* Full Simplified Chinese translation (zh_CN locale) for errors and logs.
* Container quota is now properly enforced during cross-account COPY.
* ssync replication now properly uses the configured replication_ip.
* Fixed issue were ssync did not replicate custom object headers.
* swift-drive-audit now has the 'unmount_failed_device' config option
(default to True) that controls if the process will unmount failed
drives or not.
* swift-drive-audit will now dump drive error rates to a recon file.
The file location is controlled by the 'recon_cache_path' config value
and it includes each drive and its associated number of errors.
* When a filesystem does't support xattr, the object server now returns
a 507 Insufficient Storage error to the proxy server.
* Clean up empty account and container partitions directories if they
are empty. This keeps the system healthy and prevents a large number
of empty directories from slowing down the replication process.
* Show the sum of every policy's amount of async pendings in swift-recon.
* Various other minor bug fixes and improvements.
swift (2.2.0, OpenStack Juno)
* Added support for Keystone v3 auth.
Keystone v3 introduced the concept of "domains" and user names
are no longer unique across domains. Swift's Keystone integration
now requires that ACLs be set on IDs, which are unique across
domains, and further restricts setting new ACLs to only use IDs.
Please see http://swift.openstack.org/overview_auth.html for
more information on configuring Swift and Keystone together.
* Swift now supports server-side account-to-account copy. Server-
side copy in Swift requires the X-Copy-From header (on a PUT)
or the Destination header (on a COPY). To initiate an account-to-
account copy, the existing header value remains the same, but the
X-Copy-From-Account header (on a PUT) or the Destination-Account
(on a COPY) are used to indicate the proper account.
* Limit partition movement when adding a new placement tier.
When adding a new placement tier (server, zone, or region), Swift
previously attempted to move all placement partitions, regardless
of the space available on the new tier, to ensure the best possible
durability. Unfortunately, this could result in too many partitions
being moved all at once to a new tier. Swift's ring-builder now
ensures that only the correct number of placement partitions are
rebalanced, and thus makes adding capacity to the cluster more
efficient.
* Per storage policy container counts are now reported in an
account response headers.
* Swift will now reject, with a 4xx series response, GET requests
with more than 50 ranges, more than 3 overlapping ranges, or more
than 8 non-increasing ranges.
* The bind_port config setting is now required to be explicitly set.
* The object server can now use splice() for a zero-copy GET
response. This feature is enabled with the "splice" config variable
in the object server config and defaults to off. Also, this feature
only works on recent Linux kernels (AF_ALG sockets must be
supported). A zero-copy GET response can significantly reduce CPU
requirements for object servers.
* Added "--no-overlap" option to swift-dispersion populate so that
multiple runs of the tool can add coverage without overlapping
existing monitored partitions.
* swift-recon now supports filtering by region.
* Various other minor bug fixes and improvements.
swift (2.1.0)
* swift-ring-builder placement was improved to allow gradual addition
of new regions without causing a massive migration of data to the new
region. The change was to prefer device weight first, then look at
failure domains.
* Logging updates
- Eliminated "Handoff requested (N)" log spam.
- Added process pid to the end of storage node log lines.
- Container auditor now logs a warning if the devices path contains a
non-directory.
- Object daemons now send a user-agent string with their full name.
* 412 and 416 responses are no longer tracked as errors in the StatsD
messages from the backend servers.
* Parallel object auditor
The object auditor can now be controlled with a "concurrency" config
value that allows multiple auditor processes to run at once. Using
multiple parallel auditor processes can speed up the overall auditor
cycle time.
* The object updater will now concurrently update each necessary node
in a new greenthread.
* TempURL updates
- The default allowed methods have changed to also allow POST and
DELETE. The new default list is "GET HEAD PUT POST DELETE".
- TempURLs for POST now also allow HEAD, matching existing GET and PUT
functionality.
- Added filename*= support to TempURL Content-Disposition response
header.
* X-Delete-At/After can now be used with the FormPost middleware.
* Make swift-form-signature output a sample form.
* Add v2 API to list endpoints middleware
The new API adds better support for storage policies and changes the
response from a list of backend urls to a dictionary with the keys
"endpoints" and "headers". The endpoints key contains a list of the
backend urls, and the headers key is a dictionary of headers to send
along with the backend request.
* Added allow_account_management and account_autocreate values to /info
responses.
* Enable object system metadata on PUTs (Note: POST support is ongoing).
* Various other minor bug fixes and improvements.
swift (2.0.0)
* Storage policies
Storage policies allow deployers to configure multiple object rings
and expose them to end users on a per-container basis. Deployers
can create policies based on hardware performance, regions, or other
criteria and independently choose different replication factors on
them. A policy is set on a Swift container at container creation
time and cannot be changed.
Full docs are at http://swift.openstack.org/overview_policies.html
* Add profiling middleware in Swift
The profile middleware provides a tool to profile Swift
code on the fly and collects statistical data for performance
analysis. A native simple Web UI is also provided to help
query and visualize the data.
* Add --quoted option to swift-temp-url
* swift-recon now supports checking the md5sum of swift.conf, which
helps deployers verify configurations are consistent across a cluster.
* Users can now set the transaction id suffix by passing in
a value in the X-Trans-Id-Extra header.
* New log_max_line_length option caps the maximum length of a log line.
* Support If-[Un]Modified-Since for object HEAD
* Added missing constraints and ratelimit parameters to /info
* Add ability to remove subsections from /info
* Unify logging for account, container, and object server processes
to provide a consistent message format. This change reorders the
fields logged for the account server.
* Add targeted config loading to swift-init. This allows an easier
and more explicit way to tell swift-init to run specific server
process configurations.
* Properly quote www-authenticate (CVE-2014-3497)
* Fix logging issue when services stop on py26.
* Change the default logged length of the auth token to 16.
* Explicitly set permissions on generated ring files to 0644
* Fix file uploads larger than 2GiB in the formpost feature
* Fixed issue where large objects would fail to download if the
auth token expired partway through the download
* Various other minor bug fixes and improvements
swift (1.13.1, OpenStack Icehouse)
* Change the behavior of CORS responses to better match the spec
A new proxy config variable (strict_cors_mode, default to True)
has been added. Setting it to False keeps the old behavior. For
an overview of old versus new behavior, please see
https://review.openstack.org/#/c/69419/
* Invert the responsibility of the two instances of proxy-logging in
the proxy pipeline
The first proxy_logging middleware instance to receive a request
in the pipeline marks that request as handling it. So now, the
left most proxy_logging middleware handles logging for all
client requests, and the right most proxy_logging middleware
handles all other requests initiated from within the pipeline to
its left. This fixes logging related to large object
requests not properly recording bandwidth.
* Added swift-container-info and swift-account-info tools
* Allow specification of object devices for audit
* Dynamic large object COPY requests with ?multipart-manifest=get
now work as expected
* When a client is downloading a large object and one of the segment
reads gets bad data, Swift will now immediately abort the request.
* Fix ring-builder crash when a ring partition was assigned to a
deleted device, zero-weighted device, and normal device
* Make probetests work with conf.d configs
* Various other minor bug fixes and improvements.
swift (1.13.0)
* Account-level ACLs and ACL format v2
Accounts now have a new privileged header to represent ACLs or
any other form of account-level access control. The value of
the header is a JSON dictionary string to be interpreted by the
auth system. A reference implementation is given in TempAuth.
Please see the full docs at
http://swift.openstack.org/overview_auth.html
* Added a WSGI environment flag to stop swob from always using
absolute location. This is useful if middleware needs to use
out-of-spec Location headers in a response.
* Container sync proxies now support simple load balancing
* Config option to lower the timeout for recoverable object GETs
* Add a way to ratelimit all writes to an account
* Allow multiple storage_domain values in cname_lookup middleware
* Moved all DLO functionality into middleware
The proxy will automatically insert the dlo middleware at an
appropriate place in the pipeline the same way it does with the
gatekeeper middleware. Clusters will still support DLOs after upgrade
even with an old config file that doesn't mention dlo at all.
* Remove python-swiftclient dependency
* Add secondary groups to process user during privilege escalation
* When logging request headers, it is now possible to specify
specifically which headers should be logged
* Added log_requests config parameter to account and container servers
to match the parameter in the object server. This allows a deployer
to turn off log messages for these processes.
* Ensure swift.source is set for DLO/SLO requests
* Fixed an issue where overwriting segments in a dynamic manifest
could cause issues on pipelined requests.
* Properly handle COPY verb in container quota middleware
* Improved StaticWeb 404 error message on web-listings and index
* Various other minor bug fixes and improvements.
swift (1.12.0)
* Several important pieces of information have been added to /info:
- Configured constraints are included and allow a client to discover
the limits on names and object sizes that the cluster supports.
- The supported tempurl methods are now included.
- Static large object constraints are now included.
* The Last-Modified header value returned will now be the object's
timestamp rounded up to the next second. This allows subsequent
requests with If-[un]modified-Since to use the Last-Modified
value as expected.
* Non-integer values for if-delete-at headers will now properly
report a 400 error instead of a 503.
* Fix object versioning with non-ASCII container names.
* Bulk delete with POST now works properly.
* Generic means for persisting system metadata
Swift now supports system-level metadata on accounts and
containers. System metadata provides a means to store internal
custom metadata with associated Swift resources in a safe and
secure fashion without actually having to plumb custom metadata
through the core swift servers. The new gatekeeper middleware
prevents this system metadata from leaking into the request or
being set by a client.
* catch_errors and gatekeeper middleware are now forced into the proxy
pipeline if not explicitly referenced.
* New container sync configuration option, separating the end user
from knowing the required end point and adding more secure
signed requests. See
http://swift.openstack.org/overview_container_sync.html for full
information.
* bulk middleware now can be configured to retry deleting containers.
* The default yield_frequency used to keep client connections alive
during slow bulk requests was reduced from 60 seconds to 10 seconds.
While this is a change to a default, it should not affect deployments
and there is no migration process needed.
* Swift processes will attempt to set RLIMIT_NPROC to 8192.
* Server processes will now exit with a non-zero error code on config
errors.
* Warn if read_affinity is configured but not enabled.
* Fix checkmount error parsing in swift-recon.
* Log at warn level when an object is quarantined.
* Fixed CVE-2014-0006 to avoid a potential timing attack with tempurl.
* Various other minor bug fixes and improvements.
swift (1.11.0)
* Added discoverable capabilities
A Swift proxy server now by default (although it can be turned off)
will respond to requests to /info. The response to these requests
include information about the cluster and can be used by clients to
determine which features are supported in the cluster.
* Object replication ssync (an rsync alternative)
A Swift storage node can now be configured to use Swift primitives
for replication transport instead of rsync. This is an experimental
feature that is not yet considered production ready.
* If a source times out on an object server read, try another one
of them with a modified range.
* The proxy now responds to many types of requests as soon as it
has a quorum. This can help speed up responses (without
changing the results), especially when one node is acting up.
There is a post_quorum_timeout config value that can tune how
long to wait for requests to finish after a quorum has been
established.
* Add accurate timestamps in proxy log lines for the start and
end of a request. These are added as new fields on the end of
the existing log lines, and therefore should not break
existing, well-behaved log processors.
* Add an "inline" query parameter to tempurl
By default, temporary URLs add a "Content-Disposition" header
that forces many clients to download the object. Now, temporary
URLs support an optional "inline" query parameter that will
force a "Content-Disposition: inline" header to be added to the
response, overriding the default.
* Use TCP_NODELAY for created sockets. This can dramatically
lower latency for small object workloads.
* DiskFile API, with reference implementation
The DiskFile abstraction for talking to data on disk has been
refactored to allow alternate implementations to be developed.
Included in the codebase is an in-memory reference
implementation. For full documentation, please see the developer
documentation. The DiskFile API is still a work in progress and
is not yet finalized.
* Removal of swift-bench
The included benchmarking tool swift-bench has been extracted
from the codebase and is now in its own repository at
https://github.com/openstack/swift-bench. New swift-bench
binaries and packages may be found on PyPI at
https://pypi.python.org/pypi/swift-bench
* Bulk delete now also supports the POST verb, in addition to DELETE
* Added functionality to the swift-ring-builder to support
limited recreation of ring builder files from the ring file itself.
* HEAD on account now returns 410 if account was deleted and
not yet reaped. The old behavior was to return a 404.
* Fixed a bug introduced since the 1.10.0 release that
prevented expired objects from being removed from the system.
This resulted in orphaned expired objects taking up space on
the system but inaccessible to the API. This regression and
fix are only important if you have deployed code since the
1.10.0 release. For a full discussion, including a script that
can be used to clean up orphaned objects, see
https://bugs.launchpad.net/swift/+bug/1257330
* Tie socket write buffer size to server chunk size parameter. This
pairs the underlying network buffer size with the size of data
that Swift attempts to read from the connection, thereby
improving efficiency and throughput on connections.
* Fix 500 from account-quota middleware. If a user had set
X-Account-Meta-Quota-Bytes to something non-integer prior to
the installation of the account-quota middleware, then the
quota check would choke on it. Now a non-integer value is
treated as "no quota".
* Quarantine objects with busted metadata. Before, if you
encountered an object with corrupt or missing xattrs, the
object server would return a 500 on GET, and wouldn't quarantine
anything. Now the object server returns a 404 for that GET and
the corrupted file is quarantined, thus giving replication a
chance to fix it.
* Fix quarantine and error counts in audit logs
* Report transaction ID in failure exception logs
* Make pbr a build-time only dependency
* Worked around a bug in eventlet 0.9.16 where the size of the
memcache connection pools would grow unbounded.
* Tempurl keys are now properly stored as utf8
* Fixed an issue where concurrent PUT requests to accounts or
containers may result in errors due to locked databases.
* Handle copy requests in account and container quota middleware
* Now ensure that a WWW-Authenticate header is on all 401 responses
* Various other bug fixes and improvements
swift (1.10.0, OpenStack Havana)
* Added support for pooling memcache connections
* Added support to replicating handoff partitions first in object
replication. Can also configure how many remote nodes a storage node
must talk to before removing a local handoff partition.
* Fixed bug where memcache entries would not expire
* Much faster calculation for choosing handoff nodes
* Added container listing ratelimiting
* Fixed issue where the proxy would continue to read from a storage
server even after a client had disconnected
* Added support for headers that are only visible to the owner of a Swift
account
* Fixed ranged GET with If-None-Match
* Fixed an issue where rings may not be balanced after initial creation
* Fixed internationalization support
* Return the correct etag for a static large object on the PUT response
* Allow users to extract archives to containers with ACLs set
* Fix support for range requests against static large objects
* Now logs x-copy-from header in a useful place
* Reverted back to old XML output of account and container listings to
ensure older clients do not break
* Account quotas now appropriately handle copy requests
* Fix issue with UTF-8 handling in versioned writes
* Various other bug fixes and improvements, including support for running
Swift under Pypy and continuing work to support storage policies
swift (1.9.1)
* Disallow PUT, POST, and DELETE requests from creating older tombstone
files, preventing the possibility of filling up the disk and removing
unnecessary container updates.
* Set default wsgi workers to cpu_count
Change the default value of wsgi workers from 1 to auto. The new
default value for workers in the proxy, container, account & object
wsgi servers will spawn as many workers per process as you have cpu
cores. This will not be ideal for some configurations, but it's much
more likely to produce a successful out of the box deployment.
* Added reveal_sensitive_prefix config setting to filter the auth token
logged by the proxy server.
* Ensure Keystone's reseller prefix ends with an underscore. Previously
this was a recommendation--now it is enforced.
* Added log_file_pattern config to swift-drive-audit for drive errors
* Add support for telling Swift to detect a content type on a request.
* Additional object stats are now logged in the object auditor
* Moved the DiskFile interface into its own module
* Ensure the SQLite cursors are closed when creating functions
* Better support for valid Accept headers
* In Keystone, don't allow users to delete their own account
* Return a UTC timezone designator in container listings
* Ensure that users can't remove their account quotas
* Allow floating point value for dispersion coverage
* Fix incorrect error page handling in staticweb
* Add utf-8 charset to multipart-manifest=get response.
* Allow dispersion tools to use keystone server with insecure certificate
* Ensure that files are always closed in tests
* Use OpenStack's "Hacking" guidelines for code formatting
* Various other minor bug fixes and improvements
swift (1.9.0)
* Global clusters support
The "region" concept introduced in Swift 1.8.0 has been augmented with
support for using a separate replication network and configuring read
and write affinity. These features combine to offer support for a single
Swift cluster spanning wide geographic area.
* Disk performance
The object server now can be configured to use threadpools to increase
performance and smooth out latency throughout the system. Also, many
disk operations were reordered to increase reliability and improve
performance.
* Added config file conf.d support
Allow Swift daemons and servers to optionally accept a directory as the
configuration parameter. This allows different parts of the config file
to be managed separately, eg each middleware could use a separate file
for its particular config settings.
* Allow two TempURL keys per account
By adding a second key, a user can safely rotate keys and prevent URLs
already in use from becoming invalid. TempURL middlware has also been
updated to allow a configuable set of allowed methods and to prevent a
bugrelated to content-disposition names.
* Added crossdomain.xml middleware. See
http://docs.openstack.org/developer/swift/crossdomain.html for details
* Added rsync bandwidth limit setting for object replicator
* Transaction ID updated to include the time and an optional suffix
* Added x-remove-versions-location header to disable versioned writes
* Improvements to support for Keystone ACLs
* Added parallelism to object expirer daemon
* Added support for ring hash prefix in addition to the existing suffix
* Allow all headers requested for CORS
* Stop getting useless bytes on manifest Range requests