Understanding workspace and syslogreceiver directories
On Linux HA (Helm) and Swimlane Platform Installer (SPI - Standalone and HA), two directories '/app/workspace' and '/app/log/syslogreceiver', are mounted inside the tasks container by default.
The directory, '/app/workspace' is primarily used from inside the Swimlane Python tasks or forked plugin tasks to temporarily store/retrieve (read/write) files from within the tasks container.
The directory, '/app/log/syslogreceiver', is the storage location when working with Syslog receiver.
The volume type for the aforementioned directories is emptyDir. When the tasks pod(s) are removed/deleted (container restarts are ok), the data is deleted forever.
Using persistent data
In Linux HA Helm, you can change the volume type to persistent data by enabling sharedfs. When sharedfs is enabled, the data in the aforementioned directories are not only accessible from all the tasks pods but more importantly, the data is the same. This is because all task pod(s) will point to the same underlying persistent volume. The main benefit here is that when the tasks pod(s) are removed/deleted, the data will still be available once the pods start up again. In this case, data is not deleted.
To enable this feature:
NOTE: Linux HA Helm will be eventually deprecated and sharedfs (enabling persistent data) is NOT available in Swimlane Platform Installer (SPI). If youβre currently using this feature in Helm, then consult your Professional Service Engineer to explore other options.
In Linux Standalone Toolkit (Docker), the two directories, '/app/workspace' and '/app/log/syslogreceiver', are not mounted by default. However, you can mount and allow data to persist by following the steps below:
Newer version :