Glossary of Terms
The MultiCloud Marketplace contains a wide range of components including ServerTemplates to create a MySQL EBS Master/Slave setup, PHP Application servers, or a grid application macro for instantly creating a complete setup for performing batch processing tasks. Feel free to browse through the MultiCloud Marketplace to see what components are available.
Be sure to visit the MultiCloud Marketplace often to check for new or updated components.
You can view the MultiCloud Marketplace two different ways but each supports slightly different functionality.
In order to use any components from the MultiCloud Marketplace you need to place a copy in your own local collection so that you can use it in your own account. Simply browse through the MultiCloud Marketplace to find all of the components that are relevant for your application. Once you find a component that is relevant for your application, you can either import a static copy or subscribe to a HEAD (non-static) version. A copy of that component will be added to your local collection. You can either use the preconfigured components as-is or clone them to create editable copies that you can customize accordingly. Remember, each component that is available in the MultiCloud Marketplace has been published by either RightScale, an ISV Partner, or by another RightScale account that has publishing privileges.
It is the responsibility of the publisher to test and support their published components. The MultiCloud Marketplace simply serves as a central location where publishers can distribute their components to users of the RightScale community. RightScale is not responsible for supporting components that are not officially published by RightScale.
When you find a RightScale component that you want to use in your own RightScale account, you can either import it or subscribe to it. In both cases, a copy of the component is placed in your account's local collection for that component type.
The key difference between importing and subscribing is that you import committed (static) revisions of an component, whereas you can only subscribe to HEAD (non-committed) components. Most components that are available in the MultiCloud Marketplace are published, committed revisions. You can either use them as-is, or customize them. However, if you need to customize them in any way, you must clone them first, which creates private editable copies. You will only have access to the published revision or HEAD version for cloning. You will not have access to earlier revisions of that component, however you can import earlier revisions as separate actions as needed (if they are still available in the MultiCloud Marketplace). Once you import a component from the MultiCloud Marketplace, it will remain in your local collection even if the publisher later deprecates it and it is no longer browsable or importable in the MultiCloud Marketplace.
You must be extremely careful and understand the consequences of using a subscribed component. For example, if you subscribe to a HEAD version of a ServerTemplate, you can use it as-is, but the publisher reserves the right to make changes to it at any time. The ability to subscribe to a HEAD version can be a very useful tool, especially for collaborative development. When you subscribe to a RightScale component it will be listed as an "imported" component. So, if you add a server to a deployment, you'll find the subscribed ServerTemplate under the "imported" list. (view screenshot)
In order to view components in the MultiCloud Marketplace, you will need the 'designer' user role privileges, but in order to import/subscribe to a component from the MultiCloud Marketplace, you will need the 'library' user role.
When you import a ServerTemplate, any of its underlying RightScripts, RepoPaths, and MultiCloud Images are also imported unless they already exist in their respective local collections.
Note: Only the committed RightScript revision that's referenced in the ServerTemplate becomes visible (Design > RightScripts). i.e. You cannot see the complete history of all revisions of that RightScript. For example, if you import 'ServerTemplate A' that uses 'RightScript A [rev 4]' you will not see 'RightScript A [rev 3]' of that RightScript unless you previously imported a ServerTemplate that referenced 'RightScript A [rev 3]'.
You can also import RightScripts, MultiCloud Images, and RepoPaths individually.
When you import a Macro, you're only importing the Macro component itself. None of its referenced ServerTemplates, RightScripts, etc. are imported when a Macro is imported. Instead, these components are only imported (if necessary) when the Macro runs. For example, when a Macro runs, RightScale checks to see if the referenced RightScale components exist in your Local Collection. If any components are missing, RightScale attempts to import those components from the MultiCloud Marketplace. However, your account must have access to those components in the MultiCloud Marketplace. Otherwise, they are not imported and the Macro will fail. Therefore, it's important that anyone who runs a Macro has access to those referenced components in their RightScale account. Most of the time you run a macro as-is. However, if you need to make any changes to a Macro's underlying code, you must clone it to create an editable copy.
The Local Collection shows all of the RightScale account's private, imported, and subscribed components. A local collection will exist for each RightScale component that's in the MultiCloud Marketplace (ServerTemplates, RightScripts, etc.). The Local Collection is RightScale Account-specific, not user-specific.
Inside your Local Collection you'll find two types of RightScale components:
© 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.