diff options
author | John Dickinson <me@not.mn> | 2018-01-16 14:51:29 -0800 |
---|---|---|
committer | John Dickinson <me@not.mn> | 2018-02-02 12:09:20 -0800 |
commit | f4cfe81e593b52e11e67916073a050cd2dde2e00 (patch) | |
tree | 0d0c92538e4553c03ad69e27b0170f9c8575c0a0 | |
parent | c97459b54aa150fbd7aa590b42a5bada3a5a5198 (diff) | |
download | swift-f4cfe81e593b52e11e67916073a050cd2dde2e00.tar.gz |
authors/changelog updates for 2.17.0 release
Change-Id: I577d169022916676a20a9ac24c7cc7b63ae46778
-rw-r--r-- | .mailmap | 3 | ||||
-rw-r--r-- | AUTHORS | 12 | ||||
-rw-r--r-- | CHANGELOG | 102 | ||||
-rw-r--r-- | releasenotes/notes/2_17_0_release-bd35f18c41c5ef18.yaml | 119 |
4 files changed, 234 insertions, 2 deletions
@@ -95,7 +95,8 @@ Mehdi Abaakouk <sileht@redhat.com> <mehdi.abaakouk@enovance.com> Richard Hawkins <richard.hawkins@rackspace.com> <hurricanerix@gmail.com> Ondrej Novy <ondrej.novy@firma.seznam.cz> Ondrej Novy <ondrej.novy@firma.seznam.cz> <novy@ondrej.org> -Peter Lisak <peter.lisak@firma.seznam.cz> +Peter Lisák <peter.lisak@gmail.com> <peter.lisak@firma.seznam.cz> +Peter Lisák <peter.lisak@gmail.com> Peter Lisák <peter.lisak@firma.seznam.cz> Ke Liang <ke.liang@easystack.cn> Daisuke Morita <morita.daisuke@ntti3.com> <morita.daisuke@lab.ntt.co.jp> Andreas Jaeger <aj@suse.de> <aj@suse.com> @@ -82,7 +82,9 @@ ChangBo Guo(gcb) (eric.guo@easystack.cn) Chaozhe Chen (chaozhe.chen@easystack.cn) Charles Hsu (charles0126@gmail.com) chenaidong1 (chen.aidong@zte.com.cn) +cheng (li.chenga@h3c.com) Cheng Li (shcli@cn.ibm.com) +chengebj5238 (chengebj@inspur.com) Chmouel Boudjnah (chmouel@enovance.com) Chris Wedgwood (cw@f00f.org) Christian Berendt (berendt@b1-systems.de) @@ -155,6 +157,7 @@ Fujita Tomonori (fujita.tomonori@lab.ntt.co.jp) Félix Cantournet (felix.cantournet@cloudwatt.com) Gage Hugo (gh159m@att.com) Ganesh Maharaj Mahalingam (ganesh.mahalingam@intel.com) +gaofei (gao.fei@inspur.com) Gaurav B. Gangalwar (gaurav@gluster.com) gecong1973 (ge.cong@zte.com.cn) gengchc2 (geng.changcai2@zte.com.cn) @@ -164,6 +167,7 @@ Gonéri Le Bouder (goneri.lebouder@enovance.com) Graham Hayes (graham.hayes@hpe.com) Gregory Haynes (greg@greghaynes.net) Guang Yee (guang.yee@hpe.com) +guotao (guotao.bj@inspur.com) Gábor Antal (antal@inf.u-szeged.hu) Ha Van Tu (tuhv@vn.fujitsu.com) Hamdi Roumani (roumani@ca.ibm.com) @@ -199,6 +203,7 @@ Jing Liuqing (jing.liuqing@99cloud.net) Joanna H. Huang (joanna.huitzu.huang@gmail.com) Joe Arnold (joe@swiftstack.com) Joe Gordon (jogo@cloudscaling.com) +Joel Wright (joel.wright@sohonet.com) John Leach (john@johnleach.co.uk) Jola Mirecka (jola.mirecka@hp.com) Jon Snitow (otherjon@swiftstack.com) @@ -292,7 +297,7 @@ Pavel Kvasnička (pavel.kvasnicka@firma.seznam.cz) Pawel Palucki (pawel.palucki@gmail.com) Pearl Yajing Tan (pearl.y.tan@seagate.com) Pete Zaitcev (zaitcev@kotori.zaitcev.us) -Peter Lisak (peter.lisak@firma.seznam.cz) +Peter Lisák (peter.lisak@gmail.com) Peter Portante (peter.portante@redhat.com) Petr Kovar (pkovar@redhat.com) Pradeep Kumar Singh (pradeep.singh@nectechnologies.in) @@ -306,6 +311,8 @@ Ray Chen (oldsharp@163.com) Rebecca Finn (rebeccax.finn@intel.com) Ricardo Ferreira (ricardo.sff@gmail.com) Richard Hawkins (richard.hawkins@rackspace.com) +Robert Francis (robefran@ca.ibm.com) +Robin Naundorf (r.naundorf@fh-muenster.de) Romain Le Disez (romain.ledisez@ovh.net) Russ Nelson (russ@crynwr.com) Russell Bryant (rbryant@redhat.com) @@ -361,8 +368,10 @@ Viktor Varga (vvarga@inf.u-szeged.hu) Vincent Untz (vuntz@suse.com) Vladimir Vechkanov (vvechkanov@mirantis.com) Vu Cong Tuan (tuanvc@vn.fujitsu.com) +vxlinux (yan.wei7@zte.com.cn) wanghongtaozz (wanghongtaozz@inspur.com) Wu Wenxiang (wu.wenxiang@99cloud.net) +xhancar (pavel.hancar@gmail.com) XieYingYun (smokony@sina.com) Yaguang Wang (yaguang.wang@intel.com) Yatin Kumbhare (yatinkumbhare@gmail.com) @@ -378,6 +387,7 @@ Zack M. Davis (zdavis@swiftstack.com) Zap Chang (zapchang@gmail.com) Zhang Guoqing (zhang.guoqing@99cloud.net) Zhang Jinnan (ben.os@99cloud.net) +zhang.lei (zhang.lei@99cloud.net) zhangdebo1987 (zhangdebo@inspur.com) zhangyanxian (zhangyanxianmail@163.com) Zhao Lei (zhaolei@cn.fujitsu.com) @@ -1,3 +1,105 @@ +swift (2.17.0) + + * Added symlink objects support. + + Symlink objects reference one other object. They are created by + creating an empty object with an X-Symlink-Target header. The value of + the header is of the format <container>/<object>, and the target does + not need to exist at the time of symlink creation. Cross-account + symlinks can be created by including the + X-Symlink-Target-Account header. + + GET and HEAD requests to a symlink will operate on the + referenced object and require appropriate permission in the + target container. DELETE and PUT requests will operate on the + symlink object itself. POST requests are not forwarded to the + referenced object. POST requests sent to a symlink will result + in a 307 Temporary Redirect response. + + * Added support for inline data segments in SLO manifests. + + Upgrade impact: during a rolling upgrade, an updated proxy server + may write a manifest that an out-of-date proxy server will not be + able to read. This will resolve itself once the upgrade completes + on all nodes. + + * The tempurl digest algorithm is now configurable, and Swift added + support for both SHA-256 and SHA-512. Supported tempurl digests + are exposed to clients in `/info`. Additionally, tempurl signatures + can now be base64 encoded. + + * Object expiry improvements + + - Disallow X-Delete-At header values equal to the X-Timestamp header. + + - X-Delete-At computation now uses X-Timestamp instead of + system time. This prevents clock skew causing inconsistent + expiry data. + + - Deleting an expiring object will now cause less work in the system. + The number of async pending files written has been reduced for all + objects and greatly reduced for erasure-coded objects. This + dramatically reduces the burden on container servers. + + - Stopped logging tracebacks when receiving an unexpected response. + + - Allow the expirer to gracefully move past updating stale work items. + + * When the object auditor examines an object, it will now add any + missing metadata checksums. + + * `swift-ring-builder` improvements + + - Save the ring when dispersion improves, even if balance + doesn't improve. + + - Improved the granularity of the ring dispersion metric so that + small improvements after a rebalance can show changes in the + dispersion number. Dispersion in existing and new rings can be + recalculated using the new '--recalculate' option to + `swift-ring-builder`. + + - Display more info on empty rings. + + * Fixed rare socket leak on range requests to erasure-coded objects. + + * The number of container updates on object PUTs (ie to update listings) + has been recomputed to be far more efficient while maintaining + durability guarantees. Specifically, object PUTs to erasure-coded + policies will now normally result in far fewer container updates. + + * Moved Zuul v3 tox jobs into the Swift code repo. + + * Changed where liberasurecode-devel for CentOS 7 is referenced and + installed as a dependency. + + * Added container/object listing with prefix to InternalClient. + + * Added '--swift-versions' to `swift-recon` CLI to compare installed + versions in the cluster. + + * Stop logging tracebacks in the `object-replicator` when it runs + out of handoff locations. + + * Send ETag header in 206 Partial Content responses to SLO reads. + + * Now `swift-recon-cron` works with conf.d configs. + + * Improved `object-updater` stats logging. It now tells you all of + its stats (successes, failures, quarantines due to bad pickles, + unlinks, and errors), and it tells you incremental progress every + five minutes. The logging at the end of a pass remains and has + been expanded to also include all stats. + + * If a proxy server is configured to autocreate accounts and the + account create fails, it will now return a server error (500) + instead of Not Found (404). + + * Fractional replicas are no longer allowed for erasure code policies. + + * Various other minor bug fixes and improvements. + + swift (2.16.0) * Add checksum to object extended attributes. diff --git a/releasenotes/notes/2_17_0_release-bd35f18c41c5ef18.yaml b/releasenotes/notes/2_17_0_release-bd35f18c41c5ef18.yaml new file mode 100644 index 000000000..cdb9ff04c --- /dev/null +++ b/releasenotes/notes/2_17_0_release-bd35f18c41c5ef18.yaml @@ -0,0 +1,119 @@ +--- +features: + - | + Added symlink objects support. + + Symlink objects reference one other object. They are created by + creating an empty object with an X-Symlink-Target header. The value of + the header is of the format <container>/<object>, and the target does + not need to exist at the time of symlink creation. Cross-account + symlinks can be created by including the + X-Symlink-Target-Account header. + + GET and HEAD requests to a symlink will operate on the + referenced object and require appropriate permission in the + target container. DELETE and PUT requests will operate on the + symlink object itself. POST requests are not forwarded to the + referenced object. POST requests sent to a symlink will result + in a 307 Temporary Redirect response. + + - | + Added support for inline data segments in SLO manifests. + + Upgrade impact -- during a rolling upgrade, an updated proxy server + may write a manifest that an out-of-date proxy server will not be + able to read. This will resolve itself once the upgrade completes + on all nodes. + + - | + The tempurl digest algorithm is now configurable, and Swift added + support for both SHA-256 and SHA-512. Supported tempurl digests + are exposed to clients in ``/info``. Additionally, tempurl signatures + can now be base64 encoded. + + - | + Object expiry improvements + + - Disallow X-Delete-At header values equal to the X-Timestamp header. + + - X-Delete-At computation now uses X-Timestamp instead of + system time. This prevents clock skew causing inconsistent + expiry data. + + - Deleting an expiring object will now cause less work in the system. + The number of async pending files written has been reduced for all + objects and greatly reduced for erasure-coded objects. This + dramatically reduces the burden on container servers. + + - Stopped logging tracebacks when receiving an unexpected response. + + - Allow the expirer to gracefully move past updating stale work items. + + - | + When the object auditor examines an object, it will now add any + missing metadata checksums. + + - | + ``swift-ring-builder`` improvements + + - Save the ring when dispersion improves, even if balance + doesn't improve. + + - Improved the granularity of the ring dispersion metric so that + small improvements after a rebalance can show changes in the + dispersion number. Dispersion in existing and new rings can be + recalculated using the new ``--recalculate`` option to + ``swift-ring-builder``. + + - Display more info on empty rings. + + - | + Fixed rare socket leak on range requests to erasure-coded objects. + + - | + The number of container updates on object PUTs (ie to update listings) + has been recomputed to be far more efficient while maintaining + durability guarantees. Specifically, object PUTs to erasure-coded + policies will now normally result in far fewer container updates. + + - | + Moved Zuul v3 tox jobs into the Swift code repo. + + - | + Changed where liberasurecode-devel for CentOS 7 is referenced and + installed as a dependency. + + - | + Added container/object listing with prefix to InternalClient. + + - | + Added ``--swift-versions`` to ``swift-recon`` CLI to compare installed + versions in the cluster. + + - | + Stop logging tracebacks in the ``object-replicator`` when it runs + out of handoff locations. + + - | + Send ETag header in 206 Partial Content responses to SLO reads. + + - | + Now ``swift-recon-cron`` works with conf.d configs. + + - | + Improved ``object-updater`` stats logging. It now tells you all of + its stats (successes, failures, quarantines due to bad pickles, + unlinks, and errors), and it tells you incremental progress every + five minutes. The logging at the end of a pass remains and has + been expanded to also include all stats. + + - | + If a proxy server is configured to autocreate accounts and the + account create fails, it will now return a server error (500) + instead of Not Found (404). + + - | + Fractional replicas are no longer allowed for erasure code policies. + + - | + Various other minor bug fixes and improvements. |