DuraCloud 6.0.1

Release Notes

Bug fix release to resolve a single issue. Ensures that calls to set content properties do not clear the instance cache.

Issues Resolved

• DURACLOUD-1225: Each call to set content properties is causing a notification to be sent to clear the provider cache

DuraCloud 6.0.0

Release Notes

The 6.0.0 release of DuraCloud updates the AWS client connections used to communicate with S3 and Glacier storage and also removes the DPN Storage Provider type and references to allow for greater focus on the Chronopolis Storage Provider. While there are several dependency updates and related fixes, there are no significant changes with this release that will be visible by application users.

Thanks to Andy Foster from the University of Toronto for his work on the AWS client updates!

Issues Resolved

• DURACLOUD-1219: Replace use of AmazonS3Client (deprecated) with AmazonS3ClientBuilder
• DURACLOUD-1214: Modify/remove DPN storage provider type and language from Duracloud
• DURACLOUD-1221: Management Console: Allow users to set region on Chronopolis storage providers
• DURACLOUD-1222: Ensure that the S3ProviderUtil client cache is flushed on change to the storage provider info
• DURACLOUD-1218: Update commons-fileupload dependency version
• DURACLOUD-1217: Update test jetty dependency in common package

Deployment Notes

• In the DuraCloud application Elastic Beanstalk configuration, an Environment Property named AWS_REGION must be set to the default AWS region of your deployment (e.g. us-east-1). The updated AWS client requires that all calls specify a region.
  • The updated AWS client is more sensitive to region settings. All buckets in each S3 account under DuraCloud must belong to the AWS region specified in the Management Console (or the default defined in the AWS_REGION value above). If a storage provider region needs to change, all spaces from the original region must first be removed, then the region changed, then new spaces created.
• Prior to deployment, ensure that no accounts have storage providers with type "DPN" in the Management Console. Accounts with a DPN provider will be inaccessible after the upgrade.
• If you are running a DuraCloud Bridge (snapshot baseline), the following updates will be required:
  • In the bridge config init JSON document: change "dpnEmailAddresses" to "targetStoreEmailAddresses"
  • In the bridge database, update the state for any in-process snapshot or restore actions
    • Snapshot: State values must be updated, e.g. (replace [bridge_db] with your database schema name):

    UPDATE [bridge_db].snapshot SET status="REPLICATING_TO_STORAGE" WHERE status="WAITING_FOR_DPN";
    

    • Restore: State values must be updated, e.g. (replace [bridge_db] with your database schema name):

    UPDATE [bridge_db].restoration SET status="RETRIEVING_FROM_STORAGE" WHERE status="WAITING_FOR_DPN";
    UPDATE [bridge_db].restoration SET status="STORAGE_RETRIEVAL_COMPLETE" WHERE status="DPN_TRANSFER_COMPLETE";
    UPDATE [bridge_db].restoration SET status="VERIFYING_RETRIEVED_CONTENT" WHERE status="VERIFYING_DPN_TO_BRIDGE_TRANSFER";
    

DuraCloud 5.1.0

Release Notes

The 5.1.0 release resolves several issues and brings transfer improvements in the DuraCloud client tools. Support was also added for allowing secondary storage providers to be managed independently. A big thank you to the Texas Digital Library for their assistance in selecting tasks and working through issues in this release!

Issues Resolved

• DURACLOUD-1212: Fixes error while adding tags via the UI
• DURACLOUD-1210: Sets default log level for all apps and exposes log.level as a -D system property for all commandline tools.
• DURACLOUD-1209: Updates Jetty dependencies in the SyncTool
• DURACLOUD-1191: Adds support for range requests and automatic retrying of midstream failures from point of failure.
• DURACLOUD-1201: Adds support for new storage account property that allows non-root users to modify secondary storage providers via Duradmin
• DURACLOUD-623: Adds "Forgot Password" link to the Duracloud login page
• DURACLOUD-956: "Add Space" button no longer displayed upon login for user-level account log-in.

Deployment Notes

This release depends on updates to the management-console which are detailed on the 4.1.0 release page

DuraCloud 5.0.0

Release Notes

• HTTP Live Streaming (HLS) is now available as an option for streaming files. HLS is widely supported by browsers and mobile devices and allows for non-Flash video and audio players. HLS is supported by HTML5 video and audio tags. Both open and secure streaming options are available for HLS through DuraCloud.
  • Content to be streamed via HLS must first be transcoded into a format supported by HLS (generally .ts segment files with .m3u8 playlists)
  • More details on HLS streaming can be found in the documentation
  • Details on new API calls to support HLS can be found in the REST API documentation
• All OpenStack-based storage provider options have been removed from DuraCloud, including both Rackspace and SDSC. This change paves the way for features in future releases which are more closely aligned with the AWS S3 API, such as multi-part upload.
• Content retrieval calls can now include a Range header to request parts of a content file. This is particularly useful for large files when you only need a portion of the file or when you'd like to download portions of the file in parallel to speed retrieval.
• Generated manifest files now include a Content-Encoding header to specify the format of the manifest
• Attempts to include non-ASCII characters in content properties now results in an immediate error (rather than failing silently)
• The Retrieval Tool now provides a useful error message if the user's credentials are not correct
• The description field in snapshots is now truly optional

Deployment Notes

• An idle timeout setting is now expected in the Load Balancer, see the deployment documentation for details
• The Elastic Beanstalk environment should be updated to the latest tomcat environment: Tomcat 8 with Java 8 running on 64bit Amazon Linux/3.0.3. (This change will also upgrade Apache to 2.4.33)
  • The 5.0.0 release includes changes to the Apache configuration to support Apache 2.4.33. These changes will fail to deploy in an older Apache version. At the same time, the Apache configuration in the previous (4.4.6) release will cause the environment update to fail. Together this presents a situation where neither the version or the environment can be updated without failure due to incompatible Apache settings. This can be resolved by:
    1. Starting an Elastic Beanstalk environment update to the latest Tomcat 8/Java 8 version
    2. As each instance is started, log in and replace the contents of '/etc/httpd/conf.d/elasticbeanstalk.conf' with the 5.0.0 version
    3. Start Apache (it will have failed to start): sudo service httpd start. This will allow the environment update to complete successfully
    4. After the environment update completes, perform the version update to bring the application to v5.0.0
  • The updated Apache version has a more strict policy on allowable header values which results in the DuraCloud UI not being able to complete loading the spaces list (appearing to hang) when a user in the account has a username with an @ symbol (usually an email address) and there are space ACL settings in the account listing that user. This is due to the fact that DuraCloud uses headers to transfer space ACL details. A ticket has been opened to disallow the @ symbol in usernames, but this will apply only to new users. The work-around for existing users is:
    1. Before upgrading to 5.0.0, review space ACLs. Any that contain an @ symbol need to be removed. If the user has Administrator rights, they will continue to have access to all spaces. If the user does not have Administrator rights, they can be added to a goup, and the group be given permissions on the space.
    2. Provide users with an @ symbol in their username the opportunity to create a new user profile, then duplicate their permissions and remove the original user.

A list of all issues included in the 5.0.0 release can be found here

DuraCloud 4.4.6

Resolves issue in 4.4.5: https://jira.duraspace.org/browse/DURACLOUD-1183

DuraCloud 4.4.5

This release applies code style guidelines

• https://jira.duraspace.org/browse/DURACLOUD-889

This release also adds new documentation

• https://jira.duraspace.org/browse/DURACLOUD-1181
• https://jira.duraspace.org/browse/DURACLOUD-1182

DuraCloud 4.4.4

duracloud-4.4.4

Updates version to 4.4.4

DuraCloud 4.4.3

Release includes updates to fix the following issues:

• DURACLOUD-1161 - SyncTool doesn't work on workstation with language different than En
• DURACLOUD-1164 - Allow mill to use SES in region different than Virginia
• DURACLOUD-1165 - Allow to use the Glacier Storage in region other than Virginia
• DURACLOUD-1174 - When a call to update a file in S3 storage fails, the original file is removed
• DURACLOUD-1171 - Retrieval Tool logging error on startup

duracloud-4.4.2

Updates version to 4.4.2

duracloud-4.4.1

Updates version to 4.4.1