Getting Started with Aspera On Demand for Softlayer

Overview

This article is for customers who want to deploy Aspera On Demand on Softlayer.  If you are still investigating Aspera On Demand options and want to learn more, please view the Aspera Cloud site for more info.  This is a general document that covers the various options for purchasing, obtaining and provisioning Aspera On Demand products, including directly purchasing from Aspera.  Please note that as of April 2015, we now provide pre built images of the Aspera on Demand product line.  Additional information below.

 

Ready

This article assumes that you are familiar with the following:

  1. How to login to your Softlayer account.
  2. How to provision a Linux CCI image in Softlayer.
  3. The Aspera On Demand offerings.  If you need more info, please review our Cloud Site.
  4. How to use SSH to connect to your Softlayer Linux image.
  5. You have completed your purchase of one of the Aspera On Demand products.  If you still need to complete this step, please contact our Sales team via this link.  

 

Set

At this point, we assume that you have the following:

  1. Softlayer Image ID for the Aspera on Demand product you have purchased.  This should come from Aspera Sales (note: these are private images that are shared with your Softlayer account). 
  2. Aspera On Demand entitlement (received from your Aspera contact)
  3. You have decided on a persistent storage option where you will be storing your data.  This can be an NFS mount or SWIFT Object Storage.  An article on setting up SWIFT can be found here.
  4. If you plan to perform your own installation of Aspera on your own custom image, you will also need credentials to download the Aspera on Demand software.  Please contact your Aspera Sales person, if you have not received these credentials.

 

Go

This section is written in two parts:  Image provisioning and Manual provisioning.   As of spring 2015, we now have pre packaged virtual machine images available on Softlayer.  We highly recommend that you use these images, since it makes the provisioning process much easier.  However, if your circumstance prevent you from using them, we understand.  Please use the instructions below.

 

Image provisioning (for booting up a pre-packaged Aspera on Demand Image)

  1. Log into the Softlayer portal
  2. Search for the Aspera on Demand image.  Once you are logged into the Softlayer Portal, you can search for a specific image.  In this screenshot you can see that I am filtering for the "Shares on Demand" image.  A list of existing images can be found in our release notes, located HERE.

    Image_Search_filtering.png
  3. Provision the server with the specifications you require   Launch_Image.png
  4. Login to the Aspera on Demand.   Point your browser to the IP address of the server you have just launched.  The login is 'admin' and the password is the unique Image ID.  The Image ID can be obtained from the Softlayer Image listing URL.  See screenshot, where I have highlighted the Image ID.
    Unique_Instance_iD.png
  5. Entitle your Aspera on Demand system

 

Manual provisioning  (for installing Aspera on your own Softlayer Linux 64 image).

  1. Provision your Linux 64 image (Red Hat 6.x or CentOS 6.x recommended)
  2. Login via SSH and sudo to 'root' user
  3. Download Aspera software - depending on the product bundle you have purchased (e.g. Enterprise Server, Shares, Console, Faspex)
  4. Install and configure Aspera software
  5. Configure the server to use On Demand Entitlements
  6. Enable the Aspera Trapd Service  (# /opt/aspera/bin/astrap-config.sh enable)
  7. Configure Aspera server for Object Storage (e.g. Document Root)

 NOTE: Faspex v.3.7.8+, Shares v.1.7.3+ and Console v.2.3.2+ have its own entitlement steps.  If you installed any of these products, please see the following instructions.

To entitle Faspex v.3.7.8 or higher

# export RAILS_ENV=production 
# asctl faspex:rake entitlement:config_license_server EL_KEY="d1234567-7fac-409d-9200-e2cb1234567c" EL_CUSTOMER_ID="foo"

To entitle Shares v.1.7.3 or higher

# /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="d1234567-7fac-409d-9200-e2cb1234567c" EL_CUSTOMER_ID="foo"

To entitle Console v.2.3.2 or higher

# 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="d1234567-7fac-409d-9200-e2cb1234567c" EL_CUSTOMER_ID="foo"

 

Example Document root setup:

The following is an example taken from softlayer (user/password were changed).

When the object storage is created the credentials are shown as follow - for the storage cluster located in Dallas-5:

Object Storage information

Authentication Endpoint

Private: https://dal05.objectstorage.service.networklayer.com/auth/v1.0/

Username:

IBMOS303456-2:someuser

API Key (Password):

af879bf5737b3e7f98919d98f524c52d62771a736066b39606968fef4db78f77

 

Docroot Example:

<absolute>swift://IBMOS303456-2%3asomeuser:af879bf5737b3e7f98919d98f524c52d62771a736066b39606968fef4db78f77@dal05.objectstorage.service.networklayer.com/test</absolute>

Note: 

  1. The URI does not include the /auth/v1.0/. This has to be defined later.
  2. Both above URLs (public and private)  would work, but the best is to use the private one that uses the internal network (on eth0) to communicate with the storage.    Using the public URL will incur additional egress costs and will also create additional traffic, as the connection to object storage will compete with the FASP traffic coming over the WAN.
  3. Note that the ":" in the user name must be url encoded ("%3A").

Additional required settings

The following settings must also be changed for Softlayer and depend on how the storage servers are configured within the data center.

Edit /opt/aspera/etc/trapd/swift.properties, uncomment and change the auth property - as follow:

# Auth path (looks as a virtual path)

# Default is '/v1.0'

aspera.swift.endpoint.auth-path=/auth/v1.0

  1. multipart support

If the SWIFT storage is < 1.12 release (It does not support “Static Large Objects”) the Trap init script must be changed in method trap_init_start() by adding the colored line below:

# disable checks done on open-write for small files

#PROPS="$PROPS -Daspera.session.upload.start-check-small-file.enabled=false"

PROPS="$PROPS -Daspera.swift.session.upload.large-object.dynamic=true" 

Restart the Aspera Trapd service

# service asperatrapd restart

 

Have more questions? Submit a request

2 Comments

  • Avatar
    Crystal Yeung

    Added the following to the KB.

     

    NOTE: Faspex v.3.7.8+, Shares v.1.7.3+ and Console v.2.3.2+ have its own entitlement steps.  If you installed any of these products, please see the following instructions.

    To entitle Faspex v.3.7.8 or higher

    export RAILS_ENV=production

    asctl faspex:rake entitlement:config_license_server EL_KEY="d1234567-7fac-409d-9200-e2cb1234567c" EL_CUSTOMER_ID="foo"

    To entitle Shares v.1.7.3 or higher

    /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="d1234567-7fac-409d-9200-e2cb1234567c" EL_CUSTOMER_ID="foo"

    To entitle Console v.2.3.2 or higher

    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="d1234567-7fac-409d-9200-e2cb1234567c" EL_CUSTOMER_ID="foo"

     

  • Avatar
    Larbi BELBECIR

    You should add a section on entitlement via the web-ui as well as a link to Clients

Please sign in to leave a comment.
Powered by Zendesk