Hi Xin, Good discussion. Suppose the admin issues alto:delete (btw, I found the verb destroy too violent, so I, as you, will use delete). I assume that then the network will disappear. This means that

Hi Tony, We are going down the path of trying augment (based on the cost-mode: numerical vs ordinal vs path-vector vs calendar vs policy). We will keep you updated. If you have new suggestions, please

Hi all, This is an update of our M4 status: 1) API freeze achieved. (All externally accessible APIs [Stable and Provisional] may not be modified.) Yes 2) Document word counts for each documents:

Hi all, We haven’t decided how to handle anyxml issue in yang model. And here is my idea. We use augment instead of changing anyxml into string. The backgroud is though cost has multiple structures

Here is a simple test on if a command belongs to karaf console: can it apply to a large number of features. For example, bundle:, feature: ... can be used by others (e.g., sfc, l2switch), but alto:

On 16/04/15 13:04, Y. Richard Yang wrote: Hi Kai, Good work! Here are some quick initial feedback:

Hi Kai, Good work! Here are some quick initial feedback: - In the long run, alto:* should not be karaf commands. The CLI should be a standard alone admin client that manages the alto info at a server.

Hi all, Yesterday I was asked to give a brief description about my understanding of the design and here is the response. A deployment scenario through the command

Dear team, I added the initial version due to the feature template requirement:https://wiki.opendaylight.org/view/ALTO:Lithium_User_Facing_Features I will add more tomorrow. Including the documents

Dear team, I am having some second thought on the alto-manager design. This is triggered when I was (1) thinking about the implications of providing the alto:* scope in the karaf console, and (2)

Issues that we may face as well. For those of us who are not on slacks: Here is a summary on alto: commands. There are 4 design considerations: 1. The design is to be consistent with karaf

Hi, still trying to figure out other possibilites for you how to model cost-maps and do not loose exact type information. Tony From: wangxin [mailto:xinwang2014@...] Sent: Tuesday, April 14,

Hi Richard, I didn’t understand if alto-manager deletes alto-hosttracker-generated data (i think delete is only action it can do), how alto-hosttracker reacts? it stops listening to l2switch and

I have submitted another review that merges the work of Li into the latest master branch. https://git.opendaylight.org/gerrit/#/c/18335/ On 15/04/15 18:45, Y. Richard Yang

Dear Luis, Thanks for doing the check. We updated ALTO and integration: https://git.opendaylight.org/gerrit/#/c/18310/ Could you please take a look again at ALTO and let us know if you see any issues?

Wonderful progress, Kai & Xin! Could you please approve the alto patches? Thanks! Richard -- Richard

I have cleaned up the build enviroment, you can review it at https://git.opendaylight.org/gerrit/18320

I have passed the integration test and submitted a review. https://git.opendaylight.org/gerrit/18309 for alto https://git.opendaylight.org/gerrit/18310 for integration

Dear team, Some of us (Kai and Xin L.) made some good progress this evening to clean up the build environment. If Xin L. can finish the remaining items, we can focus on the design issues during the

Just in case not everyone subscribed to release... ---------- Forwarded message ---------- From: George Zhao <George.Y.Zhao@...> Date: Monday, April 13, 2015 Subject: [release] M5 status template -