BonFIRE logo and link to main BonFIRE site

Previous topic

Overview of Storage

Next topic

Datablock Portal How-To

This Page

Datablock StorageΒΆ

If the OS storage provided with the VM images offered in BonFIRE is not enough, VM’s storage can be extended with DATABLOCK resources, for which you can define the file system of (e.g., ext3, jfs, reiserfs) and the desired storage size. It is also possible to make this storage extend the root partition of your compute node instead of using it as a separate partition. See the storage attributes page for more details about the OCCI configuration options for storage. Depending on the testbed you use, the datablock might or might not be automatically mounted. Only be-ibbt testbed automatically mounts the datablocks. For other testbeds, the datablock will be linked to the VM and appears as a hard drive. Depending on the number of disks and the testbed, it will be usually available as /dev/xvdc and as /dev/sdb in pl-psnc. You can mount it using:

root@yourvm:~# mount /dev/xvdc /mnt

By default, storage resources that are created in BonFIRE are duplicated when they are deployed with compute resources, and are destroyed after the experiment duration has finished. Whilst other resources (compute and network) must be created within the context of an experiment, storage resources can be created outside of an experiment and will therefore outlive the duration of any experiments that use that storage resource. Moreover, it is possible to persist the storage resources on the OpenNebula testbeds in BonFIRE (see the Infrastructure page), so that data written to the storage during the execution of an experiment is saved when the compute resource is shut down.

For information about how to use datablock storage, please see the following links: