Actions are heavy-weight functions that run exclusively on the respective element. They have a high impact on their target and may take several minutes to finish.
State actions are used to manipulate the state of their target. They can be executed by selecting the respective entry in the target element’s right-click menu, or by executing topology actions. Topology actions execute the respective action on all suitable elements simultaneously.
Interface elements do not accept actions: Their state is changed automatically with their associated parent element.
State actions are only available when the respective element is in the respective starting state.
The prepare action leads an element from the created state to the prepared state.
First, a suitable host is selected for the element by the load balancer. Then, all required information about the element is sent to the target host, where the element is then prepared.
The start action leads an element from the prepared or created state to the started state.
If the element supports the prepared state and is in created state, the functionality of the prepare action will be executed automatically before starting.
The stop action leads an element from the started state to the prepared state. The element will automatically be stopped at its host.
The destroy action leads an element from the prepared or started state to the created state.
This means that the element is removed from the host, and all data associated with it is deleted.
There is other functionality which is implemented as actions. For example, changing a template or using executable archives. However, this has no impact of the user of the webfrontend. If you are interested in more information, consult the advanced user’s manual.