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: DuraCloud Media Streaming
- Details on new API calls to support HLS are here: DuraCloud REST API#AmazonS3StorageProvider
- All OpenStack-based storage provider options have been removed from DuraCloud, including both Rackspace and SDSC storage options. 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
- Recommended deployment changes
- An idle timeout setting is now expected in the Load Balancer, see: https://github.com/duracloud/deployment-docs/blob/master/duracloud-webapp-setup.md
- 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)
- List of all issues included in release
Issues discovered in testing
Issues discovered in testing:
| Issue | bb | db | |
|---|---|---|---|
| 1 |  | | |
| 2 | If you select a content item in the UI which has a "/" in the content ID (any file with a path), then select the "Refresh" button on the space, a 404 response comes back (white page with "Not Found"). This seems to be due to the "/" being displayed in the URL as an encoded value "%2F". If the "%2F" is replaced with a "/", the page loads just fine. | ||
| 3 | While: curl -u user:pass -X POST -H "x-dura-meta-test: ĽĔĘŔĴêť" https://bill.duracloud.org/durastore/bb-37-part1/test-file.txt fails with the expected error, curl -u user:pass -X POST -H "x-dura-meta-other: ♫♪♫" https://bill.duracloud.org/durastore/bb-37-part1/test-file.txt successfully updates the content properties with non-ascii characters Danny Bernstein : I wasn't able to reproduce: The following curl command returns a 400. Is it possible that you're running into an issue with Windows? curl -u user:pass -X POST -H "x-dura-meta-other: ♫♪♫" https://danny.duracloud.org/durastore/db-test/test-file.txt Bill Branan This does appear to be related to the Windows command line (git-bash shell in my case). The musical note characters appear in ContentResourceImpl.validateProperties() method as "???". Since question mark characters are part of US-ASCII, the check passes. So this is not a problem at the application level; it is, in fact, working as expected. |
Release Prep Steps
- Review and merge DuraCloud-1188 PR: https://github.com/duracloud/duracloud/pull/73/files
- Review and merge Transcoding Job Generator PR: https://github.com/duracloud/auxiliary/pull/2
- Review and merge Audit Task Generator Tool PR: https://github.com/duracloud/mill/pull/18
Updates in release
| Item | bb | db |
|---|---|---|
| (n/a) | (n/a) | |
| (n/a) | (n/a) | |
| | |
| | |
| #3 | | |
| | |
| | |
|
Build Tests
| Test | bb | db |
|---|---|---|
| mvn clean install (full build + integration tests) | | |
Release Actions
- Complete testing
- Perform version release (v5.0.0): https://github.com/duracloud/deployment-docs/blob/master/release-new-version.md
- Deploy release zip to production Beanstalk
- Update documentation (remove "Available in DuraCloud 5.0.0" notices)
- Create release notes in Github
