# Server cluster - Parallelization

In order to access this section in LIBSAFE, the menu option is as follows: _Advanced Options >> System Configuration (Cluster Processing Configuration)_.

**LIBSAFE** has an advanced functionality for the management and monitoring of servers when they work in parallel to perform the activities of the system, seeking to optimize time and performance. This functionality is called Processing Cluster and allows the system to add nodes (equivalent to servers) and services in each node in different states and amounts, so as to perform actions even in a parallel (or multiple) way. With this, LIBSAFE increases its performance power and with its integrated panel within the platform it is possible to monitor the status of each node and service in a simple, intuitive and practical way.

![Overall View of the node monitoring](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkmchgZSTF-wAJKocXm%2F-MkmeLhtN6rtDaZr5VU6%2Fimage.png?alt=media\&token=774e4c74-7d33-48bf-a740-86193491971c)

![Overall View with a node deployed, and visualizing associated services](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkmchgZSTF-wAJKocXm%2F-MkmedDAcxoeV0yWD4-3%2Fimage.png?alt=media\&token=b9ea6738-8c53-4999-9443-ccf32bea06d9)

Each node can store a number of services defined in the system's own configuration, even allowing for one or more services of the same type in each node. In addition, each service can have different activity states, independent of the node state (services will have states whenever the node is **On**). Nodes can only have two states (**On** or **Off**), but they can have an exceptional state which is the Deleted state. This state, which represents that the node was created and later deleted, is kept in LIBSAFE with the aim of presenting all the activity carried out by the user since its beginning until the current date. In the node’s filter options you can visualize **All at once**, **Only the Active** or **Inactive** or **Deleted**.

![](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkmchgZSTF-wAJKocXm%2F-MkmezLOPG0I72QRdoJT%2Fimage.png?alt=media\&token=077be968-817f-4bb8-955a-30ef78490f4e)

From the same monitoring panel, new nodes can be created using the "New processing node" option on the upper left of the node list header.

Each node has useful information for its identification, current status and relative or user-defined data for its categorization. It also has direct access to its edition, visualization of operation details and actions that may affect the services. These accesses or links can change independently and be available or not depending on the case at a given time; this is how a node cannot allow its edition if any of its services is under a change request or can change its color depending on the response or status indicators of each one. There is a color and status legend in the window (lower left part of the node panel) that indicates the node status and its color.

![Visualizing a node without a response from a device](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkmchgZSTF-wAJKocXm%2F-Mkmf5FjaZhn8Q_wWrt3%2Fimage.png?alt=media\&token=3721e0b4-21e1-4ee0-8fd7-348988347540)

From the monitoring panel, status change actions can be performed on each of the services that each node contains; this is how the system can modify its potential in the performance of a service in multitasking or multi-service format. The option to add new services to a node is only made from the node's edit link. From the general panel the services can be changed to the following states: READY, STOP, SLEEP or DELETE:

* READY refers to the fact that the service will be active and can execute work at any time
* STOP indicates that the service will be stopped
* SLEEP indicates that the service will be in an active state but will not execute any task

![Options for each Service](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkmchgZSTF-wAJKocXm%2F-MkmfEwP9rLtIlymIKGl%2Fimage.png?alt=media\&token=3e3641cb-5793-43e0-9b2f-61f591560882)

Since the node monitoring panel is the virtual representation of a physical infrastructure, there may be a time lapse between the invocation of the action and the actual performance in the hardware. Therefore, the panel manages a state of transit between any two given states, which limits or conditions the availability of other actions at a given time.

When the user wants to change the state of a service, this will be in a state of pending change, which will then be confirmed by the hardware so that the user interface can continue managing the panel of nodes and services.

![Change of state of a given Service](https://2476985709-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MkhEUvHaUAQ7Cu_eShA%2F-MkmchgZSTF-wAJKocXm%2F-MkmfNBn2gGYlvFgrmo-%2Fimage.png?alt=media\&token=1d441d73-0990-44bb-9afe-f274fb86048f)

Only in this case, in the action options available for this service, a cancellation of the service can be made, which will reverse the request made, as long as the hardware has not finished executing the action. As shown in the previous image, the node edit option has disappeared in a logical response to the action of changing the state of a service belonging to it.
