[
https://issues.apache.org/jira/browse/CLOUDSTACK-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jumani updated CLOUDSTACK-10445:
--------------------------------------
Description:
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
was:
ClouStack Kubernetes Service [CKS] is CloudStack's own managed Kubernetes
offering which users can use to deploy and manage Kubernetes Clusters from
CloudStack. However, there might be cases in which users may want to deploy
their own Virtual Machines and convert them into Kubernetes Nodes to run their
own personally managed Kubernetes Clusters outside the scope of CloudStack.
In such cases, CloudStack is unaware of these clusters and sees them as just a
bunch of VMs running on its infrastructure. Although this might be acceptable,
it would be a good idea for users to make CloudStack aware of the existing
unmanaged Kubernetes Clusters and be able to view them in the UI or via an API
Provide the ability to make CloudStack aware of these unmanaged Kubernetes
Clusters
Add / Modify existing API (and/or UI) support to :
* Add an unmanaged Kubernetes Cluster
* Update an unmanaged Kubernetes Cluster
* Delete an unmanaged Kubernetes Cluster
Duration
* 175 hours
Potential Mentors
- David Jumani
References
* https://github.com/apache/cloudstack/issues/6036
> Add the ability to Safely Shutdown / restart CloudStack
> -------------------------------------------------------
>
> Key: CLOUDSTACK-10445
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10445
> Project: CloudStack
> Issue Type: Improvement
> Reporter: David Jumani
> Priority: Major
> Labels: gsoc2021, mentor
>
> 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
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
