1.1.1. How to create a stack

Stack creation is based on Heat Orchestration Template (HOT). How to create a Heat Orchestration Template (HOT)
Stack creation process includes two steps which are shown as follows.

1.1.1.1. Template Selection

Select a template
Input items on the selecting screen of template are as follows.
How to specify a template
Directly type template into a text form or select a template file (yaml format) from local.
About how to create a template, please refer to page How to create a Heat Orchestration Template (HOT).
How to specify a environment setting
Directly type the environment setting, or select an environment file (yaml format) from local.
Please check Environment File for details of environment file.

1.1.1.2. Stack Creation

Create a stack
Input items on the stack creation screen are as follows.
Stack Name
Input stack name.
Possible sting: ^[a-zA-Z][a-zA-Z0-9_.-]*$
Creation Timeout (minutes) Specify the timeout value for stack creation.
Rollback On Failure
If it is checked, delete created resources when stack creation fails.
Refer to About stack rollback for details.
API secret key paired with API key
Specify API secret key paired with API key.
Refer to Reason why entering API key, API secret key is necessary for the reason why such information is needed.
If parameters section is used in the template, a field for entering parameter value will be displayed as shown below.
Stack create (Specify parameter)

About stack rollback

It is a function to restore the state before stack creation by deleting already created resources when creation failed happens during creating process.
However, temporarily created resources will still be charged for the period between creation completion time-point and deletion completion time-point (rollback).
Also, even if you use the rollback function, depending on the condition, it is possible that not all created resources could be deleted.
In that case, please try Stack Abandon operation, and delete the resources individually.

Reason why entering API key, API secret key is necessary

At creation/deletion of a stack, deployment manager creates/deletes resources of various services described in the template using the user’s own authentication information (token). However the token will expire in 1 hour as described in the service manual.
Therefore, in the case where a stack creation/deletion process will be continued for a long time, such as a stack where multiple resources are described in its template, token may be revoked during creation/deletion.
In order to prevent such failure, there is a function that allows the deployment manager to obtain tokens on behalf of user.
By entering API key, API secret key on the creation screen of the stack, a new token will be obtained by the deployment manager side when old token expires. By using the new token, deployment manager is able to continue creating/deleting its internal resources.