volume type extra specs. horizon/cinder enhancements
DESCRIPTION
Some screenshots of the current Horizon Cinder Volume Type workflow with examples of the new features for extra specs.TRANSCRIPT
Create Volume Type Enhancement
Get Volume Backend Names
Before:
Before:
After:
After:
Volume Type Extra Specs Enhancement
Get Supported Extra Specs
Before:
Before:
Before:
Scenario 1: no backend name
Option A – offers no keys (current)Option B – offers keys from all drivers (future)
After: option A
After: option B
Scenario 2: one backend name
[group1]volume_backend_name = foovolume_driver = cinder.volume.drivers.san.hp .hp_3par_fc.HP3PARFCDriver
After:
After:
Scenario 3: shared one backend name
[group1]volume_backend_name = foovolume_driver = cinder.volume.drivers.san.hp .hp_3par_fc.HP3PARFCDriver
[group2]volume_backend_name = foovolume_driver = cinder.volume.drivers.san.hp .hp_3par_iscsi.HP3PARISCSIDriver
After:
After:
Scenario 4: two backend names[group1]
volume_backend_name = foovolume_driver = cinder.volume.drivers.san.hp .hp_3par_fc.HP3PARFCDriver
[group2]volume_backend_name = foovolume_driver = cinder.volume.drivers.san.hp .hp_3par_iscsi.HP3PARISCSIDriver
[group3]volume_backend_name = barvolume_driver = cinder.volume.drivers.san.hp .hp_lefthand_iscsi.HPLeftHandISCSIDriver
After:
After: