Home > Release Notes > RightScale Cloud Management Platform > 2008-11-12
2008-11-12
2008-11-12
Table of Contents
- User Interface
- ServerTemplates
-
RightScripts
- DB master restore v4 [rev 3]
- DB Backup v2 [rev 2]
- DB slave init v1 [rev 2]
- DB promote to master v2 [rev 2]
- DB MySQL server install v7 [rev 4]
- DB RightScale tools install v9 [rev 5]
- DB continuous backups v4 [rev 3]
- DB EBS master restore [rev 6]
- DB EBS backup: [rev 4]
- DB EBS slave init: [rev 4]
- DB EBS promote to master: [rev 4]
- DB EBS slave init from non-EBS master: [rev 4]
- DB Delete EBS volume on halt [rev 4]
This release note documents the new features, changes, and bug fixes to the RightScale Dashboard.
Release Date: November 12, 2008
User Interface
(*) Features that are only available for users of RightScale pay editions will be denoted with an asterisk (*). To learn more about upgrading to one of our pay editions, visit us at RightScale: Plans & Pricing or contact us.
New Features
- Support for MySQL with EBS *
There are now ServerTemplates where you can create a redundant MySQL database using EBS. To learn more see Overview of MySQL-EBS Setups and follow the Create a MySQL-EBS Database Setup tutorial. If you have an existing MySQL database setup that saves backups to S3 and would like to migrate to an EBS setup, follow the MySQL Database Migration: S3 to EBS tutorial.
- New Monitoring Features *
Previously the monitoring feature was only available at the server level and you were unable to save individual graphs. There is now a 'Monitoring' tab at the deployment and server level, so you can now monitor all of your servers within a particular deployment. You can also save snapshots of individual graphs and rearrange them using a simple drag-and-drop. See Monitoring Deployments and Servers for more details.
- Support for sharing between related accounts *
Paying customers now have the ability to share ServerTemplates, RightScripts, and Macros with related accounts. The sharing features is not available for Trial or Developer users. Previously, only RightScale Partners had the ability to create sharing groups and invite users to access their shared components. Now, all paying customers have the ability to share ServerTemplates, RightScripts, and Macros with related accounts that are not visible to the public. For example, the development team could share their latest ServerTemplates, RightScripts, and macros with the quality assurance team for testing purposes. There is now a 'Shared' tab for ServerTemplates, RightScripts, and Macros. Components that are shared with users will continue to be listed under the 'Partners' tab. See Share RightScale Components for more details.
- New Feedback Link
There is now a Feedback link in the upper right-hand corner of the Dashboard (next to the Support link) where you can provide feedback about your success/struggles using the Dashboard interface. We are always looking for ways to improve our users' experience. Please feel free to provide us with your comments to let us know what we're doing right and how we can improve your overall user experience.
- Support for CentOS 5.2
The latest RightImage V4.0 supports CentOS 5.2.
- Support for Windows OS on Amazon EC2
Amazon recently announced their support for Windows on EC2. You can now deploy any compatible Windows-based applications using the Microsoft Web Platform, including ASP.NET, ASP.NET AJAX, Silverlight™, and Internet Information Server (IIS). Launch and bundle Windows instances on EC2 using one of the Windows AMIs directly within the RightScale Dashboard. Currently, Amazon only supports Windows Server 2003 R2. Windows Server 2008 is currently unsupported and you are not allowed to upgrade on your own. Check out our blog post for more details. NOTE: In order to enable an auto connection to a Windows instance, you must use IE 7.0 with ActiveX control installed and enabled or use an external RDP client. You cannot use the SSH Console button in Firefox. See Launch a Windows Server on EC2.
- Support for GoGrid
The Dashboard now supports GoGrid. You can now launch and terminate GoGrid servers directly within the Dashboard using one of GoGrid's images. Create GoGrid ServerTemplates and add servers to existing deployments. You can now have a deployment running multiple servers on different cloud infrastructures. Currently, there is no support for running RightScripts, alerts, or monitoring on GoGrid servers. The GoGrid options are only visible to select customers. If you are interested in unlocking the GoGrid features, contact sales@rightscale.com. See GoGrid.
Changes and Bug Fixes
- Updated Left-hand Navigation Menu (accordion-style)
The main left-hand navigation menu was revised to improve usability. The most obvious change is the addition of the Clouds section where we will provide access to supported cloud infrastructures such as Amazon EC2, FlexiScale, GoGrid, etc. Check out the new Dashboard Quick Reference Guide.
- Improved the naming convention of page titles
Previously, it was difficult to use the back button (history) of a browser to determine prior pages for quickly navigating between sections because each page had a similar title that made it difficult to distinguish one page from another. Page titles now follow a different naming conventions to improve navigation through browser histories. (ex: RightScale Deployment: Production)
- RightScale API Enhancements
The RightScale API has been expanded to support the following functions.
- Alert Specifications
- EC2 EBS Volumes
- EC2 Elastic IPs
- EC2 Security Groups
- EC2 SSH Keys
- ServerTemplates
- RightScripts
- Macros
- Credentials
- Enable/Disable Operational and Decommission RightScripts
Previously, you were only able to enable/disable boot scripts, where changes would only affect the next launched instance. You now have the ability to also disable/enable operational and decomission scripts. You can only enable/disable operational scripts if a server is not running. Once a server is running, the enable/disable options will be hidden and only enabled scripts will be visible. For decommission scripts, you can enable/disable them at any time. If you enable/disable a decommission script while a server is running, the change will take effect the next time the server is terminated.
- Cannot save template inputs on IE7/Vista
You can now save a ServerTemplate's inputs using IE7/Vista.
- EBS volumes fail to attach at boot when relaunching a server from an alert
A server can now successfully relaunch from an alert and attach an EBS volume at boot time.
- SSH does not launch when using Google Chrome
You can now launch an SSH session from the Google Chrome browser.
ServerTemplates
The MySQL ServerTemplates have been updated to support failover and recovery using EBS snapshots. This release features a new "MySQL EBS" ServerTemplate that's designed for creating a redundant failover MySQL database using EBS. See the Create a MySQL-EBS Database Setup tutorial.
MySQL EBS v13 [rev 7]
Boot Script
Added SYS REBOOT [rev 1]
Updated SYS Timezone set v1 [rev 2]
Updated SYS Syslog Remote Logging Client v6 [rev 5]
Updated RB rubygems 1.0.1 + quickinstall v3 [rev 2]
Updated SYS lvm on /mnt v8 [rev 4]
Updated DB Rightscale tools install v10 [rev 2]
Added DB MySQL server install v7 [rev 4]
Updated DB MySQL gem install v5 [rev 1]
Updated MISC ssh priv key install v2 [rev 2]
Updated DB privileges set v1 [rev 2]
Updated SYS Monitoring install v7 [rev 2]
Updated SYS Monitoring MySQL add v7 [rev 2]
Added DB EBS continuous backups: [rev 4]
Added DB EBS slave init at boot: [rev 3]
Operational Script
Added DB EBS master restore: [rev 6]
Added DB EBS backup: [rev 4]
Added DB EBS slave init: [rev 4]
Added DB EBS promote to master: [rev 4]NOTE: The script was changed to invoke the dbtool program, which now lives in a different directory.Added DB EBS slave init from non-EBS master: [rev 4]
Decommission Scripts
Added DB Delete EBS volume on halt [rev 4]
Added SYS REBOOT END Decommission [rev 1]
MySQL Additional v13 [rev 2]
Boot Script
Added SYS REBOOT [rev 1]
Updated SYS Timezone set v1 [rev 2]
Updated SYS Syslog Remote Logging Client v6 [rev 5]
Updated RB rubygems 1.0.1 + quickinstall v3 [rev 2]
Updated SYS lvm on /mnt v8 [rev 5]
Updated DB Rightscale tools install v9 [rev 5]
Updated DB MySQL server install v7 [rev 4]
Updated DB MySQL gem install v4 [rev 2]
Updated MISC ssh priv key install v2 [rev 2]
Updated DB privileges set v1 [rev 2]
Updated SYS Monitoring install v7 [rev 4]
Updated SYS Monitoring MySQL add v7 [rev 4]
Updated DB slave init at boot v1 [rev 3]
Updated DB continuous backups v4 [rev 3]
Operational Script
Updated DB master restore v4 [rev 3]
Updated DB backup v2 [rev 2]
Updated DB slave init v1 [rev 2]
Updated DB promote to master v2 [rev 2]NOTE: The script was changed to invoke the dbtool program, which now lives in a different directory.
Decommission Scripts
Added SYS REBOOT END Decommission [rev 1]
MySQL Bootstrap v13 [rev 2]
Boot Script
Added SYS REBOOT [rev 1]
Updated SYS Timezone set v1 [rev 2]
Updated SYS Syslog Remote Logging Client v6 [rev 5]
Updated RB rubygems 1.0.1 + quickinstall v3 [rev 2]
Updated SYS lvm on /mnt v8 [rev 5]
Updated DB Rightscale tools install v9 [rev 5]
Updated DNS master DB register v1 [rev 2]
Updated DB MySQL server install v7 [rev 4]
Updated DB MySQL gem install v4 [rev 2]
Updated MISC ssh priv key install v2 [rev 2]
Updated DB privileges set v1 [rev 2]
Updated SYS Monitoring install v7 [rev 4]
Updated SYS Monitoring MySQL add v7 [rev 4]
Updated DB master restore v4 [rev 3]
Updated DB continuous backups v4 [rev 3]
Operational Script
Updated DB master restore v4 [rev 3]
Updated DB backup v2 [rev 2]
Updated DB slave init v1 [rev 2]
Updated DB promote to master v2 [rev 2]NOTE: The script was changed to invoke the dbtool program, which now lives in a different directory.
Decommission Scripts
Added SYS REBOOT END Decommission [rev 1]
RightScripts
DB master restore v4 [rev 3]
- Changed script to invoke the dbtool program, which now lives in a different directory.
- Added notice to description: "not compatible with DB tools < 0.18.0"
DB Backup v2 [rev 2]
DB slave init v1 [rev 2]
DB promote to master v2 [rev 2]
DB MySQL server install v7 [rev 4]
- Added support for binlogging into a path outside the datdir. (New Input: DB_BINLOG_PREFIX)
- It now creates the directory of DB_BINLOG_PREFIX and configures it with the initial my.cnf file.
- Sets this input to: /mnt/mysql-binlogs/mysql-bin (by default).
DB RightScale tools install v9 [rev 5]
- Added support for EBS. Required large code re-organization to support both S3 and EBS.
DB continuous backups v4 [rev 3]
- Added better control for master/slave backup frequency through: DB_BACKUP_MASTER_FREQ and DB_BACKUP_SLAVE_FREQ.
DB EBS master restore [rev 6]
- You can override the prefix to restore DB from through DB_RESTORE_PREFIX_OVERRIDE.
DB EBS backup: [rev 4]
- Backs up the binary DB contents to an EBS snapshot. The name of the snapshot will be the same as the volume from which the snapshot is taken (which should coincide with the EBS_DB_NAME).
DB EBS slave init: [rev 4]
- Converts a running DB instance to be a slave of an existing Master-DB. It will restore the DB contents by creating an EBS volume out of the most recent snapshot with the given DB prefix. It will also set the slave DNS entry to point to the instance's IP.
DB EBS promote to master: [rev 4]
- Execute this script on a Slave-DB instance to convert it to the new Master-DB. The slave instance must already be connected to the current master, otherwise it will assume that the current master is dead and will change this (Slave) DB to accept writes and log binary changes (i.e., become a Master-DB). The master DNS entry will be changed to point to this instance. This script will use the EBS version of the scripts.
DB EBS slave init from non-EBS master: [rev 4]
- Converts a running EBS DB instance to be a slave of an existing (and currently running) Master-DB that uses the non-EBS MySQL templates. The purpose of this script is to facilitate the live migration from a non-EBS based MySQL templates, to EBS based ones. By booting an EBS template (with INIT_AT_BOOT=false) and then executing this initialization script, one creates a live replicating slave server (that uses an EBS volume) from a non-EBS master without any downtime. Once the EBS slave is completely in sync with the non-EBS master, we can fully migrate the DB system by promoting it, launching a new EBS slave, initializing it (once the intial snapshot it completed), and then terminate the original non-EBS Master-DB.
DB Delete EBS volume on halt [rev 4]
- Deletes the existing and attached volume, on which the MySQL DB is mounted. The deletion of the volume will ONLY happen when the runlevel is 0 (i.e., halt)...not when the machine is rebooted (runlevel 6).
- © Copyright 2015 RightScale Technical Support