Edited wiki page through web user interface.
This commit is contained in:
parent
1636a9a6ea
commit
af8f298717
|
@ -19,10 +19,10 @@ PPSS is very flexible: the file server can be a different host than the PPSS ser
|
||||||
|
|
||||||
Installing PPSS on a larger number of hosts will become an appalling boring repetitive and time consuming task if this is performed manually. The following actions must be performed on a node:
|
Installing PPSS on a larger number of hosts will become an appalling boring repetitive and time consuming task if this is performed manually. The following actions must be performed on a node:
|
||||||
|
|
||||||
- create a ppss user or use an existing *unprivileged* system account (do not use root).
|
* create a ppss user or use an existing *unprivileged* system account (do not use root).
|
||||||
- copy ppss.sh to the node.
|
* copy ppss.sh to the node.
|
||||||
- copy privade ssh key to the node (in a secure way).
|
* copy privade ssh key to the node (in a secure way).
|
||||||
- create a crontab entry to start ppss automatically on the node.
|
* create a crontab entry to start ppss automatically on the node.
|
||||||
|
|
||||||
I have to come up with a simple solution to automate this process. Currently, I'm considering creating a separate tool that deploys PPSS. This tool should use a list of IP addresses and/or host names as input and install PPSS on those hosts using SSH and SCP. However, this functionality could also be implemented as a function within PPSS.
|
I have to come up with a simple solution to automate this process. Currently, I'm considering creating a separate tool that deploys PPSS. This tool should use a list of IP addresses and/or host names as input and install PPSS on those hosts using SSH and SCP. However, this functionality could also be implemented as a function within PPSS.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue