[jira] [Updated] (CLOUDSTACK-10446) View Logs in the UI

["David Jumani (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jumani updated CLOUDSTACK-10446:
--------------------------------------
    Description: 
As of now, when an admin encounters an issue or error in CloudStack, the maximum information they can immediately get is the API failure response which provides a reason for the failure. At times this might not be sufficinet to diagnose the error and would require the admin to investiage the CloudStack logs. This would require the admin or the sysadmin to log into the VM running CloudStack and either view or export the logs, and then dive into identifying the issue. This idea aims to eiliminate that step.

The goal of this is to provide admins the ability to view the logs directly in the UI. This would make diagnosing failures and RCAs much quicker.

Provide the ability display the logs in the UI

Add an API / WebSocket (and UI) support to :
 * View the logs
 * Live follow the logs (similar to 'tail -f')

 

Duration
 * 175 hours

 

Potential Mentors
 - David Jumani

 

References
 * https://github.com/apache/cloudstack/issues/6011

 

  was:
Shutting down / Restarting Cloudstack is a necessary step in upgrades, system maintenance, etc. As of now, there is no way to safely shutdown or restart CloudStack. It is directly terminated via systemd. Since this is the case, any asyncronous job or background task is abrubptly terminated and can fail. As of now, CloudStack maintains a list of asynchronous jobs wihtin it's database along with their status.

This idea aims to provide a way to safely shutdown CloudStack. It involves two parts :
 * Prevent new asynchronous jobs from being added to CloudStack when a safe shutdown is triggered
 * Check the status of the async jobs and Shut down CloudStack when all the jobs have been completed

 

Provide the ability to safely shutdown CloudStack

Add API (and/or UI) support to :
 * Trigger a safe shutdown
 * (Optional) Support restarts
 * (Optional) Support a forced shutdown when CloudStack will quit even if there are async jobs running

 

Duration
 * Some Experience : 175 hours
 * Newbie : 350 hours

 

Potential Mentors
 - David Jumani

 

References
 * https://github.com/apache/cloudstack/issues/6021

 


> View Logs in the UI
> -------------------
>
>                 Key: CLOUDSTACK-10446
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10446
>             Project: CloudStack
>          Issue Type: Improvement
>            Reporter: David Jumani
>            Priority: Major
>              Labels: gsoc2021, mentor
>
> As of now, when an admin encounters an issue or error in CloudStack, the maximum information they can immediately get is the API failure response which provides a reason for the failure. At times this might not be sufficinet to diagnose the error and would require the admin to investiage the CloudStack logs. This would require the admin or the sysadmin to log into the VM running CloudStack and either view or export the logs, and then dive into identifying the issue. This idea aims to eiliminate that step.
> The goal of this is to provide admins the ability to view the logs directly in the UI. This would make diagnosing failures and RCAs much quicker.
> Provide the ability display the logs in the UI
> Add an API / WebSocket (and UI) support to :
>  * View the logs
>  * Live follow the logs (similar to 'tail -f')
>  
> Duration
>  * 175 hours
>  
> Potential Mentors
>  - David Jumani
>  
> References
>  * https://github.com/apache/cloudstack/issues/6011
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)