Dear colleagues, The ALTO project depends on the projects L2switch, OpenFlowPlugin and OVSDB. We'd like to get the acknowledgement from the projects. Thanks very much! Regards, Kai

ALTO 0. Please provide updates on any previously-incomplete items from prior milestone readouts. N/A 1. Have you completed the project checklist [1]? Yes * (link to a merged patch in gerrit) https://g

ALTO M3 Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes ** If you had any Tentative APIs, have they been moved to Provisional or Dropped? N/A ** If any of your Tentative

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 such that all externally accessible Stable or Pro

L2switch has been converted to blueprint [0], so *-config artifacts are no longer defined. Alto was depending on them. Possible fix for the autorelease build: [1]. But even after that fix, the new val

Vratko, The current patch might do now, at least for Boron. Currently we can work around it but in the long run we may still need to enable reactive routing. Actually we don't care much about ARP pack

Jensen, Xiao and other folks, Please see the e-mail and prepare for migrations ahead of time. Thanks! -------- Forwarded Message -------- Subject: Re: [release] considering documentation migration to

Hi ALTO Team, There are plans to upgrade ietf-inet-types@2010-09-24 and ietf-yang-types@2010-09-24 (RFC 6021) to ietf-inet-types-2013-07-15 and ietf-yang-types@2013-07-15 (RFC 6991) in the Boron relea

Jensen, can you take a look at this? You can download tsdr and use dependency:tree to see what jetty version we/they are using. Ours is 8.1.19. Haven't been able to see theirs at the moment. --------

When using maven to resolve the dependencies of Application Layer Traffic Optimization in eclipse oomph after its installation through its installer I'm getting errors of tool-1.7.0.jar not found. I'm

Hi all, One outcome of this IETF is that ALTO introduces the footprint and capability interface (fci) map, to support the CDNi use case. I feel that this is an important use case and hence may I reque

FYI -------- Forwarded Message -------- Subject: Re: [release] [OpenDaylight TSC] committing to an outline of a Carbon release plan Date: Thu, 28 Jul 2016 16:36:55 -0400 From: Nadeau Thomas <tnadeau@.

Hi alto devs, Your merge job started to fail recently [1]. Please address the issue before it hits the integration distribution. BR/Luis [1] https://jenkins.opendaylight.org/releng/view/Merge-Boron/jo

I think it is a good idea. I will discuss with alto-dev group and try to add this feature into the release plan of OpenDaylight Carbon. @Kai: what do you think about? Best, Jensen

Hi ALTO, We are currently running into distribution size failures [1] where the Boron Common Karaf Distirbution is greater than 512MB. In order to decrease the size of the distribution, we believe the

FYI -------- Forwarded Message -------- Subject: Re: [release] distribution still not good Date: Thu, 4 Aug 2016 15:57:56 -0400 From: Colin Dixon <colin@...> To: Luis Gomez <ecelgp@...> CC: release@..

ALTO Boron M5 Status 1. Please provide updates on any previously-incomplete items from prior milestone readouts. N/A 2. Has your project met code freeze, i.e., only bug fixes are allowed from now on?

Do we have someone to update the documentation? -------- Forwarded Message -------- Subject: [release] [ACTION] projects missing documentation for Boron Date: Thu, 11 Aug 2016 10:45:04 -0400 From: Col

For the ALTO release review Monday morning, I have the following analysis of their upstream CSIT for boron, using the most recent boron job result. please note that I do not know if all delivered feat

Hi K. Gao, J. Jensen Zhang, Y. Richard Yang, and ALTO Team, Please vote GO/NOGO on the spreadsheet below by filling out Column B next to your project name: https://docs.google.com/spreadsheets/d/1zImt