Hi all, I have updated the developer guide wiki page for ALTO[0], it's still in progress but I think we can still benefit from your feedbacks. In this update, some out-dated contents are removed from

Hello Kai Gao and the alto development team: If you've already registered for the Boron Developer Design Forum (DDF) please disregard this email and I look forward to seeing you next Monday. HOWEVER,

Can someone take a look at this and see if we can migrate to maven sites too? -------- Forwarded Message -------- Subject: Re: [release] [documentation] idea for documentation reviewing in Boron Date:

For the record. -------- Forwarded Message -------- Subject: Re: [release] idea for documentation reviewing in Boron Date: Wed, 24 Feb 2016 06:43:17 -0500 From: Colin Dixon <colin@...> To: George Zhao

FYI -------- Forwarded Message -------- Subject: [release] Default tools VM change Date: Tue, 23 Feb 2016 17:27:10 -0800 From: Luis Gomez <ecelgp@...> To: Release (release@...) <release@...>, integrat

Hi ALTO Team, Please take a moment today to address some action items for your project regarding the Beryllium Release. 1. We are missing the Beryllium GO/NOGO vote for your project. https://docs.goog

Guys, please read this article on the style of documentation. -------- Forwarded Message -------- Subject: Re: [release] [documentation] DOCS Release Review Date: Tue, 16 Feb 2016 14:43:02 -0500 From:

Hi Jamo, I found our patch for system test was not still approved. Can you review this patch [1] and tell us if it can be merged or not? If there are any change requests, we will update them as soon a

Hi alto-dev, One of your recent changes caused validate-autorelease to fail build for all projects. The cause is that this patch [1] which was merged without first being rebased since it was submitted

When: Thursday, February 11, 2016 7:30 AM-9:30 AM (UTC-08:00) Pacific Time (US & Canada). Where: IRC #opendaylight-meeting Note: The GMT offset above does not reflect daylight saving time adjustments.

Hi ALTO Team, Please take a moment to update your project RC Status [1]. Your project has the following action items: RC Status [1] * Missing External System Test Status * Missing Experimental Feature

Hi Everyone, Your validate-autorelease job will fail to build if you're one of the projects that still have not yet approved the build with jdk8 patch in Boron. If you're one of the projects listed at

Hi K. Gao (PTL, ALTO) We recently had a discussion concerning the OpenFlow Plugin Designs Conflict and would like your feedback. Would you mind filling out this survey [1] or replying directly to this

Hi Alto, There are actually no tests here. It looks like the skeleton that you might have started to get the infra working, but no tests were ever added. Regards, JamO

ALTO M4 Status 1. Please provide updates on any previously-incomplete items from prior milestone readouts. N/A 2. Has your project achieved API freeze, i.e., all externally accessible APIs [Stable and

Hi Qiaoqiao, I am glad to hear you are trying ALTO. You can post your questions to this mailing list for discussion: alto-dev@.... Please feel free to tell us if you need help. Best, Jensen 2015-11-25

Hi ALTO Team, Please review this patch [1] and sign off with +1 code review. As agreed by the TSC, we will move to JDK8 in Beryllium [2] and your project has not yet migrated to JDK8. Please respond i

Also please keep Harvey in the loop. ODL dlux interface is not useful, use this interface for a proper understand of the layout we have in the showfloor: http://sdn.hep.caltech.edu Each circle shows a

A few more items: - Cam we use Skype (I have Azher already) for more real-time sync up? - ALTO server needs to extract routing information from ODL. The current version allows routing query by ip addr

Hello Kai & Jensen: I sent this to Richard yesterday not realizing that the leadership of the project has changed this past week. The folks at CalTech woking on the Large Hadron Collider are using Ope