On Tue, Sep 17, 2013 at 10:18:29AM -0700, Pedro Roque Marques wrote: > Chip, > A couple of questions... > > On Sep 17, 2013, at 9:54 AM, Chip Childers wrote: > > > I think the best way for this to happen, is for the code to be published > > in a couple of logical patches to reviews.apache.org as a way to get > > community agreement that we should bring it into the codebase. > > > > See: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Review+Board+Guidelines > > > > You should re-base against master first. > > Should we submit the review as feature branch, rather than a patch against > mainline ? > Would this allow an incremental review / comment process... ?
Reviewboard is rather basic on this front. Tag the reviews as belonging to master, so that they are tested against master. We'll just commit to a feature branch when we have dealt with the legal acceptance of the code. > > > > > Once we have the review(s) available, I can start a formal VOTE to > > accept the donation (I assume that this is a large chunk of work), and > > then I can work with you as the sponsor of the donation to the ASF. > > > > Once the IP assignment is handled, we would likely commit the code into a > > feature branch, so that tests could be added (if they aren't in the initial > > donation) before we bring it into master. > > We have an integration test which requires spawning a "mysql" db, initialize > it and then go through the process of creating a zone, etc. > This allows us to test the plugin against the API. The drawback is that this > test takes a bit to spawn the mysql db... > Does anyone have a recipe to run against an in-memory database for testing > purposes ? Prasanna - cc'ed you to see if you have any suggestions on this front. > > > > > Pedro, does this work for you? > Do we need to submit a design doc for the plugin ? Or is the documentation > available at opencontrail.org sufficient ? Ideally, we would have a design document on the wiki that would help everyone understand the implementation. We're not looking for a design doc for Contrail / OpenContrail... we're looking for information about the integration itself. This is both for other devs, tech writers that may choose to help document this, and for users to get a better feel for the feature. AFAICT, I'm not sure if the opencontrail.org site has anything that answers the questions that the CloudStack community needs to have documented... but I may just not have found it. -chip > > > > > -chip > > > > On Tue, Sep 17, 2013 at 05:05:33AM +0000, Animesh Chaturvedi wrote: > >> Pedro > >> > >> We are excited to learn about Contrail's plugin for CloudStack. Let me > >> pass on few links to get you started > >> > >> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/OnBoarding > >> [2] > >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Adding+new+features+and+design+documents > >> > >> > >> It seems the plugin is already under development and would have to go > >> through IP Clearance to get accepted by Apache. The process is described > >> here http://incubator.apache.org/ip-clearance/. > >> > >> > >> Which release are you targeting the Contrail plugin? Apache CloudStack is > >> on a 4 month release cycle and we are just concluding the current release. > >> The next release is ACS 4.3.0 and for which tentative feature freeze date > >> is October 31st. Let us know if you have any questions > >> > >> > >> Thanks > >> Animesh > >> > >> > >> > >>> -----Original Message----- > >>> From: Pedro Roque Marques [mailto:pedro.r.marq...@gmail.com] > >>> Sent: Monday, September 16, 2013 3:12 PM > >>> To: dev@cloudstack.apache.org > >>> Subject: contrail virtual network controller > >>> > >>> Myself and a few others in the Contrail team have been working on a > >>> cloudstack network plugin that interfaces with the contrail VNC > >>> (http://www.opencontrail.org). At the moment the plugin provides > >>> isolated guest networks (and a virtualized "Public" network) as an > >>> overlay that is capable of interconnecting directly with > >>> routers/switches that implement the existing standard for network > >>> virtualization (RFC 4364). > >>> > >>> We would like to contribute this code to CloudStack. We intend to > >>> continue to enhance it in order to add full support for functionality > >>> one would expect out of the EC2 VPN API. > >>> > >>> What is the process to do that ? > >>> > >>> thanks, > >>> Pedro. > >> > >
