Hi Kishan, Chiradeep, Thanks for the info. We are currently prototyping VPC functionality with our plugin. We are getting around this in the short term by changing the various dependencies on VPCVirtualRouter with some logic that will loop through the Elements and pick the first VPC plugin available, which we make sure is ours.
Any idea when you expect to have this in? I would also be very interested in knowing implementation details, if you have decided on any yet. thanks, Joe On Mon, Feb 4, 2013 at 5:29 PM, Kishan Kavala <kishan.kav...@citrix.com>wrote: > Yes, it needs fixing. I'm planning to make it pluggable as part of > ExternalDevice support for VPC. > https://issues.apache.org/jira/browse/CLOUDSTACK-749 > > > > -----Original Message----- > > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] > > Sent: Monday, 4 February 2013 8:28 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: VPC Functionality Not Pluggable > > > > Looks like a shortcut. Definitely needs fixing > > > > On 1/31/13 6:34 PM, "Mills, Joseph" <j...@midokura.jp> wrote: > > > > >I was looking through the code that handles creating VPCs and noticed > > >that it did not seem pluggable at the moment. For example, there are a > > >few places where the assumption is made that the only possible Vpc > > >element provider is VPCVirtualRouter: > > > > > > protected VpcProvider getVpcElement() { > > > > > > > > > if (vpcElement == null) { > > > > > > > > > vpcElement = > > >((VpcProvider)_ntwkMgr.getElementImplementingProvider(Provider.VPCV > > irtu > > >alR > > >outer.getName())); > > > > > > > > > } > > > > > > > > > > > > > > > > > > if (vpcElement == null) { > > > > > > > > > throw new CloudRuntimeException("Failed to initialize vpc > > >element"); > > > > > > } > > > > > > > > > > > > > > > > > > return vpcElement; > > > > > > > > > } > > > > > >Are there any plans to make the Vpc functionality in cloudstack > pluggable? > > >Has anyone scoped out what the required changes would be? > > > > > >thanks, > > >Joe > >
