...
Attendees
Invitees:
Wajahat Hussain+ (SEECS), Saqib+ (GZHU); Johari? (UNIMAS); Adib? (UUM); Fizi Jalil (MYREN); DrDr. Charnsak Srisawatsakul? (Ubru)?, Les+, Bebo+, Umar
+ Confirmed attendance
...
- Saqib points out: "Normally, on Friday at 12 noon, I am out of the lab and my mobile internet connection is not good to participate in the skype meeting. For the next time, is it possible for all to change the meeting day from Thursday to Wednesday according to Pacific time?"
Amity (Updated 8/6/2018)
- Amity MA is unreliable so using it for a case study does not appear fruitful.
- The Android version of the PingER MA, is described with comments at ePingER on Android Native - Amity project (this a proposal/description from Aayush Jain)
- It describes a multipurpose, stand-alone device that can be widely distributed, something that we have brainstormed about for a long time.
Bebo mentioned it to Topher and he feels that their app (when completed and vetted by his team) could easily be installed as a default service on his rainforest monitors (certainly future ones, not devices already in place). Merging the service data that he already collects with that unique to PingER has the potential to lead to some interesting results.
Bebo asks: should we try to increase our communication with Amity and do we have faith that they would follow through?
How should we proceed?
We agreed to request Amity to share the App and instructions with us; we will look at installing on a jailbroken Android phone at the San Francisco end and try it out.
Also encourage them to put together a paper.
Also August 16th and again September 3rd proposed a meeting between: Bebo, Umar and Les. and the Amity folks. No response
...
Need to add Umar Kalim to http://pinger.unimas.my/pinger/contact.php. From the 7/5/2018 meeting: Johari can't ssh into the server so he will go to it on Monday. He will also upload the new UNIMAS PingER website next week.
...
- 121.52.146.180 (kohat.edu.pk) down since Nov 22/2017. Wajahat recommends continuing at least until the new student is up to speed (3/8/2018). No data available 3/24/2018.
- cae.seecs.edu.pk last time we were able to gather any data was February 27th.
- pinger-ncp.ncp.edu.pk pings but can't gather data 8/11/2017 and 9/16/2017. Contacted. Pings but can't gather data 10/24/2017. They are in the process of restoring 1/17/2018. Still down February 28, 2018, await new student. (3/8/2018). No data 3/24/2018. Still down 8/6/2018. It has been Disabled.
- pinger.isra.edu.pk unable to gather data since 3/6/2018, also does not ping.
- Wajahat says they will get these nodes up. These have been good nodes. They just need the weekly push. NUST will push them soon. No update 8/9/2018.
...
- Looking into moving PingER to a "blockchain" database good for decentralizing distribution of data. Monitoring sites would then be able to write to a distributed ledger. This would change the architecture to a more peer to peer architecture. It helps with continuity of PingER since reduces dependence on a single site (SLAC). See BlockChain in Future PingER Projects. Bebo sent several references to Saqib who has looked at them. We could start with real-time data without including the whole archive, i.e. in parallel to the continued centrally managed archive. It would be a private Blockchain and hence not be as compute intensive as a public blockchain.
- There was a meeting to discuss blockchain possibilities, see 20180709 PingER Meeting on Blockchains.
- Bebo's impression is that Saqib will lead in putting the ides in his paper into practice. Saqib will need some students. Saqib is OK with this. He has 2 masters students but they are working in different areas. Maybe NUST can assist with this.Saqib's partner gave a talk/paper on work so far at the New York meeting on July 31st. The talk went fine but there were not many comment/questions.
- Saqib is pursuing PingER and Blockchain. He is looking at different references shared by Prof. Bebo and the implementation details using Hyperledger Fabric. Saqib is looking at making a test implementation. The blocksize will be 2MB-10MB. It does not appear to be computationally expensive. He will start testing with Internet of Thinggs Things measurements such as humidity and temperature
- There was a discussion on the use of DataBases and whether they could be avoided by caches. Hyperlogic keys are not in an SQL DB, basically, it appears like a cache. there was a question whether a 10MB block would be adequate for PingER. Foe For example, PingER from SLAC has about 700+ targets, the measurements are each 30 mins (48/day) and for pings of 100B and 1000 Bytes i.e. 2*48*700 measurements and each measurement is ~ 140Bytes, so a days day's sets of measurements from just SLAC is ~ 10MBytes. We could choose to ignore the 1000Byte pings which would reduce it to ~ 5MBytes/day. The latency of retrieving a block is proportional to the block size. Things will be clearer after the test set up is in use.
...