incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hugo Trippaers <>
Subject RE: Nicira integration pre-review
Date Mon, 18 Jun 2012 07:05:27 GMT
Hey David,

Thanks for the feedback, I've modified all license headers in my bits of the code.

The phases we have currently identified together with Nicira are:

1) First integration, L2 networking only and single NVP setup for the entire cloud.
	This means a static configuration for the NVP setup and the possibility to create guest networks
in CloudStack using the NVP solution (create logical switch and logical port attachments).
Source should be ready for production use and pushed upstream to the opensource version of
CloudStack. VIrtualRouter is used for SNAT and all other features.

2) More in depth integration, Use the pluggable resource system to add a Nicira NVP device
to a zone and allow different NVP setups per zone. Use some L3 features like SNAT directly
from the Nicira NVP instead of the VirtualRouter.

3) Everything we don't get to do in the other phases ;-)

So currently we have allocated resources to do phase 1, which is the current patch. My goal
is to finish this patch and get it upstreamed into the CloudStack master branch. When that
is done we'll move to the next phase.



-----Original Message-----
From: David Nalley [] 
Sent: Friday, June 15, 2012 7:34 PM
Cc: Somik Behera (
Subject: Re: Nicira integration pre-review

On Wed, Jun 13, 2012 at 5:51 AM, Hugo Trippaers <> wrote:
> Hey All,
> As some of you know Somik Behera and me have been working on adding 
> Nicira support to CloudStack. We have identified a few phases in the 
> project, where phase one is L2 isolated networking. Attached to this 
> email is a patch that will add Nicira phase 1 integration to 
> CloudStack. We have done internal testing using this patch and now we 
> would like to invite you to have a look as well before we submit this patch for review.
> We are looking for feedback on the integration when the existing 
> modules, we already discussed a few things in a recent meeting with 
> Chiradeep, but real code makes it easier to see how we implemented this.
> Based on the feedback and some pending thoughts about name conventions 
> we will modify the patch and submit it for review.
> Looking forward to your feedback.
> The patch can also be found on GitHub at
> 87848368a0a9399e97ab28


This is awesome. Thanks for letting us have a peak.

A couple of just housekeeping items:

You have license headers that don't match the ASF requirements, you may want to review this:

I am also curious as to what you see the remaining phases of support to be?


View raw message