[
https://issues.apache.org/jira/browse/CLOUDSTACK-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905369#comment-15905369
]
ASF GitHub Bot commented on CLOUDSTACK-9600:
--------------------------------------------
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1999
@resmo I still think vpcid should not be added to UserVmResponse, because
vm can be added to multiple vpc tiers (same as networks, this is why I asked
about networkid at the beginning), I just confirmed yes.
I am not clear what your issue is. Anyway, if you want to know which vpc
the vm belongs to, you can still get the vpcid from NicResponse (even now, if
you get networkid of nic, then you can get the vpcid from networkid via
ListNetworks).
> listVirtualMachines: return vpcid if VM is in VPC.
> --------------------------------------------------
>
> Key: CLOUDSTACK-9600
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9600
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, VPC
> Reporter: René Moser
> Labels: instances, vpc
> Fix For: Future
>
>
> listVirtualMachines API does not return vpcid for VMs in VPCs. There is no
> easy way to find out if VM is in not in a VPC.
> This is a requirement for ansible modules.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
