Archive for the ‘bfluri’ Category

Sodeli, let’s spooooood!!!

Freitag, Mai 28th, 2010

Gestern war nochmal ein Chrampf, aber wir haben’s geschafft! Um ca. 21.52 öffneten zubi, andy, beat, tobi & ich je eine Bierdose und stiessen an – die Seite war “oben” und sie lief! Bange Minuten beim Aufschalten waren überstanden! Danach gabs noch Pouletflügeli mit Pommes und die Welt war in Ordnung! Das heisst, sie ist es immer noch!

Geniesst! Und erzählt es Euren Freunden, Euren Bekannten, Euren Müttern, Euren Cousinen, Euren Kommilitonen, Euren Versicherungsagentinnen, Euren Velomechanikern, Euren Lieblingskassiererinnen, Euren Arbeitskollegen, allen!

->Foto am 27-05-2010 um 10.27

Wir haben alle Freude… (hoff ich doch zumindest…): Andy, zubi, Tobi, Jonas, Beat, räbitsch

The NEW Server Room

Dienstag, März 23rd, 2010

new_server2Since we’re getting closer to the release of BETA, we were looking for a partner who hosts our platform. In Switzerland, we got offers from aspectra, METANET, NETRICS, nexellent, and stepping-stone.

The offers were very different. METANET, for instance, didn’t give us any specific information on the phone, they just directed us to their web page. As METANET is a low-cost server-hosting provider, that was perfectly ok. However, we’d like to have at least a personal contact to discuss our needs and budget. On that point, we were satisfied by the remaining four. All of them provided us with good and interesting information and told us that we should start with a virtual server that can be extended in no time.

Since we don’t want to spend nights with setting up software infrastructures and maintaining application containers, we had the need that our future partner should also offer software support on OS (Linux), Apache2, MySQL, and JBoss AS. All of the remaining four offered us software support but only aspectra and stepping-stone for the complete setup. The software support of NETRICS and nexellent is limited to OS and MySQL.

There is no question that aspectra is cutting-edge and well-known among the companies that obtain server-housing and server-hosting services. Well, that also means, they’re cutting-edge with the costs. We can’t afford any of the offerings from aspectra (not even the “cheapest” one ;)). Moreover, we liked, and still like, the freshness and familiarity of stepping-stone, that fit perfectly into our team. So, we decided on stepping-stone.

The Server Room

Freitag, Februar 5th, 2010

server-roomAs we do not earn money for the first couple of months, we have to be sparse with spending money for gadgets. That also means, we have only bought two old Dell PowerEdge 2650 servers with hardware RAID-5 and three SCSI harddisks each. The first step was to setup the two servers with Fedora Core 11 (FC11). We don’t want to explain why we took FC11; we just did it. First problem: hardware RAID-5 is extremely slow. Let me make this clear: RAID-5 is extremely slow. After fiddling around with a lot of raid controller configurations; we gave software RAID-5 a try (you can setup software RAID-5 while installing FC11). Result: even slower. After a long discussion, we decided to try the following scenario:
We use one server with four hard disks and software RAID-1 (also via FC11 installation). We connected two disks at a time to a RAID-1 composite. The first is occupied with the partitions/boot and /; the second /home and /opt. To setup the RAID-1 composites we used the “Configuring Software RAID1 on Fedora Core using Disk Druid during system install” tutorial of Adam Ben-Gur.

The second server is used as spare in case we have to make a disaster recovery. How we prepare ourselves for a disaster recovery, we’ll explain later.

The server now runs relatively fast. So, we can begin with installing the necessary tools for our project. Must haves: Wiki, task management, version control, continuous integration, issue tracking.

We decided to use:

Don’t worry, we didn’t forget about the backup setup for disaster recovery. We’ll write about them later; when we have a running system to test backup restore and disaster recovery scenarios.