Table of Contents
The RightScale Dashboard is designed to give you a multi-cloud platform for managing all of your cloud-specific resources and RightScale-specific components. It's important to understand the distinction between the two types because it affects their functionality and how they are treated within the RightScale platform.
The key difference is that cloud resources are specific to particular cloud infrastructures whereas RightScale components are cloud-agnostic. RightScale components don't care which cloud provider you are using or if you are using your own private cloud. For example, AMIs and EBS Snapshots are cloud resources that are specific to Amazon EC2. Cloud resources can only be used within the context of their respective cloud infrastructures. Although you can use cloud resources independently of RightScale, you can also use the RightScale Dashboard or API to act on these cloud resources.
RightScale components can only be used inside the RightScale Dashboard or API. However, since they are designed to be cloud-agnostic, you can use them across multiple clouds. For example, you can use the same ServerTemplate to launch servers on Amazon EC2 and Rackspace.
RightScale provides a cloud management platform that sits on top of the various cloud infrastructures. You can use both the RightScale Dashboard or API to perform actions on both RightScale components and cloud resources. In many cases you will use cloud resources interchangeably within RightScale components. For example, multiple servers in a deployment can use the same SSH key and security group.
Both RightScale components and cloud resources can be shared with other users, however there is a slight difference in how they are shared. Since RightScale components exist within the RightScale platform, we've created the notion of Account Groups where you can add RightScale components such as ServerTemplates, RightScripts, MultiCloud Images, and macros to a particular Account Group and then invite users so that they can use those components within their own account. It's a useful way of encouraging collaborative efforts across multiple groups within your organization for development and testing purposes. It also helps ensure consistency by making sure that the same ServerTemplates are used across multiple RightScale accounts.
See Sharing RightScale Components for details.
Since cloud resources are specific to their respective cloud and can exist independently from RightScale, you cannot share them using Account Groups. Instead, you must use the sharing feature that is supported by each cloud.
For example, to share cloud resources inside AWS, you must specify a specific AWS Account Number with whom you would like to share the resource. However, it's mportant to remember that in RightScale, multiple users might have access to the same RightScale account. (Each RightScale account is tied to a specific AWS Account Number.) Therefore if you share an AMI with AWS Account # 1234-1234-1234, multiple users might have access to that AMI.
See Sharing Cloud Resources for details.
A RightScale component is a concept that is specific to the RightScale Management Platform. RightScale components only have meaning and purpose within the RightScale system. Each component is essentially a meta-data description or map of a particular configuration. RightScale components can only be created/modified/deleted within the RightScale Dashboard GUI or API. Each component is designed to be cloud-agnostic. For example, you can configure a ServerTemplate to launch a PHP server in a public cloud (e.g. any Amazon EC2 region, Rackspace, SoftLayer, etc.) or private cloud (e.g. CloudStack or OpenStack).
The following RightScale components can be cloned inside the Dashboard in order to create an editable copy within your account. Once you import ServerTemplates and Macros from the MultiCloud Marketplace, you must clone them in order to create a private version that you can modify.
Note: Although you cannot clone alerts, you can import them to other ServerTemplates or Servers. When you import an alert, it becomes an editable version, just like a cloned RightScale component.
You can also share certain RightScale components with other users by using Account Groups. See Sharing RightScale Components for details. The following RightScale components can be shared.
Note: Although you cannot share deployments directly using Account Groups, you can create a macro of a deployment and then share the macro. A user can then run the shared macro to recreate the deployment and all of its components.
If your RIghtScale Account's plan supports Account Groups (see Plans & Pricing), you can create private Account Groups where you can privately share components with other specific RightScale accounts via Account Group Invitations. In addition to using private Account Groups, RightScale partners also have the ability to share components with RightScale accounts with a paid subscription.
If you are interested in learning more about our partnership program, please send us an email at email@example.com. You can also visit our Partners page on our corporate website, or see our current partner projects on the Support Portal Partners page.
You also have a level of version control and history for certain RightScale components where you can commit revisions and maintain version history of all changes to ensure configuration consistency at all times. The following RightScale components support this type of version control.
Note: You can also use the clone and lock features to preserve a component's configuration. For deployments, you can either create a macro of it to preserve its configuration at a particular point in time or clone and archive it for future use.
Macros can only be locked. You cannot create committed revisions of macros like other RightScale components.
A cloud resource is a real entity that is specific to a particular cloud infrastructure. It can only be used within a particular cloud infrastructure/service. For example, you cannot use an Amazon Machine Image (AMI) to launch an instance on Rackspace or Windows Azure. Cloud resources exist independently of RightScale. However, as long as you've provided RightScale with valid cloud credentials, you can use the RightScale Dashboard and API to perform actions on these resources.
Important! Cloud resources can be created/modified/deleted outside of RightScale via cloud-specific tools (e.g. AWS Console or a cloud infrastructure's API). Therefore, it's important that you establish structured processes with all members of your team to ensure that the same tool is used to manage your cloud resources in order to prevent against accidental or "mysterious" modifications. RightScale makes a best effort to reflect the current state of all your cloud resources inside the Dashboard.
If the ability to share cloud resources is supported by a cloud infrastructure, you can also use the RightScale Dashboard to share such resources. Currently, you can only share images (AMIs) and EBS Snapshots on Amazon EC2. See Sharing Cloud Resources for details.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.