{"id":6945,"date":"2014-07-29T13:42:06","date_gmt":"2014-07-29T11:42:06","guid":{"rendered":"http:\/\/code.openark.org\/blog\/?p=6945"},"modified":"2014-07-29T13:42:06","modified_gmt":"2014-07-29T11:42:06","slug":"orchestrator-1-0-4-released","status":"publish","type":"post","link":"https:\/\/code.openark.org\/blog\/mysql\/orchestrator-1-0-4-released","title":{"rendered":"Orchestrator 1.0.4 released"},"content":{"rendered":"

Outbrain’s orchestrator<\/em> Version 1.0.4<\/strong> is released<\/a>.<\/p>\n

Quick links:\u00a0Orchestrator Manual<\/a><\/strong>, FAQ<\/a><\/strong>, Downloads<\/a><\/strong><\/p><\/blockquote>\n

What’s new?<\/p>\n

Co-masters<\/h4>\n

orchestrator now does a much better visualization of Master-Master replication:<\/p>\n

\"orchestrator-co-masters\"<\/a><\/p><\/blockquote>\n

<\/p>\n

\"orchestrator-co-masters-j\"<\/a><\/p><\/blockquote>\n

 <\/p>\n

The work on making the visualization more appealing also resulted in making a better distinction between the visual tree topology and the replication topology. This in turn also fixes the ruleset for moving slaves in a co-master topology, and lays the ground for future work on co-masters (i.e. Galera; unscheduled).<\/p>\n

resolve<\/h4>\n

Had a few reports on orchestrator<\/em> not being able to connect to some topology instances. It seems like the problem is with name resolving. To prove\/disprove this, the resolve<\/strong> command or resolve<\/strong> API call now allows checking for instance connectivity. Orchestrator will first test whether the CNAME at all resolves, then try to dial the TCP address (host + port) to see whether it can make a connection.<\/p>\n

A sample API call would be:<\/p>\n

\n
http:\/\/127.0.0.1:3000\/api\/resolve\/myhost.mydomain\/3306<\/pre>\n<\/blockquote>\n
A command line invocation would be:<\/p>\n
\n
orchestrator -c resolve -i\u00a0myhost.mydomain:3306<\/pre>\n<\/blockquote>\n
chef cookbook<\/h4>\n
Silvia Botros of SendGrid<\/em> has published a generic cookbook for deploying orchestrator<\/em> via chef: https:\/\/github.com\/sendgrid-ops\/chef-orchestrator<\/a><\/p>\n
Thanks, Silvia!<\/p>\n
Topology Annonymizer Cheatsheet<\/h4>\n
If you want to share your topology graph, but do not wish to expose your host names, open your cluster page and execute the following in your browser’s JavaScript console (jQuery is already included by orchestrator)<\/em>:<\/p>\n
\n
var _=function() {\r\n\u00a0 var counter = 0; \u00a0\r\n\u00a0 var port = 3306;\r\n\u00a0 jQuery(\"h3.popover-title\").each(function() {\r\n\u00a0\u00a0\u00a0 jQuery(this).html(\"instance-\"+(counter++)+\":\"+port)\r\n\u00a0 });\r\n}();\r\n\r\n<\/pre>\n<\/blockquote>\n
This results in a modified topology such as the one presented above (“instance-11”, “instance-12” and so on).<\/p>\n
Other enhancements since 1.0:<\/h4>\n