CS290I -- Project 2 Machine List

To query the NWSSlapd for forecasts on a particular machine (say bird.cs.ucsb.edu) you can issue the following command: 
ldapsearch -x -h dreadnought.cs.ucsb.edu -p 3389 -b "o=data,service=nws,o=grid" "forecast=*bird*"

The command 

ldapsearch -x -h dreadnought.cs.ucsb.edu -p 3389 -b "o=data,service=nws,o=grid" "forecast=*"
will return all of the information the server has at its disposal. WARNING: global searches are expensive. Do not make them more than once every 60 seconds. You can make individual searches (one at a time) as often as you like.

The NWSlapd provides a special mechanism for retrieving TCP bandwidth and latency measurements for a set of machines. It can provide what's called a VO-grid or virtual organization Grid. A VO-grid is simply a set of machines which someone has designated. Once the VO-grid has been set up, a single query will retrieve the N^2 forecasts for bandwidth (and/or latency) between each and every host.

We have of course set up a VO-grid for your use in the class. Our VO-grid contains all 43 machines in the class pool. You can query it like this: 

ldapsearch -x -H ldap://dreadnought.cs.ucsb.edu:3389 -b vo-grid=classpool,service=nws,o=grid

You'll notice that the returned objects have two new attributes called index0 and index1. 

# bird.cs.ucsb.edu:8065.latencyTcp.satchmo.cs.ucsb.edu:8065, data, NWS, Grid
dn: forecast=bird.cs.ucsb.edu:8065.latencyTcp.satchmo.cs.ucsb.edu:8065,o=data,
 service=NWS,o=Grid
objectClass: top
objectClass: service
objectClass: GridForecast
forecast: bird.cs.ucsb.edu:8065.latencyTcp.satchmo.cs.ucsb.edu:8065
index0: 42
index1: 41
timestamp: 1051169845
value: 2.284000
mse-forecast: 1.942242
mse-error: 0.047996
mae-forecast: 1.942242
mae-error: 0.351731

You can think of these as indices for the two hosts in a N by N matrix of forecasts. In your application program you could use these indices to build such a matrix of forecasts.

For this project, we will be configuring machines into NWSlapd from the following list. WARNING: this list is the maximal list. You should NOT depend on all of these machines being available when you run. Instead, you should query NWSlapd and base your decisions on what is returned.

There are essentially four categories of machines that you currently have available to you: 360 MHz SPARCS, 500 MHZ SPARCs, 850 MHZ x386s, and 1470 MHz x386s. The SPARCs run Solaris{2.7,2.8} and the x386 machines run Linux.

The 500 Mhz SPARC / Solaris 2.8 machines are 

ella.cs.ucsb.edu
bird.cs.ucsb.edu
joplin.cs.ucsb.edu
nat.cs.ucsb.edu
dorsey.cs.ucsb.edu

The 360 Mhz SPARC / Solaris 2.7 machines are 

blind.cs.ucsb.edu
dizzy.cs.ucsb.edu
satchmo.cs.ucsb.edu
cab.cs.ucsb.edu

The 1470 Mhz i686 / Linux 2.4 machines are 

zonker.cs.ucsb.edu
pinky.cs.ucsb.edu
wacko.cs.ucsb.edu
bart.cs.ucsb.edu
speed.cs.ucsb.edu
racerx.cs.ucsb.edu
marvin.cs.ucsb.edu
booboo.cs.ucsb.edu
scooby.cs.ucsb.edu
natasha.cs.ucsb.edu
bullwinkle.cs.ucsb.edu
whiley.cs.ucsb.edu
miles.cs.ucsb.edu
fats.cs.ucsb.edu
didley.cs.ucsb.edu
chubby.cs.ucsb.edu
brubeck.cs.ucsb.edu
duke.cs.ucsb.edu

The 850 Mhz i686 / Linux 2.4 machines are 

hobbes.cs.ucsb.edu
blondie.cs.ucsb.edu
dagwood.cs.ucsb.edu
shaggy.cs.ucsb.edu
brain.cs.ucsb.edu
linus.cs.ucsb.edu
snoopy.cs.ucsb.edu
taz.cs.ucsb.edu
eeyore.cs.ucsb.edu
goofy.cs.ucsb.edu
pluto.cs.ucsb.edu
mickey.cs.ucsb.edu
boris.cs.ucsb.edu
rocky.cs.ucsb.edu
dudley.cs.ucsb.edu
marge.cs.ucsb.edu