Toolserver:Admin:Shopping list

Some things we might want to buy, roughly in order of most important first.


 * MySQL support|: EUR430/server/year basic (2 incidents), or EUR1'500/server/year silver
 * two more stackable switches so we can have two redundant switches per rack
 * a spare or two for each type of disk we might need

(+) = budgeted


 * a new database that could store the complete text in uncompressed form for easy access by users (~5-10TB?)
 * could use zedler's old SATA array for this
 * Let's not do that, the old array sucks. Could put it on the SATA SAN storage.
 * a new database that could store the DBpedia data. Find out how to get that into MySQL, and how much it would be. This should actually be paired with the respective wiki databases, on the same servers.
 * a new database that could store all the access data collected from the squids. This should actually be paired with the respective wiki databases, on the same servers.

Wish list

 * Another array identical to the HP one, to mirror the data over.
 * A redundant storage setup will become more important once most of our storage depends on the array.
 * Increases read performance (the main bottleneck for databases).
 * No increase in storage (arrays are mirrored); but with 300GB SAS disks, storage probably isn't an issue
 * Requires that all future storage be added to both arrays to maintain redundancy.
 * More storage for the array.
 * The plan is to grow in future by adding storage to the array, instead of buying servers with local disks.
 * This is basically a permanent wishlist item; we can scale the storage forever.
 * New database servers (start with 2) without local storage.
 * These will be connected to the array.
 * Needs more storage on the array first (only has 12 SAS disks at the moment; not fast enough)
 * Existing databases will be re-purposed as login servers with local user-accessible storage