Provide validation of new extra specs key/value pairs

Registered by Julie Gravel on 2014-10-16

Summary:
Currently users manage the volume type extra specs through the “View Extra Specs” action in Admin -> Volumes -> Volume Types table. This action allows users to create, edit, and delete extra specs associated to a volume type via a simple table and dialog mechanism. Both the “Create Volume Type Extra Spec” and the “Edit Volume Type Extra Spec” dialogs do not offer any validation as to whether or not the key/value pair is legitimate. Users can type in pretty much any key or any value and have no way of knowing whether the key/value pair is valid or not until the time that the volume type is used during the volume creation process.

Motivation:
Horizon should provide a process that helps to guide users into completing a task in a more intuitive way which consumes less time.

Description:
The purpose of this blueprint is to provide the extra specs key/value pair validation. The validation should happen right in the dialog where the key/value pair is being created or edited. This is so that users can be confident that the key/value pair they set up is legitimate and will not cause any issue down the road at the time of volume creation.

This blueprint depends on the completion of another blueprint: https://blueprints.launchpad.net/horizon/+spec/vol-type-extra-specs-describe, which will replace the “Create Volume Type Extra Spec” and the “Edit Volume Type Extra Spec” dialogs with a new widget.

UX:
When users finish entering values for the keys in the new “Manage Volume Type Extra Spec” widget, they can click the Save button. The validation of the new key/value pairs will happen at this point. If the validation succeeds, the pairs will be added to the extra specs. Otherwise, the Cinder command will report the failed validation with an explanation. Users can then correct the values in the same widget. The error reporting feature have might already existed in the widget. If not, the widget will be enhanced to include the error handling and the ability to stay available to receive the new values until the validation succeeds.

Outside Dependencies:
An existing Cinder API and the corresponding command to set the volume extra specs will be enhanced to provide the extra-specs key/value pair validation. Please see the cinder specs proposal at https://review.openstack.org/127646 - specs/kilo/validate-vol-type-extra-specs-key-value.rst.

Requirements Update Required:
N/A

Doc Impact:
N/A

Blueprint information

Status:
Complete
Approver:
David Lyle
Priority:
Low
Drafter:
Julie Gravel
Direction:
Approved
Assignee:
Julie Gravel
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
David Lyle on 2016-10-28

Related branches

Sprints

Whiteboard

asahlin: +1

Gerrit topic: https://review.openstack.org/#q,topic:bp/vol-type-extra-specs-validate,n,z

Addressed by: https://review.openstack.org/173552
    Validate volume type extra specs

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.