What is cloud computing? The basic idea is to have an abstracted model to separate physical IT infrastructure from logical IT infrastructure. Think about the OSI-Layer model and map it to the various infrastructure sets. (e.g. A customer is interested in the availability of a service. He doesnt care about the availability of the exact physical system.) This is called “Infrastructure as a service” short: IaaS

There are other aspects in cloud computing, which provide PaaS (Platform as a Service, e.g. Hosting) or SaaS (Software as a Service, e.g. Salesforce). Since EC2 allows logical
Since EC2 envirements allow a massive scaling of logical infrastructure, often the term “elastic” is used to describe parts of this technology.

EC2 compatible solutions (e.g. Eucalyptus and UEC) provide IaaS Services. The logical it is split into several components:

  • A Cloud Controller: The frontend coordinating everything. It’s accessed by an API, on the client side there are the ec2 tools on the shell or plugins like elasticfox for firefox.
  • A Storage Controller: This unit provides all the storage for the cloud. The storage comes in form of S3 which is also accessible over the web by API tools. It stores files as “Objects” in a “Bucket” objects can be made into “Bundles” by adding a prefix in front of their name. Another form of storage provided is EBS (Elastic Block Storage), which are partition images on the Storage controller, accessible by virtual instances (see below).
  • A Cluster Controller (Eucalyptus term, Amazon refers to clusters as “regions”): This unit controls the physical hardware and network configuration in the cluster.
  • Cloud Nodes: The physical servers running the cloud infrastructure.

The logical infrastructure built in the cloud consists of virtual servers, the so called instances. Instances are stored in form of templates. Every instance launched is started from the template, and looses all changes on termination. So specific configurations and data have to be stored in S3 or EBS. This seems a weird paradigm change at first, but makes perfectly sence, once you look at the migration paths available: Any kind of instance can be upgraded by upgrading and testing the template and then relaunching the instances. This massively reduces migration and administration cost, and makes this tasks just… elastic!

So lautete der Titel des neunten CAOS Report. Erschreckend auf den ersten Blick, hält die Studie aber fest, dass OSS ein Prozess in der Softwareentwicklung sei. Das wiederum ist bekannt, aber was steckt dahinter?

Open Source Business-Modell: Aptana Cloud
Dieser Service bietet SVN, Hosting, Debugging etc für PHP Entwickler. Wer mit der Aptana PHP IDE arbeitet, kann dort seinen Source und seine Applikationen hosten. Der Service kostet US$ 0.04 pro Stunde. Pro Jahr also US$ 350.40. Verglichen mit 3 Jähriger Zend-Lizenz (€ 717.-, ~ CHF 1000.-) + 3 Jahre PHP Hosting mit SSH (SVN auch bald verfügbar), kostet Aptana also gleich viel. (für $ 350.40 gibt es nur 5 GB Space, 10 GB für $ 876.-, 15 GB für $ 1664.40, 25 GB für $ 3241.20 im Jahr).

Dass jeder die IDE Gratis herunterladen kann, macht dabei nichts:

  • Aptana basiert auf Eclipse. OSS dürfte die Entwicklungskosten beträchtlich gesenkt haben.
  • Die Prüfung der Benutzerlizenzen entfällt, das spart Anwälte und Lobby-Kosten.
  • Die freie Weitergabe der Umgebung ist Marketing, das Werbebudget darf tiefer sein.

Aptana ist das beste Beispiel, dass Open Source kein Business-Modell ist, aber viele attraktive Business-Modelle erst ermöglicht.

Als Webworker muss man manchmal viele Formulare ausfüllen, z.B. zum Eintragen von Webseiten auf Linklisten oder Suchmaschinen. Häufig müssen dafür immer die selben Angaben eingetragen werden. Bei Umfangreichen Formularen eine aufwändige Sache.
Das Firefox-Addon “Copy / Paste form” kopiert ganze Formulare auf Klick im Kontextmenü. Anschliessend lassen sich die Werte mit der Kontextmenü-Funktion “Paste Form” wieder ins Formular einfügen. Gerade bei Linklisten eine praktische Sache.

Read more about BoxBackup on boxbackup.org.
And the wiki.

Serverside Installation
for all these steps you need to be root, (sudo su).

apt-get install boxbackup-server
# it will look like its waiting for input, but its not just press Enter,
# and if it hangs press it again, until return to the console.

# configure backup directory.
#create a backup directory, if you want to use userland raid read this.
#you need to know the blocksize (4096) of the partition (/dev/sda1) where the backup is.
# dumpe2fs /dev/sda1 | grep -i ‘Block size’
mkdir /backup
chown -R bbstored:bbstored /backup
rm /etc/boxbackup/raidfile.conf
raidfile-config /etc/boxbackup 4096 /backup

# next is to configure the boxbackup server
# Be sure to replace “hostname” by the correct name.
rm /etc/boxbackup/bbstored.conf
bbstored-config /etc/boxbackup hostname bbstored

# last thing todo for the server is to create the certificates
# This will create a folder “ca”, which is very important, cause it is needed to create the client certificates.
# Also without certificates the backup can’t be used.

cd /root
bbstored-certs ca init
# Sign the certificates prepared by boxbackup.
bbstored-certs ca sign-server /etc/boxbackup/bbstored/boxbackup-server-cert-req.pem
# Copy (not move)
cp -a ca/servers/bserver.hjbaader.home-cert.pem /etc/boxbackup/bbstored/boxbackup-server-cert.pem
cp -a ca/roots/clientCA.pem /etc/boxbackup/bbstored/boxbackup-client-ca-cert.pem

# start the BoxBackup server
/etc/init.d/boxbackup-server start
# if there is no output at all, there is something very wrong..
# logoutput can be found in /log/syslog

Client Installation
for all these steps you need to be root, (sudo su).

Joomla 1.5 ist ja schon seit einer Weile draussen. Zeit mal ein paar nette Links & Fakten aufzuschreiben: