Hello, You receive this email because your project hasn’t reported RC0 test status, please take time to do so. RC0 can be downloaded: https://nexus.opendaylight.org/content/repositories/automatedweekl

As far as I can tell there have been four submitted patches for ALTO docs: https://git.opendaylight.org/gerrit/#/c/18389/ https://git.opendaylight.org/gerrit/#/c/20475/ https://git.opendaylight.org/ge

George, Thanks for the note. Kai and I will work with Robert to merge it. Thanks! Richard _____________________________

Wendy, Good proposal! Two comments: 1. I liked that the interop is for a setting that is close to real-life deployment. In particular, my understanding of the proposal is that the interop should leave

Hi Richard, Vijay, Could you take care of the two patches. Thanks, George

FYI ---------- Forwarded message ---------- From: Thanh Ha <thanh.ha@...> Date: 29 May 2015 at 13:51 Subject: Lithium RC0 Status To: "release@..." <release@...> Hi Everyone, A few folks have pinged me

Hi all, I’m going to write the documentation of ALTO within two or three days and we would be ready for M5. After the CoNEXT we may get back to alto-0.2.0, and I’d like to share some thoughts on the c

1. Code Freeze (bug fixes only from here as defined above) Yes 2. Stability branch, i.e., stable/lithium, must be cut and local project versions bumped on master to avoid overwriting lithium SNAPSHOTS

1. Code Freeze (bug fixes only from here as defined above) Yes 2. Stability branch, i.e., stable/lithium, must be cut and local project versions bumped on master to avoid overwriting lithium SNAPSHOTS

Dear Christian, It is great to hear about your development. Regarding open source implementation, some of us are developing an open source ALTO server in OpenDayLight. We are slightly behind the sched

Dear team, The previous draft doc is under review. ---------- Forwarded message ---------- From: Gerrit Code Review <gerrit@...> Date: Wed, Apr 22, 2015 at 3:26 PM Subject: Change in docs[master]: Doc

Dear team, My apologies for being quiet in the last few days. I did check and saw that you guys are making good process! Thank you so much! I greatly appreciate it! Tomorrow (May 14) is the M5 cutoff

Dear team, Here is the template. Richard ---------- Forwarded message ---------- From: George Zhao <George.Y.Zhao@...> Date: Monday, May 11, 2015 Subject: [release] [Reminder for offset 2 projects] M5

Hi folks, I am suspecting there are some constraints on AddressGroup which could most include one IPV4 and(or) one IPV6. The processing code in RFC2ModelEndpointAddressGroupCoventer.java seems only co

Dear all That is my misunderstanding. I have posted my previous question here(https://ask.opendaylight.org/question/3617/there-should-be-some-improvement-about-the-auto-generated-codes-from-yangtools/

Hi Kai, Good proposal. I’ll try to find who is responsible for that. There is another project(https://wiki.opendaylight.org/view/YANG_Tools:Main), may be the committers know the clue. BR Robert 发件人: G

Hi folks, I am reading the code under ALTO@ODL. And here are my two comments. 1:File named ‘AltoProviderImplBuilder’under alto-provider/……./modules/module/configuration :in function named 'toString',f

Yes! It is really helpful! Thanks a lot! Xiao Lin ------------------ 原始邮件 ------------------ 发件人: Wendy Roome <wendy@...> 发送时间: 2015年04月30日 21:50 收件人: <linxiao9292@...> <linxiao9292@...> 抄送: alto-dev@

Project leads in the following projects, could you please provide your documentation locations: AAA ALTO Controller, D4A DIDM dLux L2switch SDNi SNMP SNMP4SDN SNBI Yangtools Please use TTP project for

Hi all, When ALTO server provide endpoint cost between h1 and h2 , is the path between h1 and h2 given ? For example, before ALTO server provides endpoint cost, it knows that h1 can connect to h2 in p