*NOTE: This is a Release Candidate, for the latest GA release see releases *

(This Release Candidate is virtually identical to 10.0.3 except that the ServerTemplate has images for 7 operating systems on 4 clouds making it easier to try out the install-at-boot use-cases and making it easier to refer to a known-to-work image if you're having difficulties.)

Quick Reference

Item Description
Change log https://rightlink.rightscale.com/rll/10.0.rc4/CHANGES.md
Linux Base ServerTemplate https://us-3.rightscale.com/library/server_templates/RL10-0-3-Linux-Base/lineage/52389
Github repo for Base ServerTemplate https://github.com/rightscale/rightlink_scripts/tree/10.0.rc4
Install-at-boot Tag:
rs_agent:mime_include_url=https://rightlink.rightscale.com/rll/10.0.rc4/rightlink.boot.sh
How-to: import ServerTemplate, create server from ST, pick desired MCI, launch
Enable-running Script:
https://rightlink.rightscale.com/rll/10.0.rc4/rightlink.enable.sh
How-to: import ST, launch raw instance, SSH in, copy key from 'settings>API credentials', run:
curl -s https://rightlink.rightscale.com/rll/10.0.rc4/rightlink.enable.sh | bash -s -- -l -k <your-key> -d <deployment-name> -n my server -t RL10.0.rc4 Linux Base -a us-3.rightscale.com -c <cloud_type>
Known limitations Decommission scripts are terminated after a second or two instead of waiting up to 180 seconds due to errors in init system scripts. Upstart, systemd, and sysvinit are affected. A RightScript to hotfix these issues is available at https://us-4.rightscale.com/library/right_scripts/RightLink-10-0-3-fix-decommiss/lineage/53363. This issue will be fixed in 10.0.5. Meanwhile, this fix should also be applied to RC4 manually by running the above script.

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&start the enabled instance, create the rightscale user and support managed login, install the Rightlink init scripts, and install monitoring (collectd v4).

Note: except for vmWare the tests for this RC 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 (CentOS 7 on Rackspace is an example of this).

OS Clouds Images Image provenance Limitations
Ubuntu 14.04 AWS US-East: ami-6089d208
US-Oregon: ami-3b14370b

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)
Custom

no public image available

Rackspace Ubuntu 14.04 LTS (Trusty Tahr) (PVHVM) Rackspace public image  
Ubuntu 12.04 AWS US-East: ami-94faa6fc

Official Ubuntu image locator

 
Softlayer 25GB - Ubuntu / Ubuntu /
12.04-64 Minimal for VSI (202346)
Softlayer public image enable-running use-case only
Rackspace Ubuntu 12.04 LTS (Precise Pangolin) (PVHVM) Rackspace public image  
CentOS 7 AWS US-East: ami-96a818fe http://wiki.centos.org/Cloud/AWS  
Softlayer N/A   no official image available
Rackspace CentOS 7 (PVHVM) Rackspace public image fails on reboot due to yum crash
CentOS 6 Softlayer 25G CentOS 6 64-bit (10609) Softlayer public image enable-running use-case only
AWS, Rackspace N/A   problems with cloud-init installation
Debian 7 AWS US-East: ami-e0efab88 https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy  
RHEL 7 AWS US-East: ami-785bae10 AWS Marketplace  
Softlayer N/A   no official image available
Rackspace Red Hat Enterprise Linux 7 (PVHVM) Rackspace public image  
RHEL 6 AWS US-East: ami-8d756fe4 AWS Marketplace  
Softlayer 25G RedHat 6 64-bit (10660) Softlayer public image enable-running use-case only

How-To

Quick test

  • From the marketplace import the RightLink 10.0.rc4 Linux Base (fix link) 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 RLL: cloud-init for additional tags):

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

  • AWS, Softlayer, and VMware (vscale) have been tested; YMMV on other clouds

  • For GCE the tags and script differ slightly due to some problems with multi-part MIME userdata, which we expect to resolve soon, contact RightScale for info

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

  • The collectd monitoring script works for Ubuntu 14.04, Ubuntu 12.04, CentOS 7, CentOS 6.6, RHEL 6.5 and will strand for most other distros due to the lack of a functioning collectd.4.10 rpm

RL10 is Not Fully Compatible with RL6

  • 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 filesystem locations you need instead of a OS type variable.
  • No rs_tag command, instead RLL 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 creds are not output to stdout/stderr!