Release Notes - Version 4.x¶

Host Server Functionality¶

• Set security headers in Apache configuration (HOSTSERVER-821).

• The Host Server will now pause up to 5 seconds before sending the reply to the client if the download limit is exceeded, see DownloadLimit (HOSTSERVER-808).

  If the limit is exceeded, the Host Server will send an email to all System Administrators that receive emails. This notification is sent at most, once per hour.

• Depot overflow behavior has been changed significantly in 4.0 (HOSTSERVER-795)

  The Host Server now allows upload of files to continue when the depot of a space is over the 100% limit. However, files uploaded in this time may not be downloaded by clients. Only once the depot is below the 100% limit are those files released for download. Files uploaded before the overflow may always be downloaded.

  Depots now have an “overflow limit” and a “maximum overflow upload rate” which apply when the depot is full. This value depends on the actual depot storage limit as follows:

  Depot limit	Overflow limit	Max Upload Rate
  < 3 GB	10 GB	1 GB per day
  < 120 GB	50 GB	2 GB per day
  >= 120 GB	100 GB	4 GB per day

  When a depot reaches the depot limit plus the overflow limit, the depot is “frozen”. When a depot is frozen upload and download of files is no longer permitted. This means that the only way to “unfreeze” a depot is to increase the depot storage limit.

  In the frozen state deleting files, snapshots or emptying the trash may not work because of file uploads that may be queued before these operations prevent the operations from being synchronised.

  A number of emails are sent to the owner of the depot, the managers of the account that owns the depot, and to certain administrators of the Host Server. In the Admin Console you can mark an Admin User as a receiver of “Email Notifications”. By default, this is enabled for all administrators.

  Emails are sent when the storage exceeds 20% and 50% of the overflow limit, and when it exceeds 100% of the overlimit an email is sent to inform users and managers that the depot has been frozen.

  Note that these emails are in addition to the warning emails send when the depot is 80% and 100% full, however these emails are not sent to the Host Server administrators.

• The Host Server nows sends a notification emails to the depot owner, and managers of the account that owns the storage usage exceeds 80% and 100% of the storage limit (HOSTSERVER-768).

• The Host Server also sends notification emails if the depot network traffic reaches 80%, and when traffic exceeds the limit (HOSTSERVER-793). Emails are sent to the depot owner and to managers of the account that owns the depot.

  The 100% usage notification is also sent to Host Server administrators that have been selected to receive email notifications.

• Added functionality to recalculate the size used by a space, on disk and in the cloud (HOSTSERVER-738).

  Buttons are provided in the Admin Console to initiate the calculation of disk usage for a space and for all spaces in a depot.

  After a space has been restored, recalculation of disk usage is automatically scheduled.

  Depot size recalculation is triggered if a depot exceeds 100% storage usage, and the size of the depot has not been recalculated in the last 180 days.

• This version implements Amazon Signature Version 4. This can be enabled by adding the option UseSignatureV4=True to the S3Options setting (HOSTSERVER-766).

  Note that this signature type only works for Amazon (and fully Amazon compatible) object stores, Azure and OpenStack still use the Version 2 signatures.

• Added the S3Region setting which determines the region used in Amazon Version 4 signing process. By default the value “eu-west-1” is used.

  The region must be set according to the following mapping: Amazon Regions and Endpoints

• The Host Server will now automatically delete spaces in a depot to reduce disk usage, when the limit of a depot is exceeded by a certain amount (HOSTSERVER-759). See Depot Overflow and Automatic Space Reduction for details.

  Two settings have been added to support this feature: EnableSpaceReductionProcess` and ``AllowAutoDeleteSpaces (see Resource Management Settings for details).

  Spaces will not be deleted if the depot has been active within the last 6 months.

• The Apache module and the s3d service now check the database version. If the database structure in not up-to-date the Apache module generates an error, but will continue normally as soon as the database is update. The s3d quits if the database version is not he require version, currently this is version 3.7 level.

• Added TransferConnection setting which is used to support the transfer of the Host Server Object Store to a different service provider (see TransferConnection) (HOSTSERVER-771).

• Added the UseIPWorks setting (default: False). Set this value to True in order to use the IPWorks-based cloud access implementation.

• Added various binary hardening measures. Maximum POST request size for API calls is is now 10 MB.

Administration Console¶

Note

Please clear the browser cache after the server update.

• You can now specify whether snapshots should be enabled or disable for a new space on the depot level. Here you can choose between always enabling or disabling snapshots for spaces created in the depot, or you can make it depending on the value of the EnableSnapshotsByDefault setting. This is the default (HOSTSERVER-785).

  Note that changing this value does not change whether snapshots are enabled or not for existing spaces.

• Using “Set Space Status” and “Unset Space Status” on the space depot page, you can now set and remove a status from all spaces in a depot. The status’ that may be set/removed are: “Disabled”, “Readonly”, “Deactivated for maintenance” and “Deactivated by provider” (HOSTSERVER-761).

• On the Space Depot page the “Recalc Depot Size” button can be used to initiate the recalculation of the sizes of all spaces in the depot. This process is performed in the background and may take a while.

• On the Space Details page you can use the “Recalculate Disk Usage” button to initiate recalculation of the disk space used. This process is performed in the background and may take a while.

• On the Space Depot page, the “Restore Spaces” button may be used to undelete all spaces in the depot. This function can be used after restoring the space of a depot from backup.

  If the space directory does not exist on disk, then the space cannot be restored, and this will cause the process of restoring spaces to stop.

  An empty space directory will be restored as an empty space. After restoring a space, recalculation of the disk space of the space will be initiated.

• It is now possible to set a volume space limit to 0, which means unlimited.

• The Admin Console can now “rollback” a failed restore snapshot attempt (HOSTSERVER-807). This case is clearly shown in the Admin Console, if the space is in the “Restoring” state, and a notice on the space indicates that a restore to snapshot is in progress. If this operation is not completed within a few minutes it is OK, to press the “Space Restored” button, to undo any changes to the space log files.

• The Object Store key (setting S3SecretKey) is no longer shown completely in the Admin Console for security reasons (HOSTSERVER-813).