Release Notes: IBM Aspera Transfer Cluster Manager 1.2.3

Product Release: May 5, 2017

Release Notes Updated: May 8, 2017

This release of IBM Aspera Transfer Cluster Manager 1.2.3 for Amazon Web Services (AWS) and IBM Bluemix provides the new features, fixes, and other changes listed below. These release notes also list system requirements, including supported platforms, and known problems.

NEW FEATURES

  • IBM Aspera Enterprise Server Version
  • Cluster Manager
    • The cluster configuration now supports the ability to configure options for the following external services that the Cluster Manager monitors: Aspera Central, Aspera NodeD, Aspera TrapD, Aspera ScaleKV, HTTPD, ALEE, Nginx.
    • Cluster Manager now supports search capabilities for the event log. When browsing a cluster's nodes, you can search all fields in the event log.
    • Cluster Manager now displays the Node ID in the Activity Status tab.
    • Cluster Manager now supports IBM Bluemix S3 Object Storage.
    • Cluster Manager S3 storage configuration now supports the "Infrequent Access" storage class and AWS KMS server-side encryption.
  • Cluster Nodes
    • Cluster nodes are now configured with overcommit_memory, Transparent Huge Pages, and TCP backlog options.
  • Infrastructure
    • Aspera transfers can now be configured to work with S3 versioning, which enables customers to retain multiple versions of an object in the same S3 bucket. For more information, see IBM Aspera Enterprise Server Admin Guide: Using AWS S3 Versioning with Aspera.
    • Status reporting is decoupled from service health checks.
    • Cluster Manager now uses the SoftLayer VLAN ID option instead of the SoftLayer VLAN Number option to provision nodes.
    • VACUUM has been disabled in the asperacentral section of cluster templates.
    • ScaleKV has a faster restart time after aspera.conf changes.
    • Storage specs in the ATC API are now handled as opaque JSON structures.

ISSUES FIXED IN THIS RELEASE

ATC-320 - TrapD retries on browse operations provokes long timeouts.

ATC-291 - Cluster Manager cannot launch cluster nodes in the AWS eu-central-1 (Frankfurt) region.

TRAP-68 - In some situations, termination of Trapd in ATCM is unsuccessful or delayed for a long time.

AMAZON MACHINE IMAGE (AMI) INFORMATION

Cluster Manager Image

Name: atc-clustermanager-3.7.3.103-2017-04-07T14-19-05Z

Region Registered Image
us-east-1 ami-aa61ecbc
us-east-2 ami-79a5811c
us-west-1 ami-2ecd974e
us-west-2 ami-2baf3e4b
ap-south-1 ami-8cafdce3
ap-northeast-1 ami-9d8faefa
ap-northeast-2 ami-a0bf6dce
ap-southeast-1 ami-29e25c4a
ap-southeast-2 ami-452c2226
eu-central-1 ami-68e63507
eu-west-1 ami-ddaa92bb
sa-east-1 ami-b4d4b7d8
Transfer Node Image

Name: atc-node-3.7.3.119-2017-04-20T17-21-26Z

Region Registered Image
us-east-1 ami-55dc4043
us-east-2 ami-6874530d
us-west-1 ami-8d3410ed
us-west-2 ami-ea920e8a
ap-south-1 ami-582d5f37
ap-northeast-1 ami-e0e9c087
ap-northeast-2 ami-b739ebd9
ap-southeast-1 ami-05ad1566
ap-southeast-2 ami-41aba222
eu-central-1 ami-013fe26e
eu-west-1 ami-0b4e486d
sa-east-1 ami-61630e0d

SOFTLAYER MACHINE IMAGE INFORMATION

Cluster Manager Image
Data Center Registered Image
sjc01 7cc975e9-f23b-4a74-8dd9-ecdc62dde6fc
Transfer Node Image
Data Center Registered Image
sjc01 749fd691-3054-4786-999b-6b50143dc679

PACKAGE INFORMATION

Cluster Manager
aspera-atcm-1.2.3.4f3220.46-linux-64.tar.gz
clusterconsole.10.20170315092307.9e6d991.tar.gz
clusterconsole-ui.101.20170407064143.e25c0d2.tar.gz
aspera-entsrv-3.7.3.141652-linux-64-release.rpm
aspera-stats-collector-2.0.0.135636_135636-linux-64.tar.gz
aspera-ruby-rbenv-centos-7.rpm
aspera-ruby-2.2.4-centos-7-x86_64.rpm

Transfer Nodes
aspera-entsrv-3.7.3.142231-linux-64-release.rpm
aspera-atcm-1.2.3.4f3220.46-linux-64.tar.gz

KNOWN ISSUES

ATC-207 - The Cluster Manager Console displays a maximum of ten access keys in the drop-down menu.

PRODUCT SUPPORT

For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk