Introduction

Currently, the gathering of data from the MAs is initiated by the SLAC end.

• However, access to the Beijing MA run by Guangzhou is not allowed. 
• Since the MAs from the PingER Android project do not want to have to run a web server, they need a proxy to copy their data to. This proxy, in turn, has to be accessible from SLAC.

Possible solution

Initially, this is proposed for the Beijing MA.

Since we cannot initiate the gathering from SLAC, a possibility might be to use the anonymous ftp service at SLAC (see https://www.slac.stanford.edu/comp/unix/ftp.html).

1. In this case, the MA (e.g. a script initiated at the Beijing MA and run at Beijing by say user Ann who does not have an account at SLAC) would daily run a script (as a cronjob) to use the incoming anonymous FTP at SLAC to store the day's data at SLAC.

2. Then it would be necessary to move the data from the anonymous FTP to:

/nfs/slac/g/net/pinger/pingerdata/hep/data/<host>/ping-<YYYY>-<MM>-<DD>.txt.gz
e.g.
/nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2018-06-04.txt.gz
/nfs/slac/g/net/pinger/pingerdata/hep/data/pingergzhu.edu.cn/ping-2018-06-04.txt.gz

See https://confluence.slac.stanford.edu/display/IEPM/PingER+data+flow+at+SLAC for the data flow. It might be possible to modify the current gathering script (getdata.pl) to add step 2 support (i.e. gather the data from anonymous ftp that is basically acting as a proxy). This would be done via a script run at SLAC under a SLAC account (e.g. Dan). This might be interesting since it also could be extended and a step to providing support for the Android PingER project at Amity in Delhi, India which also needs a proxy.

This would need to be automated by cron scripts.