To gain a proper understanding of the Sharing features within the RightScale Dashboard and how you can best use them for collaborative development and testing purposes. You can use Account Groups (previously called Sharing Groups) to share the following RightScale components: ServerTemplates, RightScripts, MultiCloud Images, and Macros.
For AWS, you can also share Images and EBS Snapshots, but those are cloud resources and are shared in a different manner. See Sharing Cloud Resources.
This document focuses on sharing RightScale components via Account Groups.
Table of Contents
One of the best ways to facilitate collaborative work across multiple teams or departments is to use RightScale's sharing features. Account Groups provide a means of sharing commonly used Rightscale components such as ServerTemplates and RightScripts between different RightScale accounts. Any RightScale user (with 'publisher' role privileges) has the ability to create Account Groups and share RightScale components. You can either publicly or privately share your RightScale components.
|Detail||Public Sharing||Private Sharing|
|Who can share?||All Accounts||Select RightScale Editions |
(Accounts with enterprise structure)
|Who can view it in the MultiCloud Marketplace?||All Accounts||All Accounts |
|Who can import it from the MultiCloud Marketplace?||All Accounts|| |
Select RightScale Editions
Public sharing allows you to share your custom RightScale components with all other RightScale accounts. Everyone will have access to view and import your components from the RightScale Component MultiCloud Marketplace. Public sharing is supported in any RightScale account, regardless of the plan type. Community publishing helps facilitate development within the RightScale community by providing a way for RightScale users to share their custom ServerTemplates, RightScripts, etc. with each other. To enforce best practices, you can only publish committed revisions of components to the public.
Private sharing is performed discretely between RightScale accounts via Account Groups. Only Premium plans and above support private sharing. Whereas public sharing makes a component viewable and importable by all users, private sharing provides a way for you to control who can view and import your shared components. You can privately share both committed revisions and HEAD versions of a component.
Note: The ability to share a HEAD version of a component is only supported in Private Sharing using private account groups; HEAD versions cannot be published and shared with the public.
For example, your development team could share their latest ServerTemplates and Macros with the quality assurance team for testing purposes. Privately shared components will not be visible to all RightScale users. Remember, RightScale components are not user-specific; they are RightScale account-specific. Therefore, it's important to understand that sharing is performed between RightScale accounts and not individual users. Users will be able to view and use those RightScale components as long as they have the appropriate user role privileges ('designer') in that account. See User Role Privileges.
If you share a HEAD version of a RightScale component, you should understand its implications, namely that you can automatically inherit changes from the publisher. See Subscribe to a ServerTemplate.
The example below demonstrates private sharing between two different RightScale accounts.
In order to properly understand the concept of sharing RightScale components, it's important to understand the following terms.
By default, when you publish a ServerTemplate to the MultiCloud Marketplace, you are also publishing/sharing all of the template's private RightScripts, MultiCloud Images, and RepoPaths (if available). In order to prevent against piracy, if you share a ServerTemplate that contains paid RightScripts that have been published by RightScale or some other Partner, you must make sure that the RightScale account(s) that you are sharing the template with has access to use those paid scripts, otherwise they will not be able to use the ServerTemplate as-is.
You can publish RightScripts and MultiCloud Images individually.
You can publish locked and unlocked Macros. However, it is strongly recommended that you only publish locked Macros. Remember, any RightScale account that you share a Macro with will need to have access to any of its ServerTemplates, RightScripts, etc. in order to successfully run the Macro.
To protect the use of your ServerTemplate, you can attach an End User License Agreement (EULA) to it. In order to use a ServerTemplate with an attached EULA, a user must accept the defined terms and conditions.
Note: Currently, you can only attach EULAs to ServerTemplates. In the future, you will be able to attach EULAs to other RightScale components as well.
Unless you are working closely with another group that's using a different RightScale account, you should never publish and share a HEAD version of any component because it's not static. As a best practice, you should only publish committed revisions of a component. The ability to publish and share HEAD versions of a component is only supported for private sharing. You can only publicly share committed revisions.
Before you deprecate or delete a shared component from the MultiCloud Marketplace, it's important that you understand the difference between the two actions. See Deprecating or Deleting Shared Components.
To learn more about how to share RightScale components via Account Groups, see the How to Share RightScale Components tutorial.
© 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.