Hello Richard,

FDT is easy to use :

For the server :   java -jar fdt.jar

for client   :   java -jar fdt.jar  -P number_of_streams -nettest -c server_name

This is run very much like iperf


We use Monalisa for monitoring. It is not necessary to have it in a VM

Concerning the path computation,  one possibility is to get the maximum
throughput . Is any ODL module that can do this ?

Best Regards,
ioji

On 11/5/2015 5:04 PM, Y. Richard Yang wrote:

Hello Losif,

On Thu, Nov 5, 2015 at 10:44 AM, Iosif Legrand <Iosif.Legrand@...>
wrote:

Hello Richard ,

My skype id is :ioji88

I sent you a contact request.

For file transfer we will use FDT


https://urldefense.proofpoint.com/v2/url?u=http-3A__monalisa.cern.ch_FDT_&d=AwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=I0Y2RfbcFQooIrPgnj7j-YB5mUuA_0xHQNTiHBm5Df0&s=kR5SQfbS9X0H8Oao2xH_DDRLs9v2h9HBtRdu_IYWFCU&e=
It also has the functionality of iperf (memory tto memory )

Thanks a lot. Let us take a look on how to use FDT.

I saw that MoniLisa is running on the controller VM. Will it be used in the
demo?

Can you use in ALTO the traffic info from the connectors (ports)
  and per flows to  use the best path in terms of available bandwidth ?

The port stat provides traffic volumes (and if we pull frequent enough, we
can have reasonable rate estimate; capacity minus this will give available
bw). ALTO assumes that path is computed by other modules, because this
function should be configured by users such as involving SFC, GBP or not...
For this demo, what is the Path Computation approach? We can work together
to set up the path computation module and then ALTO can help to pick the
best data source. Please let us know.

Thanks a lot!
Richard

Thanks a best Regards,
ioji


On 11/5/2015 4:00 PM, Y. Richard Yang wrote:

A few more items:
- Cam we use Skype (I have Azher already) for more real-time sync up?

- ALTO server needs to extract routing information from ODL. The current
version allows routing query by ip addresses only---transport ports
work-in-progress. My understanding is that you will use PCE for path
computation:
1. Your UI allows a user to pick a src-dst pair (already done);
2. Your backend can enumerate all paths for the pair (already done);
3.1 Your backend calls PCE in ODL to compute a path (work in progress)?
3.2. Your backend install the path
Could you keep us updated on your status?

- ALTO can aggregate network information sources beyond ODL modules (e.g.,
perfSONAR) to provide unified info. Any opinion on how you want to collect
such info (OpenFlow flow stat does not provide latency)?

- Which software do you use in the demo for file transfer?  iperf, or
another?

Thanks a lot!
Richard

On Thursday, November 5, 2015, Y. Richard Yang <yry@...
<javascript:_e(%7B%7D,'cvml','yry@...');>> wrote:

Hi Losif,

We will be happy to do so.

Azher: We need access to your installation of ODL so that we can add the
ALTO module. To be safer, so that our addition will not break your
existing
ODL, how about you tell us the extract setting of ODL you installed?
We will create a VM, first do the exactly same install, test, and then
add
ALTO and other needed modules, and then test. In other words, there will
be
two VMs running. One is your current working VM, and the other is the VM
with extension. We will always have a backup. How dies the proceeding
sound?

Thanks!
Richard

On Thursday, November 5, 2015, Iosif Legrand <Iosif.Legrand@...>
wrote:

Hello Richard,

To follow-up our discussion about running ALTO services
at SC15, I would like to ask you and your team if you can
help  to correctly setup ALTO on our test-bed controller at
Caltech and than to try to use it in a quite similar set-up as for the
SC15.
Azher will help to make   access accounts to our controller.


Thank you very much,

Best Regards,
Iosif

--
Richard