SwiftStack Controller Release Notes Archive

2.37.0 (Dec 29, 2014)

Features:

Bug Fixes:

  • Fixed a package dependency which could prevent Gateway install on CentOS/RHEL 6.6.
  • Fixed a rare edge case where a change in replication network IP or port could fail to get applied.
  • Fixed an LDAP problem which could cause proxies to slow down or hang.

2.36.0.1 (Dec 19, 2014)

Features:

  • Node disable includes table for its devices current used storage and rings assignment for additional context to go with the warning that disabling a node will immediately remove it from the Swift cluster.
  • Graphical interface for configuring and manually running controller backups.

Bug Fixes:

  • A down Gateway no longer prevents a config push to its Cluster. Also, a config push to a Cluster no longer pushes configs to Gateways. To push a new configuration for a Gateway, you must do so from the Gateway deploy page or the SwiftStack controller API.
  • Improved robustness of node agent code when a bad disk causes I/O operations to hang forever.
  • The new python-pbr package in Ubuntu 14.04 LTS (Trusty) conflicts with the SwiftStack package ss-python-pbr. This release includes a new Swift packaging which resolves this conflict.

Known Issues:

  • Users of the LDAP-based Authentication for SwiftStackAuth middleware will need to push a config to each Cluster after 2.36.0 is deployed.

2.35.0.1 (Dec 11, 2014)

Bug Fixes:

  • Improved the X-Object-Manifest header used by the Gateway for large (segmented) files.
  • Fixed race condition where an uploaded file could get lost after a Gateway restart when the Gateway was under heavy load.
  • Fixed issue where devices removed from all rings no longer appeared in the rings at all, preventing data from getting migrated off of them.

Known Issues:

  • Truncating a large (segmented) file with the Gateway can leave segments in Swift. A future release will correctly reap the extraneous segments as well as audit and correct any existing extraneous segments.
  • If you create a cluster in which the amount of storage is severely imbalanced between availability zones, you can get more replicas of data residing in one of the availability zones than is desirable from an availability perspective. A future release will give visibility into this condition if it exists.

2.35.0 (Dec 4, 2014)

Features:

  • V2 Authentication responses from SwiftStack Auth include default "region" values, enabling V2 Auth in certain third-party tools such as Cyberduck.
  • Client compatibility improved when terminating SSL on Swift nodes.
  • Greater flexibility for configuring LDAP/AD authentication for Swift, especially when authenticating against multiple servers.
  • An alert will now appear for any Swift nodes that are disabled due to outdated configuration.

Bug Fixes:

  • Firewall rules for non-default OpenVPN subnets are now installed correctly on fresh controllers.
  • Multiple bug fixes improving stability for Gateways running on Trusty.
  • Multiple bug fixes involving Multipath devices in Swift nodes.

Known Issues:

  • Updating the OpenVPN subnet on an existing controller is known to require manual editing of ssnoded.conf.

2.34.0.1 (Nov 12, 2014)

Bug Fixes:

  • Gateway filesystem deadlock detection now uses a more accurate mechanism than /sys/fs/fuse/connections/.

2.34.0 (Nov 12, 2014)

Bug Fixes:

  • Gateway filesystem deadlock detection no longer dependent on any filesystem components.
  • Resolved issue when configuring a cluster after deleting the user that created it.
  • Fixed bug for standby controllers periodically updating cluster stats/metrics.

2.33.0 (Oct 30, 2014)

Features:

  • Added integrity checks during install process.
  • Improved system-time checks in ssdiag.
  • Improved Gateway performance for directories with many files.
  • Added ability for administrators to download controller reports for later upload to swiftstack.com

Bug Fixes:

  • Improved Gateway monitoring and stability.
  • Addressed an issue with gradual capacity adjustments.
  • Improved authentication middleware conflict detection.
  • Addressed an issue with package status detection.
  • Improved handling of nodes that fail to ingest properly.
  • Addressed an issue when sending some ring-builder backups to Swift.
  • Improved experience for controller users with read-only access.
  • Various UI fixes.
  • Various documentation corrections.

Known Issues:

  • Recent OS updates may cause instability on SwiftStack Gateways. This is known to affect CentOS 6.6 and Ubuntu 14.04 LTS (Trusty); neither is supported at this time. This will be fixed in a future release.

2.32.0.3 (Oct 22, 2014)

Bug Fixes:

  • Fixed an issue where the Gateway health check could erroneously consider the Gateway unresponsive when under load.

2.32.0.2 (Oct 21, 2014)

Bug Fixes:

  • Updated post transaction directive for ss-collectd rpm to ensure that collectd is always started after upgrade from conflicting system package.

2.32.0.1 (Oct 21, 2014)

Bug Fixes:

  • Renamed Ubuntu collectd package to avoid name conflict with system package, thereby resolving installation issues on Ubuntu 14.04 LTS (Trusty).
  • Fixed Gateway UI for custom outward facing network interface settings.

2.32.0 (Oct 16, 2014)

Features:

  • Swift upgrade (2.2.0.1) includes Storage Policies.
  • Added support for Swift's Storage Policies (See: SwiftStack Storage Policies).
  • New Drive Management interface.
  • Gateway version (0.0.110) robustness checks and service restarts for filesystem.
  • Support new Swift object auditor configuration for disk_chunk_size and apply improved performance tuning.
  • New configuration options for Swift's TempURL middleware (See: TempURL).
  • LDAP controller authentication configuration management has been improved for robustness and will be configurable at runtime in a future release.

Bug Fixes:

  • Swift pipeline ordering for Large Objects better supports expired tokens for all auth middlewares.
  • Fixed issue where Gradual capacity adjustment could get stuck.
  • Fixed issue where some swift deamons could fail to stop and cause a Rolling Swift Upgrade to fail.
  • Fixed issue where parallel drive formating could fail.
  • Better support for nodes with a restrictive default umask.
  • Better support for controllers with a restrictive default umask.

2.31.0.3 (Oct 15, 2014)

Bug Fixes:

  • Disabled SSLv3 for SwiftStack controller and SSL termination on nodes to defend against CVE-2014-3566 (the "POODLE" vulnerability).
  • Improved Swift package installation robustness during Swift node claiming.
  • Fixes for SwiftStack Controller On-Premises controllers and nodes running Ubuntu 14.04 LTS (Trusty).

Known Issues:

  • Upgrading an existing Ubuntu 12.04 LTS (Precise) SwiftStack Controller On-Premises or node to Ubuntu 14.04 LTS (Trusty) may not work correctly. This will be fixed in a future release.
  • For Ubuntu 14.04 LTS (Trusty) SwiftStack Controller On-Premises controllers or nodes, after installation, you must run this command with superuser privileges: apt-get install collectd-core=5.2.1-10~trusty

2.31.0.2 (Oct 1, 2014)

Bug Fix:

  • Fixed an issue with mounting node drives in parallel.

2.31.0 (Sep 18, 2014)

Features:

  • Added support for Ubuntu 14.04 LTS.
  • Added the ability to configure Swift constraints. Among other things, this allows Keystone catalogs with more than 12 endpoints per region.
  • Node drives now format in parallel.
  • Added support for sending SNMP traps for Events. See details at Sending Events Via SNMP.
  • Added system alerts for situations like the controller running low on disk space.

Bug Fixes:

  • Rolling Swift Upgrades are no longer affected by inaccessible gateways.
  • Fixed issue where graphs could retrieve less data than they should.

2.30.0.2 (Sep 10, 2014)

Bug Fixes:

  • Fixed one more issue which could prevent controller fresh installs on CentOS/RHEL.

2.30.0.1 (Sep 4, 2014)

Bug Fixes:

  • Fixed issue which could prevent controller fresh installs on CentOS/RHEL.
  • Fixed issue sending emails with non-ASCII characters in the To or From address.

2.30.0 (Sep 4, 2014)

Features:

  • Added documentation for Gateway and metrics-related API endpoints.
  • Node drives now mount in parallel.

Bug Fixes:

  • Gateway setting for LDAP group look-ups for users who belong in many groups now works.
  • Fixed issue where an existing installed libxml2 RPM could prevent controller installation on CentOS/RHEL.

2.29.0 (Aug 25, 2014)

Features:

  • SwiftStack Gateway is now available! This is a filesystem gateway for accessing your Swift cluster. See details at SwiftStack Gateway Guide
  • In order to ingest a Gateway, a license is required. Please contact sales@swiftstack.com for more information.

Bug Fixes:

  • Fixed a bug that could cause the Cluster Node CPU Utilization graph to not display
  • Rolling Swift Upgrades no longer fail on nodes with restricted services.

2.28.0.2 (Aug 14, 2014)

Bug Fixes:

  • Fixed bug in config-push status when controller hostname contains digits.

2.28.0.1 (Aug 11, 2014)

Bug Fixes:

  • Fixed bug in controller backup script.

2.28.0 (Aug 7, 2014)

Features:

  • Added ability to restrict which services run on each node in a cluster; requires that nodes run Swift 1.9.2.1 or later.
  • Added load average to node CPU utilization graphs.

Bug Fixes:

  • Fixed race condition between node cluster version listeners and config pushes.
  • Disabled nodes no longer count against utilization reporting-complete percentage.
  • Fixed directory permissions for Keystone Auth Token middleware.
  • Fixed issue with per-node Proxy Throughput graphs.

Known Issues:

  • Rolling Swift Upgrades may fail on nodes with restricted services.
  • Unicode remains unsupported for account invitation emails.

2.27.0.2 (Aug 4, 2014)

Bug Fixes:

  • Fixed issue introduced in 2.27.0 where Swift proxy transfer utilization data could get accounted to the prior 30-minute interval. A config push to each cluster is necessary to activate the fix.

2.27.0.1 (Jul 29, 2014)

Bug Fixes:

  • Additional fix for SwiftStack Controller On-Premises CentOS 6.5 platforms with the latest updates version of libxml2 installed.

2.27.0 (Jul 24, 2014)

Bug Fixes:

  • Fixed issue affecting SwiftStack Controller On-Premises CentOS 6.5 platforms with the latest updates version of libxml2 installed.
  • Fixed race condition in proxy access log parsing when old log lines still appear in the file after log rotation.

2.26.0.4 (Jul 17, 2014)

Back end improvements in preparation for upcoming feature release.

2.26.0.3 (Jul 14, 2014)

Bug Fixes:

  • Fixed an issue which could have affected SwiftStack Controller On-Premises upgrades.

2.26.0.1 (Jul 10, 2014)

Features:

  • Utilization metrics now exportable as CSV

Bug Fixes:

  • Brought security model of API in line with the GUI, by mapping actions to specific Security Roles appropriately
  • Fixed Perl package dependency errors which caused issues with installations on Red Hat 6.4

2.25.0 (Jun 27, 2014)

Features:

  • New version of Swift (1.13.1.3) properly quotes www-authenticate header (CVE-2014-3497)

2.24.0.2 (Jun 16, 2014)

Bug Fixes:

  • SwiftStack Controller On-Premises: fixed a bug that could cause installation or upgrade process to fail on some Red Hat or CentOS controllers.
  • Fixed a bug that could cause ingesting a new node into a cluster running Swift 1.11.0.1 or earlier to fail once and then fail to send transfer utilization data thereafter.

2.24.0 (Jun 5, 2014)

Features:

  • SwiftStack Controller On-Premises: installations of both controllers and Nodes no longer require HTTP/S connectivity.

Bug Fixes:

  • Fixed a bug that would cause Swift Web Console not to display all containers in an account in some circumstances.
  • Fixed a bug in LDAP Swift integration that could cause queries to time out

2.23.0.1 (May 22, 2014)

Bug Fixes:

  • Fixed edge-case processing node device data.

2.23.0 (May 22, 2014)

Features:

  • Added support for the list-endpoints Swift middleware. NOTE: this middleware has security implications and should only be enabled in certain specific deployment scenarios and use-cases.
  • Added support for the CNAME lookup Swift middleware.

Bug Fixes:

  • Fixed issues with commands timing out for storage nodes with large numbers of drives.

2.22.0.1 (May 13, 2014)

Bug Fixes:

  • Fixed node health checks for clusters which have not recently had a config pushed.

2.22.0 (May 8, 2014)

Features:

  • Swift upgrade to the Icehouse (1.13.1.1) release
  • Overhaul of controller user interface: new look, but functionality and workflows remain the same
  • Swift Usage tab displays total cluster usage in addition to top accounts
  • Static Large Object middleware enabled by default in new clusters
  • Enabled middleware listed before disabled middleware

Bug Fixes:

  • SwiftStack Controller On-Premises: when authenticating to the controller with LDAP, receiving an LDAP "Server Down" exception no longer causes a 500.

2.21.0 (Apr 24, 2014)

Features:

  • Initial integration of utilization information into controller GUI. Displays the top n Swift accounts by usage over a time period t, where both n and t are specified by the user in a form.
  • Added username into Edit User page
  • Centrify packaging removed from the SwiftStack codebase. Those interested in authing against their AD infrastructure are encouraged to consider using LDAP to do so (possible with versions of the controller 2.20.0 and after); if that is deemed insufficient, please open a support ticket to discuss further.
  • Some work has been done to explore v2 Auth protocol support in SwiftStack Auth (and its associated LDAP implementation). This work is incomplete and unsupported at this time, but if this functionality is something that you would use, please contact support and let us know about your use-case, and we'd be happy to investigate what level of increased support might be necessary and when that might be delivered.

Bug Fixes:

  • Swift LDAP Auth now works when the DN contains a comma or other escaped characters
  • Swift LDAP Auth now properly returns a 503 when it cannot reach the LDAP servers

Notes:

  • If you have used Centrify AD and have run adjoin on any of your nodes domain (this is a very small percentage of our customers), you must (as root) run adleave --force on those nodes, followed by apt-get -f -y install before those nodes can upgrade to the new SwiftStack version. Please contact us for further details.

2.20.0.1 (Apr 7, 2014)

Bug Fixes:

  • Fixed issue where certain input could stall utilization processing.

2.20.0 (Apr 3, 2014)

Features:

  • SwiftStack Auth using LDAP now supports more flexibility around combinations of search and group membership. Active Directory interoperation also improved.
  • SwiftStack Auth now supports account ACLs. Account ACLs use the "V2" ACL syntax; more information is available in the Swift documentation.
  • New Swift3 Keystone Integration middleware supported, allowing the use of Keystone authentication alongside the emulation layer for S3.

Bug Fixes:

  • A new version of Swift3 was packaged with several improvements, including support for HEAD requests on buckets.
  • SwiftStack Auth is more robust in the face of temporary LDAP errors.

2.19.0.2 (Mar 20, 2014)

Bug Fixes:

  • Worked around an edge case where some Swift builder files would trigger an exception while rebalancing.

2.19.0 (Mar 20, 2014)

Features:

  • Included SwiftStack Swift packaging version 1.13.0.1. See the Swift 1.12.0 and 1.13.0 Release Notes for more details. Some highlights:
    • Account-level ACLs and new v2 ACL format.
    • Fixed an issue where overwriting segments in a dynamic manifest could cause issues on pipelined requests.
    • More information was added to the /info endpoint.
  • LDAP controller auth supports Active Directory style user DNs.
  • The required middleware SwiftStack Auth may now be configured. The authentication token lifetime setting is now configured there instead of the Tune Cluster tab.
  • Added Keystone integration guide (See: Keystone Integration) and Keystone middleware configuration guides (See: Keystone Auth and Keystone Auth Token).

Bug Fixes:

  • Fixed a bug which could prevent data collection for the Cluster Proxy Throughput graph.

2.18.0 (Mar 4, 2014)

Features:

  • Utilization processing times substantially improved for large clusters.
  • Some clusters enabled to transmit some information to SwiftStack to enable better customer support.
  • Users can configure bind port for the proxy server (useful in some configurations.)
  • Users can now select the replica count for the cluster until the cluster is active.

Bug Fixes:

  • Addressed some issues with SwiftStackAuth and older versions (1.7.x) of Swift.
  • Fixed an issue which prevented log events from being generated for remounted devices in some circumstances.

2.17.0 (Feb 13, 2014)

Features:

  • Controller browser sessions expire after a configurable interval (default 1 day). Sessions may also be configured to expire when the browser is closed.
  • Operators are prominently warned about old versions of Swift and strongly urged to upgrade.
  • Swift cluster authentication now supports expiring a user's existing storage token. See Invalidate Existing Authentication Tokens for documentation.
  • SwiftStack Controller On-Premises: added sscontrol command-line administration script. (See SwiftStack Controller Troubleshooting Commands for more information.)
  • Added per-HTTP-verb proxy-server request timing graphs.

Bug Fixes:

  • Updated Nagios integration scripts' log parsing to work with new log style.
  • Fixed transfer utilization collection to work with new log style.
  • Fixed a regression in the format of date strings returned by the Utilization API.

2.16.0 (skipped)

  • This release number was skipped for internal bookkeeping reasons.

2.15.0.7 (Jan 29, 2014)

Bug Fixes:

  • Fixed an issue preventing rollup of utilization data. Rollups currently absent will be retroactively performed.

2.15.0.6 (Jan 23, 2014)

Features:

  • Improved visibility of working progress during Swift upgrades.

Bug Fixes:

  • Fixed issue that prevented some clusters from viewing data via the Utilization API.
  • Fixed error with controller password reset page.
  • Fixed issue that prevented some AES-NI enabled proxy nodes from using hardware acceleration for SSL termination.
  • Fixed issue which prevented upgrades of Swift 1.7.6.2 to 1.11.0.1 from succeeding without manual intervention.
  • SwiftStack Controller On-Premises: Fixed potential PostgreSQL deadlock during controller upgrade.

2.15.0 (Jan 14, 2014)

Features:

  • Included SwiftStack Swift packaging version 1.11.0.1. See the Swift 1.11.0 Release Notes for more details. All customers are strongly advised to upgrade to Swift 1.11.0.1 as soon as possible to take advantage of new features and bugfixes. Some highlights:
    • Several important security updates for Swift, including CVE-2014-0006.
    • Fixed an issue where concurrent PUT requests to accounts or containers may result in errors due to locked databases.
    • Early quorum performance optimization
    • Improvements to request latency for small-object workloads (TCP_NODELAY added to more sockets) and other socket-level optimizations.
    • Note that the SwiftStack release of 1.10.0.1 does not suffer from the object-expiry bug referenced in the Swift 1.11.0 release notes. However, all customers are still advised to upgrade to 1.11.0.1.
  • Added new configuration tunables for Swift 1.11.0+:
    • Proxy server post quorum timeout
    • Proxy server memcached max connections
    • Proxy server info admin key
  • Added a new "Deployment Status" field to the Configure Cluster page. Please use this field to mark your clusters as either "Testing" or "Production." This field is currently documentary at present, but will be used in the future to affect behavior in the SwiftStack controller.
  • Upgraded controller to Django 1.5.x, including security updates.
  • SwiftStack nodes terminating SSL now use the same version of Pound regardless of Operating System and now scale better; also AES-NI hardware acceleration will be used if available.
  • New documentation on the security features of SwiftStack is now available at SwiftStack Security Overview.

Bug Fixes:

  • Fixed issue that prevented removing unmounted/missing devices from rings.

2.14.0.2 (Jan 6, 2014)

Bug Fixes:

  • Fixed SwiftStack Controller On-Premises installs to work with newer upstream Pip.

2.14.0.1 (Dec 14, 2013)

Bug Fixes:

  • Fixed issue where some events were not getting drained from the queue

2.14.0 (Dec 14, 2013)

Features:

  • Adjusted default node configuration settings for swappiness and vfs_cache_pressure.
  • Streamline of SwiftStack node installation script.
  • Remounting of drives after boot made more robust.
  • SwiftStack Controller On-Premises operators can now have controller events sent to a syslog server.
  • Added alerting 'event catalog' to documentation.

Bug Fixes:

  • Ssdiag now catches exception thrown during server check
  • Fixes for CentOS 6.5 / selinux
  • Fixed issue where utilization aggregation would occasionally interfere with config pushes.
  • Fixed issue where drives were sometimes not getting removed from rings when requested.

2.13.0 (Dec 3, 2013)

Features:

  • Added support for CentOS 6.5 and RHEL 6.5.
  • Swift Web Console supports "bookmarks" for multiple accounts, if the user has access to multiple accounts.
  • New initial setup process via tempurl to setup-swiftstack.sh script.
  • Minor UI improvements.

Bug Fixes:

  • Unicode usernames and account names now supported.
  • Storage URL reported for LDAP Auth now respects cluster's http/https setting.

2.12.0.1 (Nov 19, 2013)

Bug Fixes:

  • Fixed unhandled exception in Swift heath checker when proxy-server PID file exists but the server is not actually running.
  • Several bug fixes in Swift Web Console:
    • Users can now upload files to any container instead of only the first.
    • Unicode usernames are now supported.
    • The move, delete, and copy buttons no longer appear for accounts to which the user does not have write access.

Known Issues:

  • Users with unicode characters in their names will not work with "non-user Swift accounts".
  • The LDAP authentication middleware for SwiftStack Auth returns incorrect storage URLs if your cluster is running SSL. This breaks Swift Web Console.
  • Under some circumstances, users with Read/Write access to a Non-User Account will be able to create containers but will not see the appropriate button on the Swift Web Console.

2.12.0 (Nov 14, 2013)

Features:

  • Added two new Utilization API endpoints which aggregate data for an entire cluster; see Per-Cluster Total Storage Utilization and Per-Cluster Total Transfer Utilization.
  • For increased security, the controller user profile edit page now requires the user's current password to be entered in order to make changes.
  • Added a new alert for low disk space on SwiftStack Nodes.
  • The disk failure alert now includes more information about which metric was bad.
  • On the Manage Drives tab, unmounted devices may now be deleted.
  • The Manage Nodes list now displays node/controller connectivity status; nodes with problems will move to the top of the list.
  • The list of Rolling Swift Upgrades now includes the "from" and "to" versions of Swift.
  • The ipvsadm RPM is now included for Red Hat Enterprise Linux nodes.
  • Manage Nodes page checks and reports the status of each node.
  • Added option on Tune Cluster page to turn off Swift account auto-create, requiring a superuser to manually create each new account.
  • SwiftStack storage nodes will now use the deadline I/O scheduler for data drives.
  • In LDAP group-membership-based authentication, multiple simultaneous DN templates are now supported.
  • Reduced the default Cluster partition power to 16.
  • SwiftStack Controller On-Premises: relax disk space pre-install check for upgrades.
  • SwiftStack Controller On-Premises: clean up old deploy directories.
  • The Swift Web Console now supports multiple accounts. Any account that a user has access to can be used from the console.

Bug Fixes:

  • Fixed issue where Utilization data on SwiftStack nodes would get uploaded into the Swift cluster multiple times while node/controller connectivity was severed or the controller was otherwise unable to acknowledge receipt of the data
  • Fixed an issue where gradual capacity removal could get stuck at the end

Known Issues:

  • Under certain circumstances, adding a new account on the Swift Web Console will succeed, but selecting the account will fail or the account selection will get caught in a loop. Refreshing the page should resolve this issue if it occurs.
  • Users with unicode characters in their names are not currently supported in the Swift Web Console.

2.11.0.4 (Nov 7, 2013)

Bug Fixes:

  • Fixed a bug which would cause some gradual capacity adjustments to be "stuck"
  • Fixed a bug preventing users from accepting invitations to join SwiftStack as part of an existing Organization
  • Fixed a bug preventing TempURL keys from being retrieved; they could be set fine, and worked fine, but were accidentally filtered in GET/HEAD responses

2.11.0.1 (Oct 31, 2013)

Features:

  • The users/groups for "non-user Swift accounts" are now newline-separated, allowing user or group names with spaces.
  • The ssdiag script on nodes now performs some disk checks
  • A new script, decode_passwd, may be used on the /etc/swift/passwd file on nodes to decode the base64-encoded strings (but not the passwords, which are irreversibly hashed)

Bug Fixes:

  • Fixed an issue in 2.10.0.1 where Swift proxy server authentication would break in some circumstances
  • Fixed an issue in 2.10.0.1 where SwiftStack Auth users could not be deleted

2.10.0.1 (Oct 29, 2013)

Features:

  • Added support for Object Expiry. For more information on how to utilize Object Expiry, see Expiring Objects documentation
  • Added support for selecting the Partition Power of a cluster upon creation
  • Controller users can now start and monitor upgrades of the Swift software on their clusters
  • Packaged new version of Swift, 1.10.0.1, which resolves a bug that would cause object writes to report failure when a quorum was reached but the 3rd node was down
  • SwiftStack Auth now supports "non-user Swift accounts". In contrast with the user Swift accounts associated with each user, a non-user Swift account represents some other entity (e.g. a project). Note that this feature is still in beta, may change significantly, and documentation for it is not complete.
  • Non-user Swift accounts support access for any combination of users (e.g. SwiftStack Auth users, LDAP users, etc.) and groups (e.g. LDAP groups)
  • Non-user Swift accounts support read-only, read-write, and admin access levels
  • Substantial improvements to controller installation

Bug Fixes:

  • Default for Object server threads per disk lowered from 4 to 0 (disabled). Clusters created between June 13 and August 9 may have the value '4'. If the Object workers value is high, and the number of disks is high, the combination may create a total number of threads that exceeds the operating system's ability to effectively manage them. See Object Workers for more information on correctly setting these values.
  • Archived alerts page now reachable without any current active alerts
  • Continued work on improving robustness and clarity of the swift health check and ssdiag
  • Fixed bugs that could cause device formatting on nodes and require manual intervention

2.9.0.1 (Oct 4, 2013)

Bug Fixes:

  • Fixed SwiftStack Controller On-Premises installer to work around a CentOS/RHEL build bug in the psutil Python package

Note

This release was not deployed to platform.swiftstack.com since the bug fixed only affected CentOS/RHEL SwiftStack Controller On-Premises deployments.

2.9.0 (Oct 3, 2013)

Features:

  • Added support for StartTLS to LDAP middleware
  • Added support for Rate Limit middleware
  • Node XFS filesystems are now mounted with "inode64", allowing inodes to be allocated beyond the first 1TB of the drive
  • SwiftStack nodes now run the Swift Recon middleware
  • Added the ability to override the default styling of the Swift Web Console

Bug Fixes:

  • Fixed Domain Remap middleware to work with TempURL and FormPost middleware
  • Fixed bug where background work jobs could get stuck
  • Made the node Swift health check more robust, reducing spurious alerts
  • Fixed issue when using the SwiftStack Load Balancer, with SSL, with SSL terminating on the proxy servers, on CentOS nodes

Known Issues:

  • Users with "@" in their name cannot upload files with the Swift Web Console

2.8.0.3 (Sep 24, 2013)

Bug Fixes:

  • Fixed bug in the node Swift checker daemon introduced in 2.8.0.2

2.8.0.2 (Sep 24, 2013)

Bug Fixes:

  • Fixed bug with separate replication networks
  • Reinstated replication interface configuration
  • Fixed display bug in the Devices Only In Account/Container Ring table on the cluster Capacity Planning tab

2.8.0 (Sep 19, 2013)

Features:

  • Utilization API (BETA) -- see Utilization
  • Cluster capacity planning dashboard now shows usable free space
  • Added alert for node Swift daemons which fires when a Swift daemon is not running or otherwise not functioning
  • Several new LDAP middleware features -- see LDAP-based Authentication for SwiftStackAuth
    • Authenticated search (for installations which prohibit anonymous search)
    • Search filters can be used to whitelist/blacklist classes of users
    • Group membership binding: set a group (object class "groupOfNames") to contain the DNs of all allowed Swift end-users

Bug Fixes:

  • Removed replication interface configuration; it will return in a future release.
  • Cluster capacity planning table could have an incorrect drive count.
  • Fixed controller/node communication for CentOS 6.4 controllers.
  • Fixed failures with "format and mount" on large sets of devices.
  • Fixed double-counting of Proxy requests in Proxy Req Timing and Count graph.
  • Improved device synchronization between nodes and controller.
  • /srv/node is now properly excluded from updatedb/mlocate on CentOS.
  • The xfsprogs RPM is now included for Red Hat Enterprise Linux nodes.

Known Issues:

  • The Domain Remap middleware does not work correctly and will be fixed in a future release.

Internal:

  • Preparation for group membership binding with "posixGroup" groups (logins rather than DNs).

2.7.0 (Sep 5, 2013)

Features:

  • Replication network interface is now settable in the SwiftStack GUI.
  • Swift3 middleware documentation added.
  • Cluster-wide XFS inode stats graph added.
  • Controller User roles are now seen as hierarchical when set from the organization/users page.
  • LDAP middleware configuration UI improved and hopefully less confusing.

Bug Fixes:

  • SwiftStackAuth User management page now viewable by people using LDAP for controller auth with SwiftStack Controller On-Premises.
  • Fixed several bugs in the Controller User creation/invitation workflow.
  • Fixed crossdomain middleware configuration page 500 error.

Internal:

  • Plumbing to pave the way for multi-region clusters features in the controller UI, including configurable replica counts and write affinity.
  • Plumbing to pave the way for Utilization API.

2.6.11 (Aug 28, 2013)

  • Better support for CentOS/RHEL on Dell with non eth0 style network device names.
  • Additional Middleware documentation, updated docs on regions/zones editing.
  • Improvements to the LDAP middleware, including documentation.
  • Support Bulk Operation middleware via the UI.
  • Support Container Quota middleware via the UI.

2.5.50 (Aug 8, 2013)

  • Distributed Swift version now 1.9.2.
  • Capacity Planning graphs now available in Monitoring section of the UI.
  • Cluster tuning page now supports read affinity for multi-region clusters.
  • UI supports editing/adding regions.
  • Documentation updates.