Difference between revisions of "Action"

Revision as of 23:23, 18 July 2018

Home > An Overview > Concepts > Actions

1 Overview

An action is a executable binary or script that can be run locally on a node that has a Veloopti agent installed on it. An action can be initiated manually through the Veloopti GUI directly from a node; or manually and automatically through an event that is associated with the node. Actions come with three levels of permissions: Operator; Power User; and Administrator.

2 Permissions

There are three levels of permissions with running an action. Each permission is associated with a different role that is increment in capability.

Operator

Operator level actions require the lowest level of permission to be run. Any user in an application that is a member of the Operator role can run an operator level action.

Power User

Power User level actions require more permissions than Operator level actions. Roles that can run Power User level actions can also run Operator level actions. Any user in an application that is a member of the "Power User" role can run Power User and Operator level actions.

Administrator

Administrator level actions require the highest level of permissions. Roles that can run Administrator level actions can also run Power User and Operator actions. Any user in an application that is a member of the "Administrators" role can run Administrator, Power User and Operator level actions.

3 Where actions can be run

Actions can be run in two different locations: on servers; and through an event.

3.1 Actions on servers

Actions can be run directly on a server that has a Veloopti agent installed. To do this, click on the server name in either the main node page, or the node page of an application. From the server there is a side menu item named Actions where actions can be run.

3.2 Actions on events

Actions can also be run from an Event. <more here>