10.1.3 it is a point release for the last major GA release (10.1.2). This release includes:

  1. Added /rll/proc/shutdown_kind to distinguish between stop and terminate during running of decommission scripts. For further reference see Local and Proxied HTTP Requests.
  2. Bug fix: Set Host field correctly for API requests proxied through RightLink

Quick Reference

Item Description
Change Log https://rightlink.rightscale.com/rll/10.1.3/CHANGES.md
Linux Base ServerTemplate https://www.rightscale.com/library/server_templates/RightLink-10/lineage/53250
Github repo for Base ServerTemplate https://github.com/rightscale/rightlink_scripts/tree/10.1.3
Install-at-boot Tag:
To run: Import Linux Base ServerTemplate, create server from ST, pick desired MCI, launch
Enable-running Script: https://rightlink.rightscale.com/rll/10.1.3/rightlink.enable.sh
To run: Import Linux Base ServerTemplate, launch raw instance, copy key from 'settings>API credentials', SSH into raw instance
Run command:
curl -s https://rightlink.rightscale.com/rll/10.1.3/rightlink.enable.sh | bash -s -- -l -k <your-key> -d <deployment-name> -n my server -t RightLink 10.1.3 Linux Base -a us-3.rightscale.com -c <cloud_type>

RightScale tested images

The following images were tested by RightScale and known to work with this version of RightLink 10. This list is not intended as a recommendation of these images, it is simply intended as a reference so you can locate known-to-work images and compare with your own images if you are having difficulties.

Known to work means that the following features work: enable a running bare instance using the rightlink.enable.sh script, reboot the instance, stop and start the enabled instance, create the rightscale user and support managed login, install the Rightlink init scripts, and install monitoring (collectd).

Note: except for VMware the tests for this release use official images prepared by the OS vendor or the cloud vendor. In some cases this leads to failures due to problems with the specific images that can easily be overcome using a custom image.

OS Clouds Images Image provenance Limitations
Ubuntu 14.04 AWS US-East: ami-6ab2a702
US-Oregon: ami-d986b7e9

Official Ubuntu image locator

Softlayer 25GB - Ubuntu / Ubuntu /
14.04-64 Minimal for VSI (226478)
Softlayer public image enable-running use-case only
vmWare (RCA-V) QA_0.7.2_Fixed_DataSource_Ubuntu_
14.04_20150204.1_784bd81bd3cce8 (not public)

no public image available

Openstack trusty-server-cloudimg-amd64-disk1.img from cloud-images.ubuntu.com

Official Ubuntu image locator

Ubuntu 12.04 AWS US-East: ami-f6132b9e

Official Ubuntu image locator

Softlayer 25GB - Ubuntu / Ubuntu /
12.04-64 Minimal for VSI (202346)
Softlayer public image enable-running use-case only
Openstack precise-server-cloudimg-amd64-disk1.img from cloud-images.ubuntu.com

Official Ubuntu image locator

CentOS 7 AWS US-East: ami-96a818fe http://wiki.centos.org/Cloud  
Softlayer N/A   no official image available
Openstack CentOS-7-x86_64-GenericCloud-1503.qcow2 from cloud.centos.org/centos/7/images http://wiki.centos.org/Cloud  
CentOS 6 Softlayer 25G CentOS 6 64-bit (10609) Softlayer public image enable-running use-case only
AWS N/A   problems with cloud-init installation
Debian 7 AWS US-East: ami-baeda9d2 https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy  
Openstack CentOS-6-x86_64-GenericCloud-20141129_01.qcow2 from cloud.centos.org/centos/6/images http://wiki.centos.org/Cloud  
RHEL 7 AWS US-East: ami-12663b7a AWS Marketplace  
Softlayer N/A   no official image available
RHEL 6 AWS US-East: ami-b0fed2d8 AWS Marketplace  
Softlayer 25G RedHat 6 64-bit (10660) Softlayer public image enable-running use-case only


Quick Test

  • From the marketplace import the RightLink 10.1.3 Linux Base ServerTemplate published by RightScale Engineering.
  • Create a Server from the ServerTemplate
  • Select an appropriate MCI and launch, the ST should go operational, you should see an audit entry with the boot scripts, you should be able to SSH into the instance using your managed SSH key and you should be logged in as user 'rightscale' from which you can sudo

Adapting the Base ServerTemplate

  • You can clone the base ST and insert a different MCI of your choice, the MCI needs to have the required RS_agent tags (see below)
  • Alternatively, you can create you own ST using your own MCI
  • Standard MCI tags (see RightLink 10: Cloud-init for additional tags):

    rs_agent:type=right_link_lite rs_agent:mime_include_url=https://rightlink.rightscale.com/rll/10.1.3/rightlink.boot.sh

  • AWS, Softlayer, Openstack Juno, and RCA-V (vSphere) have been tested; Other images on other clouds with a functioning cloud-init should work, but YMMV (see above).

  • For GCE, only Ubuntu images contain cloud-init. These images install and run RightLink, however managed login will not work due to the google manage_accounts.py daemon script running and resetting permissions on the ssh authorized_keys file. Other OSes on GCE may be bootstrapped with alternate GCE userdata and tags, contact RightScale for info.

  • For CoreOS the tags and script also differ slightly due to limitations in CoreOS' cloud-init implementation, contact RightScale for info.

  • The collectd monitoring script only works for Ubuntu and RHEL/CentOS/Compatible OSes and will strand for most other distros as there isn't code to install collectd for those alternate OSes. The monitoring script was verified with RHEL/CentOS 6 and 7 and Ubuntu 12.04 and 14.04 but should work on other versions as well.

  • The environment variables available to RightScripts are different, and there are no RS_REBOOT or RS_OS_TYPE variables. Write idempotent scripts using the capabilities of the shell, such as testing for the presence of files. Dispatch based on the presence of tools or file system locations you need instead of a OS type variable.
  • No rs_tag command, instead RightLink 10 can proxy API 1.5 requests and add authentication along the way
  • No built-in Chef support
  • RightScript log output is not sanitized to remove credential values! (Some of them are by the platform but this will change soon.) The sanitization has lots of problems, the only proper solution is for the script writer to ensure sensitive credentials are not output to stdout/stderr!
  • For a full list of changes see Incompatibilities with RightLink 6