Run an All-In-One Development and Test Macro

Import the Macro from the MultiCloud Marketplace

If the Macro that you want to run does not exist in the local collection of your RightScale account, go to the MultiCloud Marketplace and download the appropriate Macro(s).  Go to Design -> MultiCloud Marketplace -> Macros.   The Macros will be privately shared with your RightScale account, so you will find the Solution Pack Macros under the "Shared" category of the MultiCloud Marketplace.

The following AIO macros are available:

• All-In-One Server Deployment
  • Dev_and_Test All-in-One (LAMP)
  • Dev_and_Test All-in-one (Lamp/Tomcat)
  • Dev_and_Test All-in-One (RubyonRails)
  • Dev_and_test All-in-One (WASCE + DB2) - WebSphere Application Server and DB2 Express
  • Dev_and_Test All-in-One (Win)
• Multi-tier Deployment
  • Dev_and_Test Multi-Tier (LAMP)
  • Dev_and_Test Multi-Tier (LAMP/Tomcat)
  • Dev_and_Test Multi-Tier (LB + WASCE + DB2) - WebSphere Application Server and DB2 Express
  • Dev_and_Test Multi-Tier (RubyonRails)

Find the Macro(s) that you want to use and click the Subscribe button to add a copy of the Macro to your RightScale account's 'Local' collection. (Designer -> Macros)

Run the Macro

Go to Design -> Macros.  Select the Macro that you want to execute and click the Run action button. 

Note: The LAMP AIO Macro was used in the example below.

Before the Macro actually runs, you'll have the option of selecting and using an existing SSH Key.  If you do not select an SSH Key, the Macro will simply create a new SSH Key.  Unless you have a strong preference to use an existing SSH Key, it's recommended that you let the Macro create a new SSH Key for you.

Next, you'll need to specify a Deployment Name Prefix.  We suggest using your initials.  The prefix (e.g. do) will be used to create the name of your Deployment (e.g. do_All-In-One (LAMP)_1284569536230). 

When you run the Macro a unique ID is added as a suffix to the namespace of each component that's created to ensure its uniqueness, which will also help you more easily find the related components.

If you look at the output, you'll notice that the Macro performs the following steps:

• Imports and clones the ServerTemplate(s) that are used by the Macro to configure the Server(s).  It's important that your Deployment uses cloned (editable) ServerTemplates so that you can later customize them
• Creates an EC2 Security Group and adds the necessary ingress rules (i.e. Sets the firewall permissions for the server)
• Creates a new EC2 SSH Key (if you didn't select an existing one before running the Macro)
• Creates a Deployment and defines basic settings
• Adds a Server to the Deployment using the cloned ServerTemplates
• Launches the Server

Go to the Deployment's show page.  Manage -> Deployments -> YourDeployment.  Notice that the server has already been launched.

Once the Server becomes operational, go to its info page by clicking on the Server's nickname link.

Under the Info tab, click its public DNS Name link to view the running Server in a browser.

(Click to enlarge screenshot)
 

Congratulations!  You just created a functional Development and Test environment in just a few steps.  You can now safely terminate the running Server and customize as necessary.