GabrielBrascher opened a new issue #5794:
URL: https://github.com/apache/cloudstack/issues/5794


   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Feature Idea
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   API
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.17
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   KVM
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   N/A
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   CloudStack does not allow to migrate hosts from clusters. This Issue raises 
the feature idea of migrating hosts between clusters.
   In KVM at least this is quite easy to be done. Basically, it can be done by 
changing the agent.properties and updating a few tables in the DB.
   
   At first, I would propose creating such an API command only for KVM. As far 
as I know, `XenServer` & `VMware` aren't as simple. Quite a long time since I 
played with Xen or VMware, so I am not raising them here. But anyone interested 
in discussing raising it. feel free.
   
   The idea is that such a host should be placed into maintenance, making sure 
that no VMs will be running.
   If the host is in Maintenance, then the API command would run the needed 
changes in order to have the host available at other cluster.
   This would require Admins to ensure that the shared storage pool is 
available at the zone-wide level.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to