Read Me

opensand is a SAN (Storage Area Network) daemon. It is released under the GPL v3

When opensand starts up, it first uses wakeonlan to start up a couple of disk stations. Each of the disk stations will then export one or more disks using nbd-server. These NBD exports are combined into one or more RAID 5 arrays. All the arrays are then combined into an LVM2 volume group named vg_opensand.

The volume group contains disks and snapshots called lv_disk00000 through lv_disk00499. These disks are again exported using nbd-server (named exports, disk00000 through disk00499). 

opensand will now try to mount a filesystem labelled ENCRYPTIONKEYS. This filesystem contains a couple of files called 1.key through 499.key. Not all files need to be present, for those files NOT present, a file default.key will be used (giving a default encryption key).

The key files contain strings that will be used as encryption keys. The encryption algorithm used for now is a symmetric 256 bit AES cypher. You can even put in random strings. Don't lose your keys though, or you *ARE* screwed!

Make sure that the usb-storage system is linked into your kernel as a module so the USB key disk will be scanned LAST. Otherwise the stick might mess up the device names!

In order to encrypt disk images, a function encrypt (oscontrol) is used.

At this point, a couple of virtualization hosts are started up (using wakeonlan). The virtual systems will run on the disks.

Use the program oscontrol in order to manage the SAN daemon.