Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
beat.web
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
beat
beat.web
Commits
337ad2b6
Commit
337ad2b6
authored
6 years ago
by
Samuel GAIST
Committed by
André Anjos
6 years ago
Browse files
Options
Downloads
Patches
Plain Diff
[doc][admin][installation] Update development setup instruction
Using the new scheduler/broker/worker paradigm.
parent
13122197
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!275
ZMQ refactoring
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/admin/installation.rst
+16
-3
16 additions, 3 deletions
doc/admin/installation.rst
with
16 additions
and
3 deletions
doc/admin/installation.rst
+
16
−
3
View file @
337ad2b6
...
...
@@ -440,13 +440,26 @@ Here is how to do it.
$ ./bin/django runserver
2. Start the full scheduling setup::
$ ./bin/django full_scheduling
This will start all elements of the scheduling/working process. Docker can
be used for the worker node passing the ``--docker`` option.
Each element composing the scheduling can also be started separately:
1. Start a the broker node::
$ ./bin/django broker -v 2
2. Start a single scheduling node::
$ ./bin/scheduler -v
v
$ ./bin/
django
scheduler -v
2
3. Start a worker for your current node::
$ ./bin/worker -v
v
$ ./bin/
django
worker -v
2
By default, the applications are configured to figure out paths and
configuration options by themselves. You can override some defaults via the
...
...
@@ -457,7 +470,7 @@ command line. Just check the output of each of those commands running the
Mixing and matching
===================
You can mix and match any of the above techniques to run a
3
-node system
You can mix and match any of the above techniques to run a
4
-node system
(all-in-one or discrete) to build a test system to suite to your needs. For
example, it is possible to launch the scheduling activities using the web
server and the page reload trick while launching the worker process separately
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment