10.3.0 is a major GA release that brings support for Windows Azure cloud (classic), CoreOS, Linux Base Monitoring, and Custom Monitoring. This release includes:
Features
- Add custom monitoring script support that is compatible with collectd exec style plugin scripts.
- Add support for UCA on Windows
- Add Docker monitoring and tagging
- Added numerous metrics to
all
category for built-in monitoring:- df-MOUNT/(df_complex-free,df_complex-used)
- disk-DEVICE/(disk_merged,disk_octets,disk_ops,disk_time)
- swap/(swap-free,swap-used)
- swap_io/(swap_io-in,swap_io-out)
- processes/(fork_rate, ps_state-blocked, ps_state-paging, ps_state-running, ps_state-sleeping, ps_state-stopped, ps_state-zombies)
- interface-NAME/(if_octets, if_errors, if_packets)
- memory/(memory-used, memory-free)
- Fixed cpu-N/cpu-irq to be cpu-N/cpu-interrupt
Fixes
- Improve userdata fetcher service bundled with Windows to skip scraping userdata if we already have valid credentials
- Fixed memory leak in which goroutine would be left behind after running an operational script
- Fixed agent not starting up if localhost is not defined or incorrect
- Bump rightscale networking scripts to v1.0.1. Fixes installation on CentOS/vSphere if selinux is disabled
- Update install and enable scripts to handle CoreOS filesystem setup
- Remember the level of built-in monitoring across RightLink service restarts
- Add in doppelganger detection for EC2 by killing duplicate launches
- Update service configs to use current format of /var/lib/rightscale-identity
- Only add BOM on Powershell scripts that do not have one already
- Fixed service failing to start when disabling then enabling an instance on CentOS/RHEL 7
- Fixed final audit entries being cut short for upgrade script on occasion
- Do not turn on utilization monitoring by default
- Fixed boot bundle sometimes not running after stop/start due to stale state file on Windows 2008R2
Quick Reference
Item | Description |
---|---|
Change Log | https://rightlink.rightscale.com/rll/10.3.0/CHANGES.md |
Github repo for Base ServerTemplates | https://github.com/rightscale/rightlink_scripts/tree/10.3.0 |
Linux Base ServerTemplate | https://www.rightscale.com/library/server_templates/RightLink-10/lineage/53250 |
Linux Install-at-boot | To run: Import Linux Base ServerTemplate, create server from ST, pick desired MCI, launch |
Linux Enable-running | Script: https://rightlink.rightscale.com/rll/10.3.0/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.3.0/rightlink.enable.sh | bash -s -- -l -k |
Windows Base ServerTemplate | https://www.rightscale.com/library/server_templates/RightLink-10/lineage/55964 |
Windows Enable-running | Script: https://rightlink.rightscale.com/rll/10.3.0/rightlink.enable.ps1 To run: Import Windows Base ServerTemplate, launch raw instance, copy key from 'settings>API credentials', Remote Desktop into raw instance Run command: $wc = New-Object System.Net.WebClient $wc.DownloadFile( Powershell -ExecutionPolicy Unrestricted -File rightlink.enable.ps1 -k |
Known Limitations |
|
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 or rightlink.enable.ps1 script, reboot the instance, stop and start the instance, create the rightscale user and support managed login (Linux only), install the RightLink 10 init scripts, and install monitoring (collectd on Linux).
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 |
---|---|---|---|
Ubuntu 14.04 | AWS | US-Oregon: ami-abc620cb | Official Ubuntu image locator |
Azure | b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB | Microsoft Azure Marketplace | |
projects/ubuntu-os-cloud/images/ubuntu-1404-trusty-v20160114e | Official Ubuntu image locator | ||
OpenStack | ubuntu-14.04-server-cloudimg-amd64-disk1.img | Official Ubuntu image locator | |
Ubuntu 12.04 | AWS | US-Oregon: ami-08c92f68 | Official Ubuntu image locator |
Azure | b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-12_04_5-LTS-amd64-server-20160201-en-us-30GB | Microsoft Azure Marketplace | |
projects/ubuntu-os-cloud/images/ubuntu-1204-precise-v20160114 | Official Ubuntu image locator | ||
OpenStack | ubuntu-12.04-server-cloudimg-amd64-disk1.img | Official Ubuntu image locator | |
CoreOS | AWS | US-Oregon: ami-abc82ecb | Official CoreOS image locator |
Azure | 2b171e93f07c4903bcad35bda10acf22__CoreOS-Stable-835.12.0 | Official CoreOS image locator | |
projects/coreos-cloud/images/coreos-stable-835-12-0-v20160202 | Official CoreOS image locator | ||
OpenStack | coreos_production_openstack_image.img.bz2 | Official CoreOS image locator | |
CentOS 7 | AWS | US-Oregon: ami-d440a6e7 | Official CentOS image locator |
Azure | 5112500ae3b842c8b9c604889f8753c3__OpenLogic-CentOS-71-20150731 | Microsoft Azure Marketplace | |
OpenStack | CentOS-6-x86_64-GenericCloud-1601.qcow2 | Official CentOS image locator | |
CentOS 6 | AWS | US-Oregon: ami-1255b321 | Official CentOS image locator |
Azure | 5112500ae3b842c8b9c604889f8753c3__OpenLogic-CentOS-67-20150815 | Microsoft Azure Marketplace | |
OpenStack | CentOS-6-x86_64-GenericCloud-1601.qcow2 | Official CentOS image locator | |
Windows 2012R2 | AWS | US-Oregon: ami-83a5bce2 | Amazon Windows AMIs |
Azure | a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-R2-20160126-en.us-127GB.vhd | Microsoft Azure Marketplace | |
Windows 2012 | AWS | US-Oregon: ami-8ca6bfed | Amazon Windows AMIs |
Azure | a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-Datacenter-20160125-en.us-127GB.vhd | Microsoft Azure Marketplace | |
Windows 2008R2 | AWS | US-Oregon: ami-c5a7bea4 | Amazon Windows AMIs |
Azure | a699494373c04fc0bc8f2bb1389d6106__Win2K8R2SP1-Datacenter-20160125-en.us-127GB.vhd | Microsoft Azure Marketplace |
How-To
Quick Test (Linux Only)
- From the marketplace import the RightLink 10.3.0 Linux Base ServerTemplate published by RightScale Engineering.
- Create a Server from the ServerTemplate
- Select an appropriate MCI and launch. Once the server goes operational, you will see an audit entry with the boot scripts and be able to SSH into the instance using your
managed SSH
key as the user 'rightscale' from which you can sudo (see Server Login Control for additional information onmanaged SSH
keys)
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 for Linux):
rs_agent:type=right_link_lite
rs_agent:mime_include_url=https://rightlink.rightscale.com/rll/10.3.0/rightlink.boot.sh
(for Install-at-boot on Linux)AWS, Softlayer, Openstack Juno, Google, and RCA-V (vSphere) have been tested; Other images on other clouds with a functioning cloud-init should work, but have not been explicitly tested by RightScale (see above).
The Enable Monitoring RightScript will install collectd on Ubuntu and RHEL/CentOS/Compatible OSes, and will use RightLink Monitoring on CoreOS. It could strand on other distros as there may be no support to install collectd via packages. Installation of collectd was verified with CentOS 6, CentOS 7, Ubuntu 12.04, and 14.04 but should work on other versions as well, and use of RightLink Monitoring has been tested with CoreOS stable.
Please see RightLink on CoreOS if adapting the Base ServerTemplate for CoreOS.
RightLink 10 is Not Fully Compatible with RightLink6
- 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