Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Orchestrator systemd depency #1112

Merged
merged 4 commits into from
Apr 8, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions docs/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,12 +57,6 @@ Edit `orchestrator.conf.json` to match the above as follows:
"MySQLOrchestratorPassword": "orch_backend_password",
...

On systemd, and assuming your `orchestrator` config uses a MySQL backend (as opposed to SQLite), ensure that Orchestrator starts after your backend is loaded. Edit `/etc/systemd/system/orchestrator.service` and add `mysqld.service` in the [Unit] section:

[Unit]
After=syslog.target network.target mysqld.service


#### Grant access to orchestrator on all your MySQL servers
For `orchestrator` to detect your replication topologies, it must also have an account on each and every topology. At this stage this has to be the
same account (same user, same password) for all topologies. On each of your masters, issue the following:
Expand Down
2 changes: 1 addition & 1 deletion etc/systemd/orchestrator.service
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[Unit]
Description=orchestrator: MySQL replication management and visualization
Documentation=https://github.com/github/orchestrator
After=syslog.target network.target
After=syslog.target network.target mysqld.service mysql.service

[Service]
Type=simple
Expand Down