Changes between Version 13 and Version 14 of ContainmentInSeattle

Changes between Version 13 and Version 14 of ContainmentInSeattle

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 13 and Version 14 of ContainmentInSeattle

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 13 and Version 14 of ContainmentInSeattle

Show
Ignore:
Timestamp:
12/20/09 13:29:11 (10 years ago)
Author:
cosminb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContainmentInSeattle

    v13 v14  
    11= Containing Node Communication In Seattle = 
    2 Please see attached paper for information about Containment in the Seattle Testbed. 
    3  
    4 server and experiment start details coming soon... 
     2Please see attached paper for overview and detailed explanation about Containment in the Seattle Testbed. 
    53 
    64== Building and Configuring == 
     
    14124) Copy 'restrictions.cnc' into the test directory if you are planning to run the Seattle Node Directory Service (cncStandaloneServer.repy is used to run this service). 
    1513 
    16 5) If you are planning to run the Seattle Node Directory Service, copy testdir to every machine in your farm. 
     145) If you are planning to run the Seattle Node Directory Service, run: 
     15python repypp.py cncStandaloneServer.repy cncStandaloneServer.py 
     16 
     17If you are planning to run experiments from the directory, run: 
     18python repypp.py cncallpairsping.repy cncallpairsping.py 
     19python repypp.py deploycncexperiment.mix deploycncexperiment.py 
     20 
     216) If you are planning to run the Seattle Node Directory Service, copy testdir to every machine in your farm. 
    1722 
    1823 
    19 == Running the Server == 
     24== Running the Seattle Node Directory Service == 
    2025Prior to this section, please complete the steps in the 'Building and Configuring' Section 
     26On every machine on your farm run: 
     27python repy.py restrictions.cnc cncStandaloneServer.py <local available port to use> <user key range lower> <user key range upper> <server public key> <server private key> 
     28Please see the paper attached for more information on keyranges. Basically, the combined keyranges of all servers on your farm should cover the entire keyspace from 0 to 999, endpoints inclusive. When specifying the keyrange parameters to the server, the endpoints are includes. For example, if I specify lower 0 and upper 333 for a server, that server will cover the keyrange from 0 to 333 with endpoints 0 and 333 included. Keyranges of different servers should not overlap. For example, it would not be correct to have one server with keyrange 0-333 and another server with keyrange 333-666, since these ranges overlap for the value 333. 
    2129 
    22 <remainder of section coming soon> 
     30== Running an Experiment == 
     31Prior to this section, please complete the steps in the 'Building and Configuring' and 'Running the Seattle Node Directory Service' sections. 
     32 
     33<rest of section coming soon> 
     34 
    2335 
    2436== CNC Core Modules ==