Add support for Datastores to Trove dashboard

Registered by Michael Yu on 2014-01-27

1) Add Datastore type/version dropdown in Launch Instance
2) Add Datastore type/version in Instance List and Instance Details

Blueprint information

Status:
Complete
Approver:
David Lyle
Priority:
Low
Drafter:
Michael Yu
Direction:
Approved
Assignee:
Michael Yu
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Michael Yu on 2014-04-15
Completed by
David Lyle on 2014-07-17

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/datastore-support,n,z

Addressed by: https://review.openstack.org/75269
    Initial support for datastore in Horizon

[2014-03-10 mrunge] I'd like to see a bit more, what is planned here.

[2014-04-09 michayu] See below:

Added datastore type and version columns in Instance Table
Added datastore type and version in Instance Details
Added appropriate Connection Examples (for each datastore type) in Instance Details

Patchset #16+ has single dropdown approach with the following behavior:
- Auto select only if there's one datastore type and version
- Otherwise, enforce user to choose one
- Single dropdown uses optgroups to group versions for each datastore type

Patchset #15 has double dropdown approach with the following behavior:
- Initially, only the datastore type dropdown is shown
- If there is only 1 datastore type, it will be auto selected
- Once a datastore type is selected, the datastore version dropdown will appear
- Datastore versions will be populated dynamically per the datastore type chosen
- If there is only 1 datastore version, it will be auto selected
- Last chosen datastore version (for that datastore type) will be saved when switching between the various datastore types

Trove community decided (in weekly meeting) to go with single dropdown approach (at least for now). If most providers generally start having many datastore-types and many datastore-versions for each datastore-type, then we can revisit the double dropdown patchset.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.