...

<Describe which user roles are related to the problem AND the solution, e.g. admin, deployer, node owner, etc. If you need to define a new role in your design, make that very clear. Remember this is about what a user is thinking when interacting with the system before and after this design change. This section is not about a UI, it's more abstract than that. This section should explain all the aspects of the proposed feature that will surface to users.>

User experience is similar to the experience with a cloud/centralized solution:

• From a single point, the distributed data can be queried as if the data is hosted in a centralized database.
  • A user selects a database from a list of virtual databases.
  • A user selects a table from a list of virtual tables.
  • A user issue q query to the table.
  • The user can specify all nodes with relevant data (nodes with data associated to the table), or specify a subset of nodes (for example: nodes deployed in a region or nodes with a named data owner).
• From a single point, all the resources are monitored and managed as if the resources are hosted in a single machine. 
  • User can issue a status request from all nodes or to  a subset of nodes (for example: nodes deployed in a region or nodes with a named data owner).
  • Users can query an aggregator node.
• Using the rule engine, users and processes can be alerted by events on the individual nodes or on the aggregator node.

Command Line Interface

<Describe any changes to the hzn CLI, including before and after command examples for clarity. Include which users will use the changed CLI. This section should flow very naturally from the User Experience section.>

...