Move pelias@weywot3 to @aither

[dr0i]

Since hbz/lobid-resources#621 it becomes clear that the new weywot-cluster don't really have fast harddisks. Adding another node to the weywot-cluster would ease the situation until we got some SSDs. We could add weywot3 to our cluster but first have to move the pelias-server (which runs on elasticsearch 2.3) to another location - e.g. aither.

See #357 for initial setup.

[dr0i]

Setup index:
cd git/pelias/schema; npm install pelias-schema. This creates a mandatory config at ~/pelias.json. There, configure openstreetmap to use "datapath": "/files/open_data/closed/pelias/osm" and "openaddresses" to use "datapath": "/files/open_data/closed/pelias/openaddresses.
Then cd git/pelias/openstreetmap and start indexing. Redo for openaddresses.
An index pelias is then created on aither, see http://aither.hbz-nrw.de:9200/_plugin/head/.
Start the pelias server with sudo service pelias start.

[dr0i]

Compared the No geo coordinates when transforming:
old with weywot3: 2048 vs new with aither: 1246. So this has not worsened.
Edit:
Hm, that "1246" was from the staging indexing which I assumed should be the same as for production. On production, however, it turned out that 3269 had No geo coordinates.
Made a new issue at #395.

[dr0i]

Deployed to prodcution, closing.