[DATALAB-1919] [Part1][Back-end]: Set of audit tasks

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: v.2.4
• Component/s: DataLab Main
• Labels: AWS AZURE Back-end Debian GCP RedHat
• Epic Link: Audit
• Sprint: Apache DLab release 2.4
• Assignee: Oleg Fuks
• Reporter: Vira Vitanska
• Created: 03/Jul/20 10:56
• Updated: 16/Sep/20 08:44
• Resolved: 08/Jul/20 14:27

Description

1. Update of total quota is not shown in audit - we should wait if we need total quota
2. Change action for endpoint of audit: Create -> Connect, Delete -> Disconnect 
3. If we disconnect endpoint all resources are terminated. Show which resources are terminated in audit 
4.  If we stop notebook all related computational resource except for Data engine service will be terminated. So show terminate action, not stop for DES 
5. Show information icon for computational resource in case of stopping/starting/termination not directly the cluster, but via notebook or via project management (action menu) -  it will do in ticket https://issues.apache.org/jira/browse/DLAB-1932
6.  If create new edge node in existing project add information icon for update project with the following info: 'Create edge node for endpoint <endpoint_name>, requested in project <project_name> 
7. If we add git account should be Add in action, NOT Update. Show information icon: 'Add host <host_name>'  it will do in the ticket https://issues.apache.org/jira/browse/DLAB-1936
8. If we update git account show information icon: Fields -> Previous value -> New value. If user changes a password the password field should be shown, but do NOT show the password. instead of password value you can show six bullets -  it will do in the ticket https://issues.apache.org/jira/browse/DLAB-1936
9. If we decommission git account should be Decommission in action, NOT Update. Show information icon: 'Decommission host <host_name>'  it will do in the ticket https://issues.apache.org/jira/browse/DLAB-1936
10.  If user updates quota only for one project do not convey the value of the other project if values is the same as previous (It will be fixed on UI side)
11.  Instead of 'Computational' use 'Compute' in 'Resource type' column 
12.  If user follows compute link change 'Notebook' to 'Compute' in 'Resource type' column 
13.  Reconfigure notebook. Change 'Notebook config' -> 'Notebook' in 'Resource type' column 
14.  Reconfigure spark cluster. Change 'Computational config' -> 'Compute' in 'Resource type' column 
15.  Reconfigure notebook/spark cluster. Rename action from 'Update' to 'Reconfigure' 
16.  Date value should be sorted from the newest to the lates in grid 
17.  Show information if user goes to Web terminal 
18.  Image creation: Instead of 'Image' use 'Notebook' in 'Resource type' column -  it is not a bug, so it will not fix
19.  Scheduler set up for notebook/cluster: Instead of 'Notebook scheduler'/'Computational scheduler' use 'Notebook'/'Compute' in 'Resource type' column 
20.  Rename action for scheduler configuration from 'Create' to 'Configure' or 'Set up' 
21. Convey information icon for stop by scheduler for spark cluster if scheduler is triggered for notebook - will do in the other ticket https://issues.apache.org/jira/browse/DLAB-1931
22.  If stop notebook by the other user (via environment management), related cluster stopping should also be shown as stopped by the other user, NOT by owner 
23.  Related stopped cluster are not shown in audit during notebook termination 
24.  Related stopped notebook/spark cluster are not shown in audit during project termination 
25.  If the cluster stopped/started/terminated by the scheduler change message Scheduled action -> 'Terminate/stop/start by scheduler, requested for notebook 'notebook_name'.'