Fabric nodes Network access

We are still in the construction phase of FABRIC.  Although there are a plans for 30+ sites, currently only 10 of them are deployed on the production testbed.   Many more sites are being delivered and/or configured. These will be released to the users as soon as they are ready.  There will eventually be a site at Clemson but there are no plans for one at UCLA. There are plans for a site in Los Angeles but not at UCLA.

Regarding your question about latency: Every site has a management network that allows you to ssh to your VMs and pull software/data to them.  This network is intended to be used for configuration of experiments, it is not intended for experimentation.  This management network is connected to the public Internet (although protected by a bastion host).  If you ping “clemson.edu” or “ucla.edu” from your VMs, you are not pinging anything inside FABRIC.  Instead, you are pinging a host owned and managed by a university and you are sending traffic across the management network and the public Internet.

If you want to test latency across FABRIC, you will need to setup VMs at multiple FABRIC sites and ping between them over a network you setup within FABRIC.  Note that on FABRIC you can deploy L2 or L3 networks and might see different latency depending on how you design your experiment.  With L2 networks, you could even design multiple networks with different paths between the same pair of sites. You could even experiment with dynamically choosing between these paths to optimize your application.

• This reply was modified 2 years, 3 months ago by Paul Ruth.
• This reply was modified 2 years, 3 months ago by Paul Ruth.
• This reply was modified 2 years, 3 months ago by Paul Ruth.