OpenStack Swift Grizzly Release
OpenStack Grizzly was released today. As Swift’s Project Technical Lead, the most fun part of my job is to put together the release notes at the end of the OpenStack release cycle. Seeing what the community has come together to build, the new use cases that are enabled, and the improvements in existing features is tremendously exciting. I’m honored to be a part of it. I’d like to share with you a few of the key features that have been added to Swift over the last six months.
During the OpenStack Grizzly release cycle, Swift has released version 1.7.5, 1.7.6, and 1.8.0. The full notes for these releases is available in Swift’s changelog.
As always, deployers can upgrade to the latest version of Swift with no downtime on their existing clusters.
Key New Features
Global clusters building blocks
Allow the rings to have an adjustable replica count: Deployers can now adjust the replica count on existing clusters
Allow rings to have different replica counts: Deployers can choose different replica counts for account, container, and object rings
Added support for a region tier above zones: Deployers can group zones into regions.
Added timing-based sorting of object servers on read requests: This allows the fastest responding server to serve the most requests instead of a random choice of the replicas. This can be especially useful when a replicas are in different regions separated by a WAN.
Added support for large objects with static manifests: Static large object manifests allow Swift users to specifically designate the individual segments which will make up a large object. Full docs are on the OpenStack site.
Added support for CORS requests: CORS allows web application developers to get around same-origin restrictions in web browsers. With this feature, web developers can use a Swift cluster directly instead of needing to proxy content through a separate server.
Bulk requests: Users can now ask a Swift cluster to upload or delete many objects with just one request.
Added support for auto-extracting archive uploads: A client can upload an archive file (ie a .tar file) and the contents will be stored individually in the cluster
Added support for bulk deletes: A client can delete many objects with one delete request
Added user-managed container quotas
Added support for account-level quotas (managed by an auth reseller)
I’m excited about what’s been added to Swift and the growing community that has contributed to its development. I hope to see you all in Portland ten days from now at the OpenStack summit.