Please enable JavaScript.
Coggle requires JavaScript to display documents.
Leto GUI - Coggle Diagram
Leto GUI
"Spaces management" tool
Tab "Products"
(by default)
Products sidebar Menu (search, navigate, new, edit, etc.)
Products View
List of products (cards)
accessible by user
Edit / Create Product
Name and description
Parent Space
Tags to be used (defined in configuration, inherited from parent space and editable)
Team (same as for Space)
Git url for product (by default built from name)
gitops (built by default)
Workflows (see space)
Environments (see space)
Models
New
Go to Modeler (empty model for current product)
Create from Templates (inherited from parent space)
Create from Wizard (inherited from parent space)
Edit Model (go to modeler with current model and product space)
Operate (through workflows) CI/CD
Choose / New / Edit Workflows
Launch or plan workflow
Run (see workflow execution)
New product by a dedicated card with a big "+"
Tab "Templates & Wizards"
Templates & Wizard sidebar Menu
(search, navigate, new, edit, etc.)
Templates & Wizards View
List of user accessible Templates and Wizards at current space
New Template (go to Modeler for curent space)
Edit Template (go to Modeler for current space and selected workflow)
New / Edit Wizard
Form + monaco (for wizard DSL)
Tab "Spaces"
Spaces sidebar Menu (search, navigate, new, edit, etc.)
Spaces View
Hierarchy of spaces
accessible by User
(list of expendable
contanier and
product cards ?)
Edit / Create Space
For New, a "+" card into container spaces
Name and description
Tags to be used (defined in configuration part, inherited from parent and editable)
GitOps URL (read only by default,
built from parent space + space name)
Team (initially, by default,
team is inherited
from parent space)
A team is a set of members
with roles on the space scope
Add, delete member
Assign roles to member
(roles are defined in configuration part)
Chosen named workflows (default names are "onboarding, CI, CD, etc.) Ability to define new ones.
Environments
(by default, the ones, defined at upper level)
Templates and Wizard (go to "Tab Temlplates and Wizard" fot the space
Tab "Workflows"
Workflows sidebar Menu (search, navigate, new, edit, etc.)
Workflows View
List of Workflows (cards) by type (CI / CD /
onboarding / team event / operations)
accessible by user at current space
New Workflow (form + Monaco editor) for current space
Edit Workflow (form + Mocano editor)
Tab "Dashboard"
"Modeler" tool
Tab "Modeler"
(by défault)
Model Sidebar Menu (componants and navigation)
Model View (3D models)
Tab "Source editor"
Source View (Monaco Editor)
Source Sidebar Menu (file hierarchy management)
"Configuration" Tool
Super-admin
sections
Tab "Cluster"
(super-admin access only)
Cluster Members
View
List of cards
describing members
Note :
configuratrion is at cluster level (same for each member)
Each card :
Health state (running, error, etc.)
Stats : available storage, cpu %, etc.
Each card describes one member with its name (address:port)
Delete button at upper right corner
to stop and remove a member from configuration
Right panel
shows cluster level
configuration and stats:
name of the cluster, database path, port used, etc. (to be reviewed);
uptime, cpu, storage, network ios, etc.;
database stats (global and per tenant storage used, etc.)
Specific "+" card
to allow
new member declaration
Step 1: When clicked
, expended into a form to declare new member
Step 2: When validated
, built configuration file (yaml) is printed, can be copied or downloaded)
Cluster members management
sidebar menu
:
search member, navigate (list of members), new member, edit cluster configuration.
Note :
only one Cluster exists (named
"gandalf"
)
Tab "Tenants"
(super-admin access only)
Tenants
View
List of cards
describing tenants
Each card :
Name and short description for the Tenant
Health state (running, error, etc)
Number of members of the tenant
Delete button on upper right corner only if tenant is empty (no more aggregators)
Stats
Specific "+" card
to allow
new member declaration
Step 1: When clicked
, expended into a form to declare new tenant (mainly name and description)
Step 2: When validated
, built configuration file (yaml) is printed, can, be copied or downloaded)
Right panel
show Tenant
configuration when a tenant card is clicked
name and description of the tenant, database name, etc.
database stats fot the tenant
aggregators info and list
Note:
One default Tenant pre-exists
which is named
"Gandalf"
and should be used
only for administration purpose.
Tenants management
sidebar menu
:
search, navigate, new, delete edit tenants
Tenant admin
sections
Tab
Aggregators
(tenant admin access)
Aggegators management
sidebar menu
:
search, navigate, new, delete and edit aggregators
Note :
This section is under one specific tenant (non super admin users can not see other tenants) and super admin user can not see inside tenants.
Aggregators
View
List of cards
describing aggregators
Each card :
Name and short description for the aggregator
Health state
When clicked
, card is expended
Each members is shown as a
card inside
outside card
Note :
when clicked, card is expended to show members inside
A
specific '+' inner card
is shown to declare new member
for the aggregator
Step 1: When clicked
, expended into a form to declare new member of aggregator
Step 2: When validated
, built configuration file (yaml) is printed, can, be copied or downloaded)
Delete button at upper right corner if no more members
stats
Version
Specific '+' card
to
declare new aggregator
Step 1: When clicked
, expended into a form to declare new tenant (mainly name, description, version)
Step 2: When validated
, built configuration file (yaml) is printed, can, be copied or downloaded)
Right panel
show aggregator configuration
when one card is clicked
name and description of the aggregator
connectors synthetic info and stats
Note :
When a Tenant is created (using generated configuration file), one default aggregator
admin
is created
Tab Connectors
(tenant and domain admins)
Connectors
View
Filter section
Note :
Connectors have a type (between max 10~15 possible vaules)
A Connector belongs to only one aggregator
Filter section
allows to filter connectors listed in the "list section
Section "types"
to define chosen types in the filter : list of toggle switch buttons (or cards?) for connector types
Section "aggregators"
to define chosen aggregators in the filter : list of toggle switch buttons (or cards ?) for aggregators of the tenant
List section
Note :
Connector list shows only connectors of type is one of those selectred in the section "types" of the filter and the aggregator it is linked is one of those selected in the section "aggregators" of the filter
No selection in filters is equivalent to everything is selected
List of Cards
describing
filtered connectors
Each Card
Name and description for the connector
Version
Type of the connector
Product for the connector
Delete button
Heath state
stats
When clicked,
, card is exended
Note :
card is expended to show members inside
Each member is shown as a
card inside
outer card
A
specific '+' inner card
is shown to declare new member for the aggregator
1 more item...
Specific '+' card
to
declare a new connector
Step 1: When clicked
, expended into a form to declare new coonnector (mainly name, description, version, type of connector, product for the connector)
Step 2: When validated
, built configuration file (yaml) is printed, can, be copied or downloaded)
Right Panel
show connector level configuration
when one card is clicked
name and description of the connector
version of the connector
type of the connector
product for the connector
members synthetic info ans stats
healthstate for the connectir
Note :
This section is under one specific tenant (non super admin users can not see other tenants) and super admin user can not see inside tenants.
Connectors management
sidebar menu
:
search, navigate, new, delete and edit aggregators
Tab
"Users and Roles
management"
OpenIdConnect config
Role management
List of users
Each user :
Name, password (if internal user)
List of access rules
add ruke
remove rule
edit rule
Note :
a rule is a role on a domain for the current user
"+" Add user card
Tab
"Tags"
Note :
heirarchy of tags to be used