DaanHoogland commented on issue #5794: URL: https://github.com/apache/cloudstack/issues/5794#issuecomment-1048180209
> @DaanHoogland this rarely happens. But decided to open a discussion as I've seen it happen. It is quite fun to move hosts around CloudStack "logical" clusters. > > To "move" a host between clusters it is needed just a few changes in DB and host's `agent.properties`. It is not hard to do it "manually" so I'm not sure if it justifies an API call. But I rather first hear what you guys have in mind and if this could maybe add some interesting dynamic for operating KVM-based clusters. > > Keep in mind that a Pod is a "DC Rack" that contains one or multiple "clusters". In that sense, KVM hosts can easily be changed from clusters when residing in the same Pod as they are using the same switch (L2 network). Therefore, no networking nor pool changes are required in such cases, neither unplugging/plugging hosts in different racks. Yes, so that would limit changing clusters within a pod, would it? As said and though I like the idea from a logical point of view, I fear it will not be used as much as it would seem at first sight. If however it is persistently done manually it does justify an API endpoint as manual DB manipulation should be avoided. -- 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]
