| Port details |
- percona-orchestrator Replication topology manager for MySQL
- 3.2.6.12_5 databases
 =2      3.2.6.12_3Version of this port present on the latest quarterly branch. - Maintainer: zi@FreeBSD.org
- Port Added: 2024-04-05 15:00:06
- Last Update: 2024-08-09 06:24:08
- Commit Hash: aa8c011
- People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane
- License: APACHE20
- WWW:
- https://github.com/percona/orchestrator
- Description:
- Orchestrator is a replication topology manager for MySQL.
Features include:
* The topology and status of the replication tree is automatically detected
and monitored.
* Either a GUI, CLI or API can be used to check the status and perform
operations.
* Supports automatic failover of the master, and the replication tree can
be fixed when servers in the tree fail - either manually or automatically.
* It is not dependent on any specific version or flavor of MySQL (MySQL,
Percona Server, MariaDB or even MaxScale binlog servers).
* Orchestrator supports many different types of topologies, from a single
master -> slave to complex multi-layered replication trees consisting of
hundreds of servers.
* Orchestrator can make topology changes and will do so based on the state
at that moment; it does not require a configuration to be defined with what
corresponds to the database topology.
* The GUI is not only there to report the status - one of the cooler things
you can do is change replication just by doing a drag and drop in the web
interface (of course you can do this and much more through the CLI and API
as well).
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- percona-orchestrator>0:databases/percona-orchestrator
- To install the port:
- cd /usr/ports/databases/percona-orchestrator/ && make install clean
- To add the package, run one of these commands:
- pkg install databases/percona-orchestrator
- pkg install percona-orchestrator
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: percona-orchestrator
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1712256381
SHA256 (percona-orchestrator-v3.2.6-12_GH0.tar.gz) = 6ea9d25494f66fd67b18c71e155bc810ee13ea499617ffe2ec5e3caf17197d93
SIZE (percona-orchestrator-v3.2.6-12_GH0.tar.gz) = 7913143
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- go121 : lang/go121
- Runtime dependencies:
-
- bash>0 : shells/bash
- gsed>0 : textproc/gsed
- jq>0 : textproc/jq
- mysqld : databases/mysql80-server
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- databases_percona-orchestrator
- USES:
- go mysql:server shebangfix
- pkg-message:
- For install:
- #### Setup backend MySQL server
Setup a MySQL server for backend, and invoke the following:
CREATE DATABASE IF NOT EXISTS orchestrator;
CREATE USER 'orchestrator'@'127.0.0.1' IDENTIFIED BY 'orch_backend_password';
GRANT ALL PRIVILEGES ON `orchestrator`.* TO 'orchestrator'@'127.0.0.1';
Orchestrator uses a configuration file, located in:
/usr/local/etc/orchestrator/orchestrator.conf.json
Edit orchestrator.conf to match the above as follows:
...
"MySQLOrchestratorHost": "127.0.0.1",
"MySQLOrchestratorPort": 3306,
"MySQLOrchestratorDatabase": "orchestrator",
"MySQLOrchestratorUser": "orchestrator",
"MySQLOrchestratorPassword": "orch_backend_password",
...
#### Grant access to orchestrator on all your MySQL servers
CREATE USER 'orchestrator'@'orch_host' IDENTIFIED BY 'orch_topology_password';
GRANT SUPER, PROCESS, REPLICATION SLAVE, RELOAD ON *.* TO 'orchestrator'@'orch_host';
GRANT SELECT ON mysql.slave_master_info TO 'orchestrator'@'orch_host';
GRANT SELECT ON ndbinfo.processes TO 'orchestrator'@'orch_host'; -- Only for NDB Cluster
Replace `orch_host` with hostname or orchestrator machine (or do your
wildcards thing). Choose your password wisely. Modify the configuration file to
match:
"MySQLTopologyUser": "orchestrator",
"MySQLTopologyPassword": "orch_topology_password",
By default, orchestrator listens on 127.0.0.1:3000 and is configured to be
read-only. Please update the configuration file if you would like to change
this.
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
3.2.6.12_5
09 Aug 2024 06:24:08
 |
Ashish SHUKLA (ashish) |
all: Bump after lang/go121 update |
3.2.6.12_4
03 Jul 2024 08:29:54
|
Ashish SHUKLA (ashish) |
all: Bump after lang/go121 update |
3.2.6.12_3
15 Jun 2024 09:52:17
|
Ashish SHUKLA (ashish) |
all: Bump after lang/go121 update
MFH: 2024Q2 |
3.2.6.12_2
13 May 2024 17:56:04
|
Ashish SHUKLA (ashish) |
all: Bump after lang/go121 update
MFH: 2024Q2 |
3.2.6.12_1
15 Apr 2024 08:20:04
|
Ashish SHUKLA (ashish) |
all: Bump after lang/go121 update
MFH: 2024Q2 |
3.2.6.12
05 Apr 2024 14:57:01
|
Ryan Steinmetz (zi) |
databases/percona-orchestrator: new port!
Orchestrator is a replication topology manager for MySQL.
Features include:
* The topology and status of the replication tree is automatically detected
and monitored.
* Either a GUI, CLI or API can be used to check the status and perform
operations.
* Supports automatic failover of the master, and the replication tree can
be fixed when servers in the tree fail - either manually or automatically.
* It is not dependent on any specific version or flavor of MySQL (MySQL,
Percona Server, MariaDB or even MaxScale binlog servers).
* Orchestrator supports many different types of topologies, from a single
master -> slave to complex multi-layered replication trees consisting of
hundreds of servers.
* Orchestrator can make topology changes and will do so based on the state
at that moment; it does not require a configuration to be defined with what
corresponds to the database topology.
* The GUI is not only there to report the status - one of the cooler things
you can do is change replication just by doing a drag and drop in the web
interface (of course you can do this and much more through the CLI and API
as well). |
As an Amazon Associate I earn from qualifying purchases.