OK people, you heard Andrew, have any of you any objection on adding Moiz and Huang to the list of committers for Integration project? Thanks Luis

+1 for adding them.

+1!

No objections.

No objections.

+1 Ed

+1 for both. Great additions. Regards, Swaraj > From: luis.gomez@... > To: eaw@...; carol.sanders@...; swarajv@...; punal.patel@...; guangpeng.li@...; yangbaohua@...; moraja@...; huangdenghui@... >

Greetings folks, So last week there was a request for new VMs for doing black box testing. I understand we're talking about 5 systems. What I've seen is the following: VM1: Test management

Hi Andrew, I will discuss your questions more in detail with Carol but so far this is my idea for the VMs networking: 1) IP interfaces: The VMs need 1 IP interface that can be used for both:

I agree with all items mentioned with additional consideration: I like to have a separate management interface on each VM than what I'm using for test traffic. Is it possible to have two or three

Hi Carol, That makes sense to me too, so we can have 2 interfaces per VM: - Test traffic interface: to connect to other test VM. This is on a private subnet shared only by the VMs and does not need

Hi Carol, Today I learned through the TWS call that people from ON.LAB (http://onlab.us) are developing another kind (OS based) of SDN controller called ONOS. It happens that they use a test

Guys, I had promised distributions for the editions in integration by Monday. I hit some road bumps around artifacts being available in nexus (which I'm working with projects to fix). Or to put it

Yes I will take a look today. Thanks, Carol

Thanks very much Ed.

Yes Luis, I was present at the TWS call as well. ON.LAB Preso was awesome. https://wiki.opendaylight.org/images/d/dc/ONOS_ODL_TechTalkv7.pptx the webx recording link is at

I would love to be able to demo results of some of our test way On Labs did graphically. It’s probably too much to implement for our current milestone dates but we could perhaps plan to

As part of putting together the release vehicles for ODL (Base, Virtualization, Service Provider) I am constructing distribution directories for each flavor in the integration project. When I

I realized when trying to build your manager/commons that it suffers from an issue around the use of <configLocation> ${project.parent.basedir}/checkstyle.xml

Guys, Right now there are no artifacts for groupid org.opendaylight.defense4all innexus.opendaylight.org, which means I can't include them in the Release Vehicle (what we will actually be releasing)