Difference between revisions of "OS4X Portal - shared storage"
Jump to navigation
Jump to search
(Created page with "Storage for portal jobs are typically provided by the DMZ, making communication possible from the internal zone to the DMZ. The shared storage saves the following information:...") |
|||
| Line 7: | Line 7: | ||
The storage can be located anywhere in the DMZ, offering a wide range of protocols usable to be implemented, such as: | The storage can be located anywhere in the DMZ, offering a wide range of protocols usable to be implemented, such as: | ||
| − | *NFS (most common) | + | *NFS (most common, see example below) |
*CIFS | *CIFS | ||
*SSHFS | *SSHFS | ||
*others | *others | ||
| + | |||
| + | = NFS example = | ||
| + | On OS4X portal server side (DMZ), export a directory. Configuration file: | ||
| + | /etc/exports | ||
| + | Content (example): | ||
| + | /nfs 192.168.2.1(rw,sync,no_root_squash,no_subtree_check) | ||
| + | Activate export on DMZ side: | ||
| + | exportfs -a | ||
| + | |||
| + | = Configure shared storage (DMZ) = | ||
| + | |||
| + | |||
| + | = Configure shared storage (internal) = | ||
Revision as of 19:35, 7 April 2019
Storage for portal jobs are typically provided by the DMZ, making communication possible from the internal zone to the DMZ. The shared storage saves the following information:
- Outgoing portal jobs (from internal to DMZ)
- outgoing job data
- Incoming portal jobs
- incoming job data
- incoming job XML information
The storage can be located anywhere in the DMZ, offering a wide range of protocols usable to be implemented, such as:
- NFS (most common, see example below)
- CIFS
- SSHFS
- others
NFS example
On OS4X portal server side (DMZ), export a directory. Configuration file:
/etc/exports
Content (example):
/nfs 192.168.2.1(rw,sync,no_root_squash,no_subtree_check)
Activate export on DMZ side:
exportfs -a