Release Notes: IBM Aspera Transfer Cluster Manager 1.2.2

Product Release: January 17, 2017

Release Notes Updated: January 17, 2017

This release of IBM Aspera Transfer Cluster Manager 1.2.2 for Amazon Web Services (AWS) and SoftLayer provides the new features, fixes, and other changes listed below. In particular, the Breaking Changes section provides important information about modifications to the product that may require you to adjust your workflow, configuration, or usage. In particular, the Breaking Changes section provides important information about modifications to the product that may require you to adjust your workflow, configuration, or usage. These release notes also list system requirements, including supported platforms, and known problems.

NEW FEATURES

  • HTTPD fallback has been disabled.
  • Max open files limit increased to avoid REDIS connection failures.
  • ScaleKV command timeouts are configurable in the atcm_config.
  • The calculation of the utilization of a cluster node is now configurable in the cluster configuration.

ISSUES FIXED IN THIS RELEASE

ATC-259 - NodeD continues to write to scalekv during upgrades.

ATC-258 - Auto-scaler takes several hours to terminate cluster nodes.

ATC-253 - SSH access from node to Cluster Manager breaks after replacing Cluster Manager with a new image.

ATC-244 - Stats-collector blocked on retrieving DB connections from pool.

ATC-236 - Bandwidth monitoring broken due to missing activity_bandwidth_logging setting in aspera.conf required for ES 3.7.2.

BREAKING CHANGES

If you are upgrading from a previous release, the following changes for this release may require you to adjust your workflow, configuration, or usage.

  • Cluster Manager now requires the activity_bandwidth_logging configuration enabled to use the Node API for querying status of transfers. New cluster templates provide this configuration, but you must add the configuration to the aspera.conf configuration file if you are upgrading from a previous version. Workaround: Update aspera.conf on the running cluster configuration and in the launch template with this setting:
    <server>
      <activity_bandwidth_logging>true</activity_bandwidth_logging>
    </server>

AMAZON MACHINE IMAGE (AMI) INFORMATION

Cluster Manager Image

Name: atc-clustermanager-3.7.2.93-2016-12-09T01-11-03Z

Region Registered Image
us-east-1 ami-0a4a4a1d
us-east-2 ami-XXXXX
us-west-1 ami-cde3b4ad
us-west-2 ami-b36fc4d3
ap-south-1 ami-XXXXX
ap-northeast-1 ami-60593407
ap-northeast-2 ami-XXXXX
ap-southeast-1 ami-9877dbfb
ap-southeast-2 ami-0b2f1768
eu-central-1 ami-XXXX
eu-west-1 ami-6ef3a91d
sa-east-1 ami-bb79e0d7
Transfer Node Image

Name: atc-node-3.7.2.95-2017-01-12T22-06-47Z

Region Registered Image
us-east-1 ami-22b25f34
us-east-2 ami-XXXX
us-west-1 ami-eb93c08b
us-west-2 ami-64982504
ap-south-1 ami-XXXX
ap-northeast-1 ami-8d7f03ea
ap-northeast-2 ami-XXXX
ap-southeast-1 ami-d4842fb7
ap-southeast-2 ami-c07571a3
eu-central-1 ami-XXXXX
eu-west-1 ami-56351f25
sa-east-1 ami-d941dbb5

SOFTLAYER MACHINE IMAGE INFORMATION

Cluster Manager Image
Data Center Registered Image
sjc01 1acf7291-b144-4752-bd1d-1b7eb8102fd2
Transfer Node Image
Data Center Registered Image
sjc01 35a61e5a-eca1-4341-878f-898887bd7102

PACKAGE INFORMATION

Cluster Manager
aspera-atcm-1.2.2.197d04.35-linux-64.tar.gz
clusterconsole.9.20161120225315.8abf72e.tar.gz
clusterconsole-ui.15.20161117164244.2567921.tar.gz
aspera-entsrv-3.7.2.136667-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.2.137926-linux-64-release.rpm
aspera-atcm-1.2.2.197d04.35-linux-64.tar.gz

KNOWN ISSUES

ATC-207 - The Cluster Manager Console displays a max 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