Import cluster UI

[kamleshverma1]

We are going with dynamic generation and we have common form generator.
we are using this form generator for generate the form but in the import cluster case , we have different ux design , not common select box or textbox as we have in form generator.
so finally for import cluster we are not going ahead with dynamic generation for now. it will be static but we will use directive for table view.

[brainfunked]

I'm renaming this specification to address it's scope properly. This needs to be linked to the import cluster related jira issues and the specification needs to address how you're planning on implementing the UI itself and at each step, link to the appropriate UX slide.

[brainfunked]

Linked to #54

[kamleshverma1]

Import cluster UX slide :
https://docs.google.com/presentation/d/18jbUSbQbbcDBo4PI58q-uZbKTm0Ai0msePpsMfLio-k/edit#slide=id.g154cd53edc_0_0

[mcarrano]

@kamleshverma1 Note that the UX link you pasted above is to an old design. The latest/current design is posted to InVision here: https://redhat.invisionapp.com/share/R88EUSGJK

[kamleshverma1]

Linked for Jira Tickets : https://tendrl.atlassian.net/browse/TEN-171

[kamleshverma1]

Linked for tendrl-frontend issue : Tendrl/ui#63

[julienlim]

I believe the Import Cluster JIRA user stories that this spec needs to link to are as follow:

• Import Ceph 2.x cluster (https://tendrl.atlassian.net/browse/TEN-4)
• Import Gluster 3.2 cluster (https://tendrl.atlassian.net/browse/TEN-3)