...
Name | Null? | Data Type | Use |
---|---|---|---|
NODENAME | NOT NULL | VARCHAR2(100) | DNS host name |
IPADDRESS |
| VARCHAR2(15) | IPv4 address |
SITENAME |
| VARCHAR2(100) | Domain name of the node |
NICKNAME |
| VARCHAR2(35) | Abstraction of the hostname with the TLD first 1 |
FULLNAME |
| VARCHAR2(100) | Human-friendly description of the node/site |
LOCATION |
| VARCHAR2(100) | City and/or State/Province/Region for node 2 |
COUNTRY |
| VARCHAR2(100) | Country for node |
CONTINENT |
| VARCHAR2(100) | Continent or region where node is thought to be located 3 |
LATANDLONG |
| VARCHAR2(25) | Latitude and longitude of node |
PROJECTTYPE |
| VARCHAR2(10) | Flags describing how nodes are used 4 |
PINGSERVER |
| VARCHAR2(100) | URL for requesting a ping from this node to another 5 |
TRACESERVER |
| VARCHAR2(100) | URL for requesting a traceroute from this node to another 5 |
DATASERVER |
| VARCHAR2(100) | URL for retrieving PingER data from this node 5 |
URL |
| VARCHAR2(100) | URL for the home page for the institution running the node |
GMT |
| VARCHAR2(10) | Node's time offset from GMT, not used |
COMMENTS |
| VARCHAR2(4000) | Comments and notes on when and how the node's record was last updated 6 |
APP_USER |
| VARCHAR2(20) | Windows user name of the last user to edit the node's record through the UI |
CONTACTS |
| VARCHAR2(100) | Name and email address(es) of the node's maintainer(s) |
PING_SIZE |
| NUMBER | Size of pings to be sent to the node - only controls SLAC's PingER install |
...
- EDU.SLAC.STANFORD.N3 - third node at SLAC, hostname pinger.slac.stanford.edu
- CH.CERN.N2 - second node at CERN, hostname wanmoninst1.cern.ch
- AO.UCAN.EDU.N1 - first node at the Catholic University of in Angola, hostname www.ucan.edu
...
Inside the UI, the country and continent (region) are set and restricted to a pop-up list of values. This The pop-up list is actually based on values already existing in the NODEDETAILS table in those two fields. When adding a node in a country not previously used, the node can either be completely created through a SQL INSERT statement entered directly into the database (via SQLPlus or another tool); or all but the country and region/continent can be entered, the record can be saved, and then a SQL UPDATE statement can be used to add the new country and continent, similar to the following:
Code Block |
---|
update nodedetails set country = 'United States, continent = 'North America'
where nodename = 'EDU.SLAC.STANFORD.N3'
|
a separate table called COUNTRY. New countries can be added to the list by creating new rows in the COUNTRY table with SQL INSERT statements. Example:
Code Block | ||||
---|---|---|---|---|
| ||||
insert int country (country_id, country, continent, tld)
values (country_seq.nextval, 'Bermuda', 'Latin America', 'bm')
|
The COUNTRY table is not used except by the list of values in the UI. Note that if a country name needs to be changed or if a country was placed in the wrong region, it must be updated on all the nodes in the NODEDETAILS table as well as on the COUNTRY tableIt may be necessary to exit and re-launch the UI in order to get the new country and continent to appear in the list of values.