[Tendrl-devel] Import Cluster UX Design Review - workflow summary

[Ju Lim]

Team:

Based on the review we had earlier today, here's a summary of the import
cluster UI workflow (based on our discussion):

*Triggers (where this workflow is launched):*

   - Landing Page / First Time Experience
   - Cluster List view


*Workflow:*

1. User clicks on “Import Cluster.”

2. User specifies whether he / she wishes to import a Ceph or Gluster
cluster.

3. If Tendrl is able to discover hosts, which would need to have the Tendrl
node agent pre-installed and pre-configured, it will display the list of
automatically discovered hosts (for the cluster type user selected in #2)
that are not being managed by Tendrl.

4a. User selects 1 host from the auto-discovered hosts.

   - For Ceph, you need specify a Monitor host within the Ceph Cluster.
   Initially, Ceph 2.x cluster will be supported.
   - For Gluster, you can specify any host within the Gluster trusted
   storage pool (or cluster). Initially, Gluster 3.2 cluster supported.


If User does not want to select a host from the auto-discovered hosts list,
proceed to #4b.


4b.  If there are no hosts presented, System should automatically prompt
user to specify a host (bootstrap node).

   - If Ceph, user would need to specify a Monitor host.
   - If Gluster, it can be any host within the Gluster trusted pool.

5. System prompts user whether to use login credentials or SSH keys for the
selected host.

   - If login credentials, user specifies the user and password.  If
   non-root user, then password has to be sudo password.
   - If SSH keys, user has to provide SSH key.

System will assume (and use) the same credentials or SSH key for all hosts
in the same cluster.


6. System lists a confirmation screen with all the hosts in the cluster
along with login credentials or SSH keys, and it will visually indicate any
host in the cluster whereby the login credentials or SSH key does not work.


   -  The list will include host name, IP address, Operating System,
   Gluster / Ceph + release.
   -  For Ceph, displaying server role for each host is a nice-to-have (if
   possible).

7. (Optional) User can change / overwrite any of the login credentials or
SSH key that is having problems.

   - This is probably rare and an edge case.  What this means is that user
   needs to fix this before he/she can resume this workflow.

8. If cluster associated with the selected host contains an unsupported
configuration (e.g. unsupported Ceph or Gluster release, System notifies
user to select another cluster to import or to cancel import.

   - For non-production Ceph / Gluster clusters, System will warn user that
   the cluster is considered Poc / demo cluster and may have restricted
   capabilities after cluster is completed.  The same applies to EC volumes
   that are not supported or volume types not supported in the initial Tendrl
   release.  Same for Gluster (and/or host) hooks for gluster trusted storage
   pools (if applicable).

   This is just a short list of what's not supported in the initial list,
   and the fuller list on what's supported or qualified should be listed in
   the user story.

9. System generates a task for the import cluster as part of the execution.


I figured I'd send this summary out, and folks can think about it before
tomorrow's UX design review discussion.

*References*

   - JIRA: https://tendrl.atlassian.net/browse/TEN-3 (Import Gluster
   Trusted Storage Pool)
   - JIRA: https://tendrl.atlassian.net/browse/TEN-4 (Import Ceph Cluster)
   - UX Design: https://redhat.invisionapp.com/share/R88EUSGJK


Thank you,
Ju