Re: About testing of OVS Tunnel Manager, Fail on create new instance

2013-05-20 Thread Chiradeep Vittal
ep to specify the vnet range in the create >advanced >zone wizard. > >Is it have some preprocess before specify this range ? > >-原始郵件- >From: Chiradeep Vittal >Sent: Saturday, May 18, 2013 12:45 AM >To: Garnet Tang ; dev@cloudstack.apache.org >Subject: Re: A

Re: About testing of OVS Tunnel Manager, Fail on create new instance

2013-05-19 Thread 錦為
of OVS Tunnel Manager, Fail on create new instance You have to specify this range in the wizard On 5/16/13 8:06 PM, "Garnet Tang" wrote: Hi Chiradeep, Thanks for your suggestion. When I configures "sdn.ovs.controller" to "true", I do not specify the "vne

Re: About testing of OVS Tunnel Manager, Fail on create new instance

2013-05-17 Thread Chiradeep Vittal
st network in the create advanced zone wizard. > >And, the field "vnet" is null in database table "physical_network". > >How to specify this parameters? > >------ >From: "Chiradeep Vittal" >Sent: Friday,

Re: About testing of OVS Tunnel Manager, Fail on create new instance

2013-05-16 Thread 錦為
cal_network". How to specify this parameters? -- From: "Chiradeep Vittal" Sent: Friday, May 17, 2013 1:18 AM To: Cc: Subject: Re: About testing of OVS Tunnel Manager, Fail on create new instance Did you specify the guest netw

Re: About testing of OVS Tunnel Manager, Fail on create new instance

2013-05-16 Thread Chiradeep Vittal
Did you specify the guest network "vlan" range in the create zone wizard? The exception is complaining that there are no virtual network ids available. Vnet ids are populated in the op_dc_vnet_alloc table when the updatePhysicalNetwork api is called. On 5/16/13 8:07 AM, "錦為" wrote: >Hi all, >Ac