We are using PingER and PlanetLab landmarks for geolocation in TULIP. PlanetLab landmarks are manually updated with the help of perl script "insert_planetlab.pl" which is under tulip directory /afs/slac.stanford.edu/package/pinger/tulip. This script loops over monthly active hosts in PlanetLab and inserts new one based on thier availability.PingER nodes are updated with the help of automated script "create_sites-xml"(updated by trscrontab job running in pinger@pinger.slac.stanford.edu) which is located under TULIP directory.
We can also update landmarks manually using the following process .
- As it is evident there are some mandatory fields, which are required to make the TULIP work.Before adding you must check that you have everything in point (2a)
- hostName,ipv4Addr,enabled (1 or 0) ,latitude,longitude,serviceInterfaceType(PingER/PlanetLab),tracerouteURL and tulipTier
- Additionaly we can also give city,country,state,institution etc
- Process for making change in database
- Login to tulip database (username and password available in escrow -c iepm iepmacct
- Change the database to tulip by cmd
mysql> use tulip;
- Now insert new records using the following sql cmd; in this instance we are using ipv4Addr = 141.22.213.35; generally ipv4Addr is the primary key but we can also use hostName as an identifier to disable landmarks
insert into landmarks (hostName,ipv4Addr,enabled,latitude,longitude,serviceInterfaceType,tracerouteURL,tulipTier) values ('mars.planetlab.haw-hamburg.de','141.22.213.35','1','53.55','10','PlanetLab','141.22.213.35','1');
- Update Sites.xml so that it can now use the updated landmarks using follwing cmd
create_sites-xml.pl > /afs/slac/www/comp/net/wan-mon/tulip/sites.xml