With orchestration stacks, you can launch and manage multiple composite cloud applications. You start a new stack by specifying the template and environment files, and defining other operational settings, including user credentials, database access settings, and the Linux distribution.
Verify that the template and environment file for the stack are created and available. For information about creating template and environment files, see the OpenStack documentation at http://docs.openstack.org/developer/heat/template_guide/index.html.
- Log in to the VMware Integrated OpenStack dashboard.
- Select the project from the drop-down menu in the title bar.
The Stacks page lists the stacks available to the current user.
- Click Launch Stack.
- Select the template for the new stack.
Select the template source: URL, File, or Direct Input.
Template URL or File or Data
Dynamically changes depending on what you select for Template Source. Enter the URL, browse to the file location, or paste the template text.
Select the environment source: URL, File, or Direct Input.
Environment URL or File or Data
Dynamically changes depending on what you select for Environment Source. Enter the URL, browse to the file location, or paste the template text.
- Click Next.
- Configure the new stack.
Name to identify the stack.
Creation Timeout (minutes)
Number of minutes before the launch of the stack times out.
Rollback On Failure
Select this check box to roll back changes if the stack fails to launch.
Password for user "demo"
Password for the default user after the stack is created.
Name of the database user.
Linux distribution that is used in the stack.
DB Root Password
Root password for the database.
Key pair for logging into the stack.
Name of the database.
Password for the database.
Flavor for the instance.
- Click Launch to create the stack.
- (Optional) : Verify that the new stack appears on the Stacks page.
- (Optional) : Click the stack to view the stack details.
Visual topology of the stack.
Parameters and details of the stack.
Resources that the stack uses.
Events related to the stack.