Console: integration and optimisation

[grabl]

This issue was originally posted by @haikalpribadi on 2018-04-09 17:11.

Why:
Grakn functions are exposed through different executables - some through grakn, some through graql, and some others through the KGMS console.
How:
Merge all console interfaces into one grakn-[core|kgms]-console.jar

This issue needs typedb/typedb#3087, needs #7, needs graknlabs/grakn#3581, needs typedb/typedb#3743, needs typedb/typedb#3798, needs typedb/typedb#3807, needs graknlabs/grakn#3868, needs graknlabs/grakn#3871

[grabl]

This comment was originally posted by @haikalpribadi on 2018-01-08 19:10:36+01:00.

We should provide KGMS users with a dedicated Grakn console, as there will be lots of interactions for KGMS, as well as Cluster coordination commands.
 
Goals

• To provide a command-line user interface targeted at system administrator
• Must provide an interface for a sysadmin be able to orchestrate a cluster
• The interface must align with the authentication requirements
   
  Approach For Starting A Server / Cluster
  Server / Cluster management can be performed using the following commands:

1. grakn-kgms server start
2. grakn-kgms server start --join $EXISTING_CLUSTER_IP (when it is ran, it will prompt for a superuser-level credential)
3. grakn-kgms server start --join $EXISTING_CLUSTER_IP --user $USER --password $PASSWORD (supply superuser-level credentials directly)
    
   Approach For User Management
   This can be served once the user starts the console: grakn-kgms console. When it is ran, it will prompt for a superuser-level credential, and open a special console for user management. this is useful since you don't have to enter to command multiple times)
    
   Open Questions

• Revisit the syntax of showing cluster status to a user
• Revisit what information to display on the cluster status message

[grabl]

This comment was originally posted by @lolski on 2018-01-26 11:56:14+01:00.

Goals

• To provide a command-line user interface targeted at system administrator
• Must provide an interface for a sysadmin be able to orchestrate a cluster
• The interface must align with the authentication requirements
   
  Approach
• "grakn cluster configure " - tell grakn to join a cluster. it should communicate with the cluster via the specified listen adress
• "grakn cluster status" - display cluster status
• "grakn cluster status " - display status of the specified node
   
  Open Questions
• Revisit the syntax of configuring a cluster
• Revisit the syntax of showing cluster status to a user
• Revisit what information to display on the cluster status message

[grabl]

This comment was originally posted by @lolski on 2018-09-05 18:14:20+02:00.

@haikalpribadi Removing the following from the description because they made the requirement too broad:
 

• refine all commands to be better designed
  - fix console bugs
   
  Let's keep this one requirement focused on just merging the different executables?

[lolski]

The main goal of this issue has been implemented: unify different console interfaces into one (ie., into TypeDB Console).

The comments contain more proposals regarding the management of TypeDB Cluster which have all been transferred to a new dedicated issue: #179.

Closing this issue.