Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Date: Fri, 1 Feb 2013 11:34:06 +0900
Message-ID: 
 <CAHco2YUstdZHoYtnf4zjvQ4sSeiqbbAcAT5fZtU_Db=3KWTVhA@mail.gmail.com>
Subject: VPC Functionality Not Pluggable
From: "Mills, Joseph" <joe@midokura.jp>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b6d8672cefc4e04d4a093c4

--047d7b6d8672cefc4e04d4a093c4
Content-Type: text/plain; charset=ISO-8859-1

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.VPCVirtualRouter.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

--047d7b6d8672cefc4e04d4a093c4--