After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
Create a cluster from an OVA installation
Converting a virtual machine to a server or cluster node is a one-way operation. It cannot be reverted.
The most basic version of a cluster is a single Shared Services server connected to multiple instances of .
This configuration is not recommended for production use. This mode is primarily intended for Proof of Value or demonstrations. A single Shared Services server becomes a single point of failure. Any problems on the Shared Services server impact your entire cluster.
Use the following checklist for a Single Shared Services server.
Number | Task | Description |
---|---|---|
1 | Create the Shared Services server. |
|
2 | Install cluster nodes. |
|
Build a cluster with external service services
Build a more robust cluster, putting each of the services on its own server or group of servers to serve multiple cluster nodes of .
Use the following checklist for a virtual machine images cluster with external services:
Number | Task | Description |
---|---|---|
1 | Create the HAProxy node. |
|
2 | Create the PostgreSQL node. |
|
3 | Create the file shares node |
|
4 | Create the Splunk Enterprise node |
|
5 | Install cluster nodes. |
|
About clusters | Create a cluster from an RPM or TAR file installation |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1
Feedback submitted, thanks!