ALTO Boron M5 Status 1. Please provide updates on any previously-incomplete items from prior milestone readouts. N/A 2.

FYI -------- Forwarded Message -------- Subject: Re: [release] distribution still not good

Gao Kai <gaok12@...> wrote: It may be worth checking whether the version of Jetty bundled with Karaf is suitable (8.1.15.v20140411 as of Karaf 3.0.6, available as the "jetty" feature

Hello An Ho, I replied to the thread in the release mailing list [1] about the issue. We found that tsdr alone uses two different Jetty versions,

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

I agree, but to proceed we need to have someone investigate the related documents, especially how to gather the information. Also, do we

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

Okay. Thank you very much! Jensen

Looks like an Intermittent issue. I just ran a remerge and it passed. https://jenkins.opendaylight.org/releng/job/alto-merge-boron/50/ In the future if you see a connection refused to Nexus it's

Hi Thanh, Thanks for your help. It is indeed a missing license header issue. I think this should fix it: https://git.opendaylight.org/gerrit/#/c/42716/ But when we try to merge this patch, the merge

Looks like a file is missing license headers. This should fix it: https://git.opendaylight.org/gerrit/42870 Regards, Thanh

Hi alto devs, Your merge job started to fail recently [1]. Please address the issue before it hits the integration distribution. BR/Luis [1]

FYI -------- Forwarded Message -------- Subject: Re: [release] [OpenDaylight TSC] committing to an outline of a

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

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

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

An Ho, Copy that. Thanks! Regards, Kai On 12/07/16 01:55, An Ho wrote:

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

Jensen, Xiao and other folks, Please see the e-mail and prepare for migrations ahead of time. Thanks! -------- Forwarded Message

Thanh, I've contacted the committers to accept the patch. It should be done within minutes. Sorry for the trouble. Regards, Kai On