Now I see my fallacy. Thanks again for clarification. Never mind. René
On 03/11/2017 10:06 AM, Remi Bergsma wrote: > Hi René, > > From UI, you navigate to any VM, click Nics, then use “Add Network to VM” > button. > > You’re basically sending the addNicToVirtualMachine API call. > > Regards, Remi > > > On 11/03/2017, 09:57, "Rene Moser" <m...@renemoser.net> wrote: > > Hi Remi > > Perfect! Thanks for the clarification. I still wonder how to do it but > that is another story :) > > René > > On 03/11/2017 08:40 AM, Remi Bergsma wrote: > > Hi René, > > > > I just posted some screenshots on the PR that show a VM can be part of > more than one VPC (mail wouldn’t allow screenshots) so please have a look at > Github. > > > > Regards, Remi > > > > On 10/03/2017, 17:52, "Rene Moser" <m...@renemoser.net> wrote: > > > > Hi > > > > I created https://github.com/apache/cloudstack/pull/1999 to return > the > > vpcid the VM belongs to in listVirtualMachines- > > > > I need this for the cloudstack ansible modules to fully determine > VMs > > uniquely as listVirtualMachines returns all VMs (non-vpc and vpc) > and > > they can be named identically. > > > > (I have currently implemented a workaround to go though > listnetworks for > > every VM, but this is a very expensive operation, and that is why I > > wanted to solve it by returning the VPC id on the VM level.) > > > > I had a discussion with ustcweizhou which says that a VM can be > part of > > multiple VPCs and therefore it would not make sense to add vpcid to > the > > response. I disagree, a VM can not be in different VPCs. > > > > Can anyone join the discussion? Is it possible a VM can be in > different > > VPCs? > > > > Thanks for the clarification > > > > René > > > > > >
