Server Set up in OpenStack Swift Storage

With an Aspera entitlement, an Aspera server can be installed on an instance in a private or public cloud that uses OpenStack Swift storage, and run as a self-managed, cloud-based server that enables high-speed transfers with your OpenStack Swift storage.

Prerequisites:

  • You have a Swift container.
  • You launched a cloud virtual machine instance.
  • You can SSH into your server as root.
  • You have Linux Kernel 2.6.34 or higher.
  1. SSH into your VMI as root: 
    # ssh root@host_ip_address
  2. Update sshd_config to enable port 33001 and password authentication.
    Edit /etc/ssh/sshd_config and make the following changes:
    • Enable TCP/33001 by adding the text Port 33001. For example,
      ...
Port 22
Port 33001
    • Enable password authentication by uncommenting the line #PasswordAuthentication no and changing the value to yes. For example,
      ...
PasswordAuthentication yes

    Save your changes.

  3. Restart the sshd service to activate the changes. 
    # systemctl sshd restart
  4. Configure the local firewall.
    Ensure that the local firewall is configured to support Aspera. Allow inbound connections on TCP/22, TCP/33001, and UDP/33001.
  5. Verify that /etc/hosts contains an entry for 127.0.0.1 localhost.
  6. Disable SELinux.
    For instructions, see Disabling SELinux.
    Warning: If this procedure is done incorrectly, you system might be unable to boot.
  7. Create Aspera system user accounts and set passwords.
    The High-Speed Transfer Server uses the system accounts to authenticate connections and these must be in place before you can transfer.
  8. Install High-Speed Transfer Server on your VMI.
    Use your customer login credentials to download the Aspera installer and product guide from the Aspera website:

    https://downloads.asperasoft.com/downloads

    If you need help with your credentials, contact your Aspera account manager. Follow the instructions in the product guide to install and set up the server.

  9. Enable Entitlement and register by running the following commands: 
    # /opt/aspera/bin/asalee-config.sh enable
# systemctl asperanoded restart
# /opt/aspera/bin/alee-admin register customer_ID entitlement_ID
    To entitle Faspex (v.3.7.8+), Shares (v.1.7.3+), or Console (v.2.3.2+), run the corresponding command.
    • To entitle Faspex:
      # export RAILS_ENV=production 
# asctl faspex:rake entitlement:config_license_server EL_KEY="entitlement_id" EL_CUSTOMER_ID="customer_id"
    • To entitle Shares:
      # /opt/aspera/shares/bin/run bash -c 'cd /opt/aspera/shares/u/shares && RAILS_ENV=production bundle exec rake aspera:ami:entitlement:config_license_server EL_KEY="entitlement_id" EL_CUSTOMER_ID="customer_id"
    • To entitle Console:
      # cd /opt/aspera/console/ 
# export RAILS_ENV=production # export PATH=/opt/aspera/common/ruby/bin:$PATH # rake aspera:ami:entitlement:config_license_server EL_KEY="entitlement_id" EL_CUSTOMER_ID="customer_id"
  10. Enable the Aspera Trapd service by running the following command: 
    # /opt/aspera/bin/astrap-config.sh enable
  11. Set an OpenStack Swift docroot for the transfer user. 
    # asconfigurator -x "set_user_data;user_name,username;absolute,swift://account_id:api_key@auth_url/my_bucket

    Values for account_id, api_key, auth_url, and my_bucket must be URL encoded. For instructions, see URL Encoding.

  12. Restart the Aspera Noded service. 
    # systemctl asperanoded restart