Changes between Version 1 and Version 2 of DSC/Hurdle1
- Timestamp:
- Feb 16, 2013, 10:04:44 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DSC/Hurdle1
v1 v2 13 13 i. Each PI (team lead) will have received an email with account registration information. 14 14 b. Generate and upload ssh keys: 15 Go to http://www.orbit-lab.org/wiki/Documentation/SSHKeysfor instructions. Teams are advised that SSH key upload is not possible using Internet Explorer, and hence other browsers are recommended.15 Go to [wiki:Documentation/SSHKeys ssh keys page] for instructions. Teams are advised that SSH key upload is not possible using Internet Explorer, and hence other browsers are recommended. 16 16 c. Look up your reservation time to use the grid (note, teams also have received their assignments by email). For this hurdle, you will use the general-purpose domains, which are labeled ZDC##, where ## ranges from 01 to 50 17 i. Go to https://www.orbit-lab.org/schedule/ <https://www.orbit-lab.org/schedule/>. Access to the schedule requires login information provided in a registration email from the Challenge.18 ii. Note that there are a total of 50 general-purpose ORBIT virtual domains that have been set aside for Hurdle 1 and for general usage. These virtual domains are labeled ZDC##, where ## ranges from 01 to 50, and are different from the USRP-enabled virtual domains that will be used primarily for Hurdles 2 and 3. In order to be fair to all teams and ensure that each team has roughly the same exposure to the same virtual domains, a staggered time assignment has been devised for all teams across all standard virtual domains. The domains are available to DARPA Challenge teams for 14 hours per day, from 1000 to 2400 (Eastern). Teams should note that if they go to the schedule webpage, https://www.orbit-lab.org/schedule/ <https://www.orbit-lab.org/schedule/>, they may find out the actual nodes that belong to the virtual domain by hovering their cursor over the domain name (first column) in the schedule. At the end of each 2-hour time slot, teams will be automatically removed from their domain to make that domain available for the next team. Please be advised that this means that experiments that have not completed will be terminated.17 i. Go to [https://www.orbit-lab.org/schedule/ schedule]. Access to the schedule requires login information provided in a registration email from the Challenge. 18 ii. Note that there are a total of 50 general-purpose ORBIT virtual domains that have been set aside for Hurdle 1 and for general usage. These virtual domains are labeled ZDC##, where ## ranges from 01 to 50, and are different from the USRP-enabled virtual domains that will be used primarily for Hurdles 2 and 3. In order to be fair to all teams and ensure that each team has roughly the same exposure to the same virtual domains, a staggered time assignment has been devised for all teams across all standard virtual domains. The domains are available to DARPA Challenge teams for 14 hours per day, from 1000 to 2400 (Eastern). Teams should note that if they go to the [https://www.orbit-lab.org/schedule/ schedule webpage], they may find out the actual nodes that belong to the virtual domain by hovering their cursor over the domain name (first column) in the schedule. At the end of each 2-hour time slot, teams will be automatically removed from their domain to make that domain available for the next team. Please be advised that this means that experiments that have not completed will be terminated. 19 19 d. Access the domain at the specified time using: 20 20 {{{ 21 21 ssh username@console.grid.orbit-lab.org 22 22 }}} 23 Teams that are using Windows will need to use an application like PuTTY to open a session to console.grid.orbit-lab.org. An example screen shot of a successful attempt is shown at http://www.orbit-lab.org/wiki/Documentation/Short/Login <http://www.orbit-lab.org/wiki/Documentation/Short/Login>23 Teams that are using Windows will need to use an application like PuTTY to open a session to console.grid.orbit-lab.org. An example screen shot of a successful attempt is shown at [wiki:Documentation/Short/Login login page] 24 24 e. Image nodes with a specified image (darpahurdle1.ndz): 25 25 {{{ 26 26 omf load -i darpahurdle1.ndz -t system:topo:all 27 27 }}} 28 Note that the inclusion of "all" in the above command images all nodes within the team's virtual domain (in this case, two nodes). The execution and completion of this command will take several minutes as software is being installed onto the nodes. An example screen shot of a successful attempt is shown at http://www.orbit-lab.org/wiki/Documentation/Short/LoadImage#no528 Note that the inclusion of "all" in the above command images all nodes within the team's virtual domain (in this case, two nodes). The execution and completion of this command will take several minutes as software is being installed onto the nodes. An example screen shot of a successful attempt is shown at [wiki:Documentation/Short/LoadImage#no5 load image page] 29 29 f. Once the imaging has completed, turn the imaged nodes on: 30 30 {{{ … … 39 39 == Validation == 40 40 If successfully executed, the script will create a database on the OML server with a database name that has the team's username and timestamp. An automatic checker will monitor the database for a successful completion entry, at which time an email containing the instructions for Hurdle 2 will be sent to the team leader.[[BR]] 41 Questions or issues related to the hurdles should be sent by email to dsc-questions at orbit-lab dot org. Answers will be posted to a public forum site at [ [wiki:DSC/QandA]].[[BR]]41 Questions or issues related to the hurdles should be sent by email to dsc-questions at orbit-lab dot org. Answers will be posted to a public forum site at [wiki:DSC/QandA Q & A page].[[BR]] 42 42 Teams are reminded that the Qualification Period completes on March 5, 2013 at 23:59:59pm (Eastern). Submissions for Hurdle 3 must be turned in at the end of your time slot on that day. 43 43