This group is locked. No changes can be made to the group while it is locked.
Re: Work with OpenDaylight for SC15 event?
|
Y. Richard Yang
Azher, all, Thanks a lot for the nice demo and the discussions. It is very helpful! The ALTO team had some more internal discussions, based on our discussions last night. Here is an outline: ==== Entities: - Endhost: Each endhost will have a data directory, which hosts the files that it has, for example, file1, file2, file3, ... - File tracker: There is a file tracker which keeps track of the files that each endhost has as a map: <endhost> -> <list of files> - Scheduler: There is a scheduler which accepts transfer tasks and schedules the transfers - ODL SDN controller Processes: - Endhost: There is an agent running on each endhost to monitor the existing files and update the file tracker on the file index; The endhost tracker will also ping each other to get latency and report the results to the ALTO server in the SDN controller; The agent (or a remote command) can start a file transfer. - File tracker: accepts queries on files available at each endhost, and posts to update the file index - Scheduler: Schedule the transfers, where each transfer has the following attributes: client-endpoint, file-name, priority, deadline. In particular, the frontend (or API) has a form to allow others to submit transfer requests; The backend will query the network status and compute the scheduling of transfers. Details of the scheduling backend to schedule a set of transfers. Assume that all the transfers are given in a batch (T1, T2, ... TK) for the demo. - Query File tracker to obtain the replicas of the each data in the batch - Query ALTO to obtain the routing path for each T1(file).replica: path(T1(client), T1(file).replica) - Query ALTO to obtain the path properties such as latency of the routing paths - Conduct scheduling (i.e., replica selection and maximum flow based for deadline and priority), based on estimating TCP throughput (based on TCP throughput formula; the throughput of each flow is inverse proportional to its latency) - Issue transfer commands to the endhosts. It looks like that some of your packages (e.g., MoniLisa) can be used for the preceding. We are looking into. ==== On Tue, Nov 3, 2015 at 5:20 PM, Azher Mughal <azher@...> wrote:
-- ===================================== | Y. Richard Yang <yry@...> | | Professor of Computer Science | ===================================== |
|
|