On Tue, Mar 1, 2016 at 7:30 PM, Chad Horohoe <[email protected]> wrote: > On Tue, Mar 1, 2016 at 6:02 PM, Guillaume Lederrey <[email protected]> > wrote: >> >> I am finishing the upgrade of elasticsearch to 1.7.5 for codfw (eqiad >> still to do). For this, I used a small script [1], heavily inspired >> (copied / stolen / ...) from bd808. The script is ugly, but it does >> the job. It runs the deployment over a list of hosts, pausing for >> manual steps / validations along the way. The script runs locally on >> my workstation, so it is subject to loss of connectivity, local >> crashes, hard to handover, ... >> >> Do we have a central place for those kind of scripts? I'd like to >> version it in a more obvious place than my personal Github repo. Do we >> have examples of similar scripts? A specific tool for this? Rundeck >> [2] comes to mind. Note that I'm not a huge fan of Rundeck as it >> brings far too much complexity for simple tasks, but the concept of >> having a central place of re usable operational components is >> appealing. >> >> [1] https://github.com/gehel/elasticsearch-utility-scripts >> [2] http://rundeck.org/ >> > > We already have es-tool[0] in puppet which is installed on all Elastic > nodes. > You can easily iterate over the list of nodes and issue a `sudo es-tool > restart-fast` > (which waits for recovery, btw)
Yep, my script actually uses es-tool. It is mainly some glue around it to iterate on a list of servers. I'm interested in that glue. How do we orchestrate deployment across multiple servers? The locally running script that I have does not feel like a solution... > > -Chad > > [0] > https://phabricator.wikimedia.org/diffusion/OPUP/browse/production/modules/elasticsearch/files/es-tool > > _______________________________________________ > discovery mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/discovery > _______________________________________________ discovery mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/discovery
