Gaurav, I have updated the ticket with my comments. Essentially it is a network property , persistent vs non-persistent and VM should not dictate it. Let me know
Thanks, RamG > -----Original Message----- > From: Gaurav Aradhye [mailto:gaurav.arad...@clogeny.com] > Sent: 28 January 2014 16:25 > To: dev@cloudstack.apache.org > Subject: Re: Persistent Networks - Assign VM operation > > I have logged issue > CLOUDSTACK-5964<https://issues.apache.org/jira/browse/CLOUDSTACK- > 5964>for > this. > > Regards, > Gaurav > > > On Mon, Jan 27, 2014 at 2:56 PM, Gaurav Aradhye > <gaurav.arad...@clogeny.com>wrote: > > > Hello all, > > > > According to the Persistent Networks test plan at [1], if we assign a > > virtual machine deployed in a persistent network (in account-1) to a > > different account (say account-2), then a persistent network should > > get created in account-2 with the same network offering which was used > > for the previous network of the virtual machine. > > > > I have observed that in this case, a non persistent isolated network > > is getting created with default isolated network offering in the > > account-2; instead of persistent network. > > > > Please let me know if I am missing something or if there is change in > > test scenario. If not, I will file a bug for this. I have tested this > > on Vmware yet. > > > > 1. > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Persistent+Netw > > orks+without+a+running+VM > > > > Regards, > > Gaurav > >
