The entry for the vpc virtual router provider should have been inserted to the DB for all existing physical networks as a part of the DB upgrade (Upgrade302to40.java, addVpcProvider call). If the vpc provider is missing, it means that the upgrade wasn't performed completely and the DB might miss other stuff.
To add/enable the provider with the APIs, execute the following calls: 1) Add vpc virtual router provider addNetworkServiceProvider&<list of parameters, check the API docs> 2) Add vpc virtual router element createVirtualRouterElement&nspid=<the id of the VPC VR provider created on step #1> 3) Enable the element using API configureVirtualRouterElement&id=<id of vpc vr element>&enabled=true 4) enable the vpc vr provider updateNetworkServiceProvider&id=<id of the physical network vr provider>&state=Enabled -Alena. On 4/22/13 6:43 AM, "Prasanna Santhanam" <t...@apache.org> wrote: > >On Sun, Apr 21, 2013 at 10:55:58PM -0700, Evan McGee wrote: >> Hi Swamy, >> >> Thanks for getting back. cloud.virtual_router_providers is populated >>and has one entry: >> >> id: 1 >> nsp_id: 1 >> uuid: a82918427-80bf-8719-baa5-acdf88a9c026 >> type: VirtualRouter >> enabled: 1 >> removed: NULL >> >> Looks like this is enabled -- should the type be set to >> VirtualRouter? Ran the API call below anyway just to be sure, but >> got back the same result when trying to add a new VPC. > >For VPC the provider is called VpcVirtualRouter. > >-- >Prasanna., > >------------------------ >Powered by BigRock.com > >
