Posts Tagged osm
Where is cassini?
After the hardware-installation were finished yesterday River began to set up the servers that will run solaris, while I began to set up cassini that will run debian.
After I was trough the tftp-network-installation-hell again (took me only 2h and a dozen reboots to let the installation starting…), we discovered that the host doesn’t have a hardware-raid. A fast investigation result in that the osm-squid ortelius (which is nearly identical to cassini) and cassini were swap at the hardware installation. Because cassini should run a little copy of the osm-database itself, using it without hardware-raid is no option.
We are unsure what is the best way to handle the situation and how long it will take until cassini can used at the moment.
New servers are there
Yesterday Mark and Multichil were at our colo again and finished the hardware-installation of our new servers.
The toolserver-cluster got two new boxes: daphe, that is going to replace zedler as databasehost of the s2-cluster, and hyacinth that is going to work as host for our /home-directory.
Also they installed new servers for the openstreetmap/wikimedia-cooperation: A openstreetmap-toolserver on that people can play with osm-data (like our toolserver for wikimedia) named cassini, and a squid-proxy named ortelius and a database-host named ptolemy – both to handle the load the wikimedia-projects will create when they will use openstreetmap-maps.
At last two terminal-servers were installed to make it easier for the roots to handle broken servers.
Thanks to Mark and Multichil!
Faster, Better, Stronger
Yesterday, Wikimedia Deutschland has ordered five new Servers, three of which will be added to the toolserver cluster. They will be delivered (hopefully) in two to three weeks, and will go online perhaps a week or two after that. Here’s what the servers will be used for:
The first server will replace Zedler as our database server for the s2 cluster. Zedler is our oldest database server, and has lately been overloaded nearly constantly. We may keep Zedler around with a backup copy of s2, but it will mostlky be idle. We’ll see what use we can put it to later on.
The second server will take Hemlock’s duty of serving the home directories, and it will become the host system of the stable server. This means the stable server becomes virtualized (probably as a Solaris zone). Willow (the current server for stable projects) will then be free, we will probably make it into a second login server where users can run bots. This should take some load off Nightshade.
The thirs server is the “OpenStreetMap Toolserver”: it will be for the OpenStreeMap project what the Toolserver cluster has so far been for Wikimedia projects: a place to play with data and host bots and web applications. The Toolserver rules have been changed to accomodate this.
All in all, we will then have 12 servers in the Toolserver cluster.
The two remaining servers that have been ordered yesterday will also be used for the OpenStreetMap project, but not in the context of the Toolserver. They will be used to integrate interactive maps from OpenStreetMap directly into wikipedia Articles. More information about the OSM integration project is avialable on meta.