Improve Import Cluster flow

Tendrl / specifications

Tendrl specs go here

GNU Lesser General Public License v3.0

6 stars 16 forks source link

Improve Import Cluster flow #213

Closed r0h4n closed 6 years ago

r0h4n commented 7 years ago

Import cluster flow should use nodes with matching detected cluster id's for import and not rely on user input for the same.
NS.tendrl.objects.Cluster needs new attr "errors" which point out cluster wide errors at present.
NS.tendrl.objects.Cluster needs new attr "is_managed" which points out if the cluster is managed by tendrl or not.
Per node errors related to the cluster will live at NS.tendrl.objects.DetectedCluster (which is per node)

anmolbabu commented 7 years ago

Gluster volume profile needs to be started for brick level iops to be available.. Which means import cluster should start profiling probably as a last step of the flow..

julienlim commented 7 years ago

@r0h4n @Tendrl/tendrl-core @Tendrl/qe @mcarrano

Related UI design: See Import Cluster mockup in Design B.