ISSUE TYPE
COMPONENT NAME
SUMMARY
CloudStack does not list VMs that are in a project unless the listVirtualMachines API request has the specific project ID set on projectid parameter. I don`t see why we do not provide any way of listing all VMs.
Looking at the documentation of listVirtualMachines, when listall=true it lists all VMs that the caller is authorized to see; if set to false, it lists just the resources owned by the caller.
With that said, I think that the admin should be allowed to list VMs on projects when the request containslistall=true. Does anyone (dis)agree with that?
I would like to take the liberty and propose/discuss two approaches to fix/enhance it:
- Add support for Admins to list VMs on all projects when listall=true; or,
- add a new parameter that will allow the Admin to list all VMs, including those in projects.
Considering the API's documentation, the first approach fits well as Admin is indeed authorized to see all VMs; however, the second option avoids any possible backward compatibility and adds finer granularity to Admin's requests.
ISSUE TYPE
COMPONENT NAME
SUMMARY
CloudStack does not list VMs that are in a project unless the
listVirtualMachinesAPI request has the specific project ID set onprojectidparameter. I don`t see why we do not provide any way of listing all VMs.Looking at the documentation of listVirtualMachines, when
listall=trueit lists all VMs that the caller is authorized to see; if set to false, it lists just the resources owned by the caller.With that said, I think that the admin should be allowed to list VMs on projects when the request contains
listall=true. Does anyone (dis)agree with that?I would like to take the liberty and propose/discuss two approaches to fix/enhance it:
Considering the API's documentation, the first approach fits well as Admin is indeed authorized to see all VMs; however, the second option avoids any possible backward compatibility and adds finer granularity to Admin's requests.