Thanks for the suggestion. In my opinion, it does make sense allowing listing VMs using a clusterId. I would only expose this functionality to root admins though. The same goes for deploying a VM on any host of a specific cluster. Probably these enhancements were not developed because people did not have the use case for it. I think you could register this proposal in the issues section. You can then get people from your team to develop it (we will for sure help reviewing it).
On Fri, Jun 1, 2018 at 3:53 PM, Yiping Zhang <yzh...@marketo.com> wrote: > Hi, all: > > When making CloudStack API calls on VM instances, many APIs accept > parameters to filter VM instances based on domain, pod, and host, where the > VM instances belong to. However, we can’t filter VM instances based on the > cluster! I am wondering if this is a deliberate design decision or it is > just an unfortunate neglect? > > For example, when calling listVirtualMachines API, I can list all > instances belonging to a domain or running on a host, but I also would like > to be able to list all instances running on a particular cluster; for > startVirtualMachine API, I’d like to be able to start an instance on any > hosts belonging to a particular cluster (for affinity group concerns). > > IMHO, supporting such cluster wide operations, wherever it makes sense to > do so, would be a great convenience improvement for cloud admins and > operators alike. > > Yiping > -- Rafael Weingärtner
