From 62a0de50df0f95ec6523b8d4a8fe65c1d843bffe Mon Sep 17 00:00:00 2001 From: Louis Pieterse Date: Mon, 25 Apr 2022 10:13:43 +0100 Subject: [PATCH] Tweak some PipelineWise documentation (#950) --- docs/user_guide/scheduling.rst | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/docs/user_guide/scheduling.rst b/docs/user_guide/scheduling.rst index 75208c7d8..ed4064530 100644 --- a/docs/user_guide/scheduling.rst +++ b/docs/user_guide/scheduling.rst @@ -43,12 +43,15 @@ PipelineWise is tested and can run with at least the following schedulers: * `Unix Cron `_ Unix Cron - This is the simplest option - for a single server installation. + for a single server installation. + +* `Cicada `_ Cicada Scheduler - A lightweight multi-server + CRON manager * `Cronicle `_ - Cronicle is a reasonably good and relatively simple tool to schedule PipelineWise jobs in both Single Server and Multi-Server cluster installations. - + * `Apache Airflow `_ - Airflow is a robust and mature tool to schedule and monitor workflows. @@ -67,11 +70,3 @@ PipelineWise commands on multiple nodes that operate on the same project, then every node has to read/write into the same directory, doesn't matter where the nodes are located. This is typically done by mounting ``${HOME}/.pipelinewise`` on every node to a shared directory on NFS/EFS. - -.. warning:: - - There are plans to store ``${HOME}/.pipelinewise`` runtime configuration files - optionally on different data stores, like S3, RDBMs or on document stores like - Couchbase or MongoDB. Once it is implemented, Multi-Server Cluster installation - will not require NFS/EFS. -