OpenNebula

The help blurb in Sunstone, the 'man' page for oneimage, and the usage message emitted by oneimage all document the "fstype" argument given when creating a new datablock image as:

         Type of file system to be built. This can be any
          value understood by mkfs unix command.

This obfuscates the reality of the code in /usr/lib/one/sh/scripts_common.sh which implements handling of "raw", "swap", "qcow2", and (sloppily) "vmdk_*" as possible values. The web documentation mentions "swap" and "qcow2" as possible values but not the vmdk_* options. The "Image Guide" page lists fs types that may or may not reflect those available on any particular system without any additional explanation, while the "Image Template" page explicitly states non-support for VMWare.

There's an underlying design error here that arguably should be fixed by making "fstype" strictly as the man page says (with "swap" as a possible addition) while breaking out the image formats to an independent parameter, but with the code as it is, the docs lead to confusion. The best example is qcow2: the apparent but wrong way to create an empty qcow2 image with oneimage is to use a "driver" value of "qcow2" and an arbitrary fstype, since it is a required parameter. That runs and creates an image, but it is useless: raw format, marked for use with the qcow2 transfer driver. Documenting the quirky design pending a proper fix would help users who are not ready to investigate what the code really does.