Page History

...

For example, in the GUI we would like to have a storage provider field for the CO and DO windows (this equates to the name of one and only one storage provider). If the admin inputs a specific storage provider, he can enter in an arbitrary number of key/value pairs in another text field (perhaps we would provide a nice entry dialog to make this easier in the GUI). These key value pairs can be passed into the storage driver when it's asked to create (or update) a volume and the storage driver can decide what each and every key/value pair means, if anything.Reference

References

JIRA-xxxx: https://issues.apache.org/jira/browse/CLOUDSTACK-xxxx

Use

...

cases

• An admin wants to ensure a root or data disk uses the plug-in of a specific storage vendor because he wants to make sure he can leverage vendor-specific properties.
• The admin creates a Compute or Disk Offering and selects the desired storage plug-in from a combo box. The admin enters in an arbitrary collection of key/value pairs (in the following form: key=value;key=value;key=value). These keys and values are vendor specific and have no meaning to CloudStack (CloudStack simply passes them to the selected storage plug-in and the plug-in decides what, if anything, to do for each key/value pair). We will likely have a dialog in the GUI that makes entry of key/value pairs easier and less error prone than manually entering them in.
• A user executes such a Compute or Disk Offering, which leads to the creation of a root or data disk (respectively) that was created using the storage plug-in specified in the Compute or Disk Offering and the arbitrary collection of key/value pairs, if any.

...

The GUI will likely provide a helper dialog to list all applicable properties for a given storage plug-in as well as performing basic verification of input based on the type the property is (ex. Integer).

...

Database changes

We will need to add two columns to the cloud.disk_offering table: provider and custom_properties.

The provider value should match one of the provider values in the storage_pool table.

The custom_properties value should be of the following format: key_1=value_1;key_2=value_2;key_3=value_3...key_n=value_n