Skip to content

# orchestrator 1.1.18: new features, support for orchestrator-agent

MySQL Open Source orchestrator Replication October 13, 2014

Outbrain‘s orchestrator 1.1.18 is released:

- Support for orchestrator-agent (see announcement): agent pages, support for agent actions, initiation of seeds (provisioning of new/corrupted servers), auditing of seeds.
- Clusters dashboard
- Support for long query auditing
- SSL
- Proxy authentication (e.g. apache2 serving as reverse-proxy with LDAP)
- User control
- Better slave moving rules.

Quick links:

- Get orchestrator 1.1.18
- Read the orchestrator manual
- Check out orchestrator-agent

orchestrator now allows for seeding/provisioning of servers via orchestrator-agent. It communicates with agents executing on the MySQL hosts and coordinate transfer of data between them. orchestrator now supports invocation and auditing of seeding operations, and protects you from breaking your seeds. The orchestrator-agent is a solution to Outbrain’s specific use case, and may not appeal to the greater crowd. Nonetheless it is extendible and is released as open source.

A nice overview of all topologies is provided in the clusters > dashboard page. The dashboard points out the clusters, amount of servers per cluster, and amount and type of problems per cluster. It also provides configurable aliasing to your clusters, so you may name your mysql01.myservice.mydomain.com:3306 as “customer db”.

orchestrator will list each instance’s long running queries in its own backend database, and will present the user with such data. It also provides with a “kill query” functionality (do note that polling for long running queries is done once per minute only).

SSL is supported in agents communication.

orchestrator now accepts proxy authentication (configurable). This lets you put, for example, apache2 as reverse proxy, which communicates with LDAP and authenticates access. The authenticated user is then relayed to orchestrator. With this method of authentication you are now able to pre-define “power users”. In this authentication mode orchestrator will limit user actions to read-only, unless the user is a power-user. Thus, viewing the topologies is open to everyone, but moving slaves around is limited to a smaller group of people. Read more.

You may now move up a slave if it’s master is in stopped-slave state, which allows extracting good, healthy slaves from underneath busy, slow relay-slaves.

orchestrator is released by Outbrain under the Apache 2.0 license, and is free to use.

- Twitter
- LinkedIn
- WhatsApp
- Email
- Facebook
- Print

### Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe
Notify of
wpDiscuz
Send to Email Address Your Name Your Email Address Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.