EECS Technical Database

User Tools

Site Tools

You are here: Technical Database » Departmental Services » Labtest Mode
Trace:
services:labtest:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
services:labtest:start [2025/01/27 11:54] – [1. Allow lab machines to access eClass in labtest mode] jasservices:labtest:start [2026/08/21 15:30] (current) – jas
Line 47: Line 47:
 In order to setup your labtest, login to an EECS system via [[https://remotelab.eecs.yorku.ca|remotelab]], then follow these instructions: In order to setup your labtest, login to an EECS system via [[https://remotelab.eecs.yorku.ca|remotelab]], then follow these instructions:
  
-Open a Terminal, then start Labtest Assistant (labtest command) and pass in the concatenation of your course number and section (eg. 7777A for EECS7777A) followed by a space and then a test version name (eg. labtest1).  For example, for course EECS7777A if you're having a test that you want to call labtest1:+Open a Terminal (click "Activities" in the upper left corner, then click on "Terminal"), then start Labtest Assistant (labtest command) and pass in the concatenation of your course number and section (eg. 7777A for EECS7777A) followed by a space and then a test version name (eg. labtest1).  For example, for course EECS7777A if you're having a test that you want to call labtest1:
  
 <code>     <code>    
Line 53: Line 53:
 </code> </code>
  
-NOTE: The test version name can be whatever you choose.  In this case, we chose "labtest1".  Other names might be: labtest1-lab1, labtest1-lab2, midterm, final, or whatever other name you feel describes the purpose of the test. +NOTE: The test version name can be whatever you choose.  In this case, we chose "labtest1".  Other names might be: labtest1-lab1, labtest1-lab2, midterm, final, or whatever other name you feel describes the purpose of the test.  Whatever name you choose, you will need to submit that exact name as part of your labtest booking.
  
 After you hit enter, this is what you will see: After you hit enter, this is what you will see:
Line 84: Line 84:
 </code> </code>
  
-By default, the default start page for your labtest is called "index.html".   It will be opened in a GUI HTML editor.  This makes it easy for you to edit the start page whether or not you know HTML.  If you prefer to use the "vi" text editor, use the "edit" command instead of "gedit":+By default, the default start page for your labtest is called "index.html".   It will be opened in a GUI HTML editor.  This makes it easy for you to edit the start page whether or not you know HTML.  If you prefer to use the "vi" text editor instead, use the "edit" command instead of "gedit":
  
 <code> <code>
Line 90: Line 90:
 </code> </code>
  
-Modify the default page, and add your own information such as your rules for the test, and links to other content.  Change the index.html file, and customize it for your test.  By default, index.html includes a link to the file "labtest.pdf".  This file is intended to contain your labtest questions in PDF format.  If you don't want to use this filename, you can change the name to whatever you like.+Modify the default start page, and add your own information such as your rules for the test, and links to other content such as slides or documentation.  Change the index.html file, and customize it for your test.  By default, index.html includes a link to the file "labtest.pdf".  This file is intended to contain your labtest questions in PDF format.  If you don't want to use this filename, you can change the name to whatever you like.
  
-NOTE: If you're creating a labtest which points to an eClass quiz, you'll want to include a link to your quiz directly on this page.  It will look like this: https://eclass.yorku.ca/mod/quiz/view.php?id=12345 (you'll need to find the ID for your quiz)+NOTE: If you're creating a labtest which points to an eClass quiz, you'll want to include a link to your quiz directly on this page.  It will look like this: https://eclass.yorku.ca/mod/quiz/view.php?id=12345 (you'll need to find the ID for your quiz by logging into eClass)
  
 After you finish editing index.html, save the file. After you finish editing index.html, save the file.
Line 105: Line 105:
 Put success. Put success.
 </code> </code>
 +
 +You can also upload other files like slides, or documentation, and make that available to students in your test.
  
 Labtest Assistant will ensure that file permissions are setup correctly. Labtest Assistant will ensure that file permissions are setup correctly.
Line 144: Line 146:
 <code> <code>
 Labtest (7777A) [labtest1] > help Labtest (7777A) [labtest1] > help
 +
 +Available commands:
  
 status                                       Display labtest status status                                       Display labtest status
Line 162: Line 166:
 quit                                         Quit quit                                         Quit
  
 +app help                                     Display app help options
 +eecsvm help                                  Display eecsvm help options
 lock help                                    Display lock help options lock help                                    Display lock help options
 ltinit help                                  Display ltinit help options ltinit help                                  Display ltinit help options
Line 180: Line 186:
   * You can use the "restore" command to restore student files should they forget to submit.   * You can use the "restore" command to restore student files should they forget to submit.
  
-There are also a few subcommands in Labtest Assistant - lock, ltinit, restrict, and submit which will be described below.+There are various subcommands in Labtest Assistant - app, eecsvm, lock, ltinit, restrict, and submit, which will be described below. 
 + 
 +===== Labtest Applications Help ===== 
 + 
 +<code> 
 +Labtest (7777A) [labtest1] > app help 
 + 
 +Labtest Application Dock Help: 
 + 
 +In labtest mode, you can specify which applications are available on the app dock at the bottom of the 
 +screen. 
 + 
 +These applications are ALWAYS included no matter what your settings: Firefox, Logout, and LTRestore 
 + 
 +In labtest lock mode, no additional applications are added by default unless you add them using "app add". 
 + 
 +DISCLAIMER: Not all applications are suitable for labtest lock mode.  For example, VSCode 
 +            requires access to the terminal for compiling and debugging code. 
 +            Consult with tech when adding new applications in lock mode. 
 + 
 +In regular labtest mode, these other applications are added by default: 
 + 
 +org.gnome.Ptyxis 
 +eclipse 
 +org.gnome.Nautilus 
 + 
 +NOTE: If you add an app, but still want some of the defaults, you will have to re-add the defaults. 
 + 
 +NOTE:  
 + 
 +app default                                Delete custom app list 
 +app list                                   List custom app list 
 +app add <app>                              Add app to custom app list 
 +app delete <app>                           Delete app from custom app list 
 +app edit                                   Edit app list in text editor 
 +app help                                   Display this help text 
 +</code> 
 + 
 +===== EECSVM Help ===== 
 + 
 +<code> 
 +Labtest (7777A) [labtest1]  > eecsvm help 
 + 
 +EECSVM Mode Help: 
 + 
 +The EECSVM service allows students to use virtual machines required by courses 
 +they are taking. The service is only available to students enrolled in courses 
 +requiring this service, and the respective faculty. 
 + 
 +By default, EECSVM service is NOT available in Labtest mode.  It can be enabled 
 +(or disabled) with the options below.  When enabled, users do not have access 
 +to VMs that they have created outside of Labtest mode - only the template VMs. 
 + 
 +eecsvm enable                               Enable EESCVM mode 
 +eecsvm disable                              Disable EECSVM mode 
 +eecsvm help                                 Display this help text 
 + 
 +For more information on EECSVM service, please refer to this page: 
 + 
 +https://wiki.eecs.yorku.ca/dept/tdb/services:eecsvm 
 +</code>
  
 ===== Labtest Lock ===== ===== Labtest Lock =====
Line 191: Line 257:
 In labtest lock mode, the student is placed in a limited environment In labtest lock mode, the student is placed in a limited environment
 with no access to a terminal.  By default, the only application available with no access to a terminal.  By default, the only application available
-is Firefox web browser.  Additional applications can be made available.+is Firefox web browser.  Additional applications can be made available 
 +(see "apps help").
  
 lock enable                                 Enable lock mode lock enable                                 Enable lock mode
 lock disable                                Disable lock mode lock disable                                Disable lock mode
-lock list                                   List apps in lock mode 
-lock add <app> [<opts>] [<display-name>]    Add app to lock mode 
-lock delete <app>                           Delete app from lock mode 
-lock help                                   Display this help text 
- 
-NOTE: As there is no access to a terminal, apps must bring up a GUI. 
- 
-Example: 
  
 Enable lock mode (by default includes Web browser access only): Enable lock mode (by default includes Web browser access only):
Line 208: Line 267:
 > lock enable > lock enable
  
-Want to make Eclipse available in lock mode?+Disable lock mode:
  
-> lock add eclipse+> lock disable
  
-Add Matlab to lock mode (requires the option -desktop): 
- 
-> lock add matlab -desktop 
- 
-DISCLAIMER: Not all applications are suitable for lock mode.  For example, VSCode 
-            requires access to the terminal for compiling and debugging code. 
 </code> </code>
  
Line 247: Line 300:
 restrict list                                List labtest URL restrictions (including line numbers) restrict list                                List labtest URL restrictions (including line numbers)
 restrict add <restriction> [<line number>]   Add labtest URL restriction <restriction> restrict add <restriction> [<line number>]   Add labtest URL restriction <restriction>
-restrict eclass                              Allow access to eClass Quiz and VPL+restrict eclass                              Allow access to eClass (*)
 restrict delete <line-number>                Delete restriction <restriction> restrict delete <line-number>                Delete restriction <restriction>
 restrict edit                                Edit labtest restrictions restrict edit                                Edit labtest restrictions
Line 261: Line 314:
 labtest> restrict add -www.w3schools.com/html/html_editors.asp labtest> restrict add -www.w3schools.com/html/html_editors.asp
  
-To allow access to eClass Quiz/VPL:+(*) To allow access to eClass Quiz/VPL, please read the following web page:
  
-labtest> restrict eclass+https://wiki.eecs.yorku.ca/dept/tdb/services:labtest:start#accessing_external_hosts_in_labtest_eclass_example
  
-NOTE: Running an eClass in labtest requires other setup as well.  Please refer +*** Don't forget - ALWAYS test your eClass quiz using ltcloud! https://webapp.eecs.yorku.ca/ltcloud ***
-      to this URL for further instructions: +
- +
-  https://wiki.eecs.yorku.ca/dept/tdb/services:labtest:start#accessing_external_hosts_in_labtest_optional+
 </code> </code>
  
-By default, labtest doesn't permit students to access external websites.  Using the "restrict" subcommand, you can allow access to other web sites if your labtest requires it.  For more information, refer to this page.+By default, labtest doesn't permit students to access external websites.  Using the "restrict" subcommand, you can allow access to other web sites if your labtest requires it.  For more information on the restriction format, please refer to this page: 
 + 
 +  * https://wiki.eecs.yorku.ca/dept/tdb/services:labtest:start#accessing_external_hosts_in_labtest_optional 
 + 
 +For eClass specific restrictions, please refer to this page:
  
-https://wiki.eecs.yorku.ca/dept/tdb/services:labtest:start#accessing_external_hosts_in_labtest_optional+  * https://wiki.eecs.yorku.ca/dept/tdb/services:labtest:start#accessing_external_hosts_in_labtest_eclass_example
  
-Labtest restrictions are entirely optional as well.+Labtest restrictions are entirely optional.
  
 ===== Labtest Submit ===== ===== Labtest Submit =====
Line 295: Line 349:
 ====== Requesting Labtest Mode ====== ====== Requesting Labtest Mode ======
  
-Each term, the technical team books a significant number of labtests.  Please help us to make the process more efficient by ensuring that your labtest booking request contains all the required information in the proper format.+Each term, the technical team books a significant number of labtests for faculty.  Please help us to make the process more efficient by ensuring that your labtest booking request contains all the required information in the proper format.
  
 The **first time** in a term when you book a labtest for a course, please provide us with: The **first time** in a term when you book a labtest for a course, please provide us with:
Line 304: Line 358:
   * EECS TA user IDs (they will be able to help students move between machines in a labtest) (eg. johns, alicez, aigha) (*)   * EECS TA user IDs (they will be able to help students move between machines in a labtest) (eg. johns, alicez, aigha) (*)
  
-(*) Please make sure that you **only send us EECS user IDs** - not full names, not gmail, or other alternate email.  While EECS usernames should be the same as a users Passport York username, some TAs don't apply for an EECS account, and may not have one yet!  In this case, they won't be able to help your students move between machines during your test.  You can search for a users name [[https://webapp.eecs.yorku.ca/directory|here]] or by using the "finduser" command on our system (eg. finduser abc).  If you find that your TA doesn't have an EECS account, then please insist that they e-mail tech to request an account.  In this case, you can report their PPY username so that when their account is created, it will have access as an admin to your test.+(*) Before submitting a list of users, **please read this carefully**: Please make sure that you **only send us EECS user IDs** - not full names, not gmail, or other alternate email.  While EECS usernames should be the same as a users Passport York username, some TAs may not have an EECS account yet.  In this case, they won't be able to help your students move between machines during your test.  When you submit a list of usernames, we add it to the booking **as is**.  We don't check the usernames for validity.  You can search for a users name [[https://webapp.eecs.yorku.ca/directory|here]] or by using the "finduser" command on our system (eg. finduser abc). 
 + 
 +If a TA does not have an account, the process for them to get an account depends on the user type: 
 + 
 +  * If your TA is an undergrad, and an EECS student taking an EECS course, and they don't already have an EECS account, kindly ask them to get one with [[https://webapp.eecs.yorku.ca/activ8|Activ8]]. 
 +  * If your TA is an undergrad or grad that is not an EECS student, then **you** (**please not the student**) need to send an email to tech@eecs.yorku.ca with the following information:  (If the student emails us to request an account, we have to check with you which requires multiple emails.  If the request comes from you, we know it is legitimate.) 
 +    * Student Type: ugrad TA 
 +    * First name: 
 +    * Last name: 
 +    * Student ID: 
 +    * Passport York Login: 
 +  * If your TA is an EECS grad, and does not have an EECS account, then **they** need to email tech@eecs.yorku.ca with the following information: 
 +    * First name:  
 +    * Last name: 
 +    * Student ID:  
 +    * Degree: Msc/PhD  
 +    * Supervisor: 
 +    * Passport York login:  
 + 
 +Grad accounts will remain on our system for the duration of the students time in their programme at York.  Undergraduate temporary TA accounts will be deleted at the end of the term.
  
 For **subsequent** labtest bookings in your course, please always include in your booking: For **subsequent** labtest bookings in your course, please always include in your booking:
Line 318: Line 391:
 # <optional description> # <optional description>
 #version: <optional labtest version name> #version: <optional labtest version name>
-MM/DD/YYYY  HH:MM M labtest <HOSTSPEC> +MM/DD/YYYY  HH:MM M labtest HOSTSPEC 
-MM/DD/YYYY  HH:MM M default <HOSTSPEC>+MM/DD/YYYY  HH:MM M default HOSTSPEC
 </code> </code>
  
Line 328: Line 401:
   * HH:MM - hour:minute hour of your test (note that this is impacted by the next field)   * HH:MM - hour:minute hour of your test (note that this is impacted by the next field)
   * M - number of minutes of warnings to send to students before system will reboot (usually 5) - NOTE: If M=5, machines will REBOOT at HH:MM + 5 MIN, NOT at HH:MM   * M - number of minutes of warnings to send to students before system will reboot (usually 5) - NOTE: If M=5, machines will REBOOT at HH:MM + 5 MIN, NOT at HH:MM
-  * <HOSTSPEC> - lets us know which hosts you want to book. <HOSTSPEC> can contain:+  * HOSTSPEC - lets us know which hosts you want to book. <HOSTSPEC> can contain:
     * individual machines separated by commas: ea01,ea02,ea03     * individual machines separated by commas: ea01,ea02,ea03
     * groups of machines:      * groups of machines: 
Line 358: Line 431:
 # labtest1-LAB1 # labtest1-LAB1
 # version: labtest1-lab1 # version: labtest1-lab1
-06/20/2023   09:54 5 labtest ea 01-78+06/20/2023   09:55 5 labtest ea 01-78
 06/20/2023   11:45 5 default ea 01-78 06/20/2023   11:45 5 default ea 01-78
 </code> </code>
Line 364: Line 437:
 Description: Description:
  
-  * On June 20, 2023 at 9:54 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot in 5 minutes into labtest mode.  The machines will remind students once per minute until the 5 minutes have elapsed. +  * On June 20, 2023 at 9:55 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot in 5 minutes into labtest mode.  The machines will remind students once per minute until the 5 minutes have elapsed. (You could also use "4" instead of "5" in the third column to give 4 minutes of warnings, and a reboot at 9:59 so the machines are ready by 10.) 
-  * The machines will reboot into labtest mode at 9:59 AM, so they should be ready by 10:00 AM.+  * The machines will reboot into labtest mode at 9:55 AM, so they should be ready by 10:00 AM.
   * On June 20, 2023 at 11:45 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot back to Linux mode in 5 minutes.  The machines will remind students once per minute until the 5 minutes have elapsed.   * On June 20, 2023 at 11:45 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot back to Linux mode in 5 minutes.  The machines will remind students once per minute until the 5 minutes have elapsed.
-  * At 11:50 PM, machines will reboot from Labest mode back to Linux mode.+  * At 11:50 PM, machines will reboot from Labtest mode back to Linux mode.
  
 **Please ensure that your labtest ends 10 minutes prior to the end of your lab booking time.**  For example, if your lab time is 10:00 AM - 11:30 AM, then the students should receive their 5 minute warning at 11:45 AM, then the machines will reboot at 11:50 AM.  **Please ensure that your labtest ends 10 minutes prior to the end of your lab booking time.**  For example, if your lab time is 10:00 AM - 11:30 AM, then the students should receive their 5 minute warning at 11:45 AM, then the machines will reboot at 11:50 AM. 
Line 376: Line 449:
 # labtest1-LAB1 # labtest1-LAB1
 # version: labtest1-lab1 # version: labtest1-lab1
-06/20/2023   09:54 5 labtest ea 01-78+06/20/2023   09:55 5 labtest ea 01-78
 06/20/2023   11:45 5 default ea 01-78 06/20/2023   11:45 5 default ea 01-78
 </code> </code>
  
-If you have students with different accommodations for extra time, please submit a **separate** block for each accommodation type.  Here's the same booking request above with 5 machines getting an extra hour, 2 machines getting 30 minutes extra, and 1 machine getting 10 minutes extra.  **Accommodations cannot exceed your lab booking time.  In order to book machines past your lab booking time, please consult with tech.**+If you have students with different accommodations for extra time, please submit a **separate** block for each accommodation type.  Here's the same booking request above with 5 machines getting an extra hour, 2 machines getting 30 minutes extra, and 1 machine getting 20 minutes extra.  **Accommodations cannot exceed your lab booking time.  In order to book machines past your lab booking time, please consult with tech.**
  
 <code> <code>
 # labtest1-LAB1 MAIN # labtest1-LAB1 MAIN
 # version: labtest1-lab1 # version: labtest1-lab1
-06/20/2023   09:54 5 labtest ea 01-70+06/20/2023   09:55 5 labtest ea 01-70
 06/20/2023   11:45 5 default ea 01-70 06/20/2023   11:45 5 default ea 01-70
  
 # labtest1-LAB1 ACCOMMODATION - 5 machines getting extra hour # labtest1-LAB1 ACCOMMODATION - 5 machines getting extra hour
 # version: labtest1-lab1 # version: labtest1-lab1
-06/20/2023   09:54 5 labtest ea 71-75+06/20/2023   09:55 5 labtest ea 71-75
 06/20/2023   12:45 5 default ea 71-75 06/20/2023   12:45 5 default ea 71-75
  
 # labtest1-LAB1 ACCOMMODATION - 2 students getting extra 30 minutes # labtest1-LAB1 ACCOMMODATION - 2 students getting extra 30 minutes
 # version: labtest1-lab1 # version: labtest1-lab1
-06/20/2023   09:54 5 labtest ea 76-77+06/20/2023   09:55 5 labtest ea 76-77
 06/20/2023   12:15 5 default ea 76-77 06/20/2023   12:15 5 default ea 76-77
  
 # labtest1-LAB1 ACCOMMODATION - 1 student getting extra 20 minutes # labtest1-LAB1 ACCOMMODATION - 1 student getting extra 20 minutes
 # version: labtest1-lab1 # version: labtest1-lab1
-06/20/2023   09:54 5 labtest ea78+06/20/2023   09:55 5 labtest ea78
 06/20/2023   12:05 5 default ea78 06/20/2023   12:05 5 default ea78
 </code> </code>
Line 422: Line 495:
 </code> </code>
  
-...  or you can create one long session 9:00 AM - 11:00 AM, but you will have to clear the lab manually between sessions yourself:+...  or you can create one long session 9:00 AM - 1:00 PM, but you will have to clear the lab manually between sessions yourself:
  
 <code> <code>
Line 432: Line 505:
  
 After you have submitted your labtest booking, someone from tech will get back to you to confirm your booking.  If you don't get back a confirmation email from tech, then your session has **not** been booked.  You can check the labtest booking schedule [[http://www.eecs.yorku.ca/schedule/pcmode/|here]] at any time. After you have submitted your labtest booking, someone from tech will get back to you to confirm your booking.  If you don't get back a confirmation email from tech, then your session has **not** been booked.  You can check the labtest booking schedule [[http://www.eecs.yorku.ca/schedule/pcmode/|here]] at any time.
 +
 +===== Reserving Additional Lab Time for Accommodations =====
 +
 +You can now view the [[https://www.eecs.yorku.ca/schedule/lab|Lab Schedule]] online.  This includes all the lab bookings **AND** extra lab bookings (at the bottom).  If you need to book additional lab time outside of your lab session for accomodations, first consult the schedule and extra bookings to check for availability of extra time.  Ask tech to reserve that time for you.  Once a lab is reserved for your use, you can now use that additional block of time in your labtest booking request.
  
 If you have any questions about labtest booking, please e-mail the technical team. If you have any questions about labtest booking, please e-mail the technical team.
Line 919: Line 996:
 Now if you test your labtest in ltcloud, the user will only be able to access the Firefox web browser. Now if you test your labtest in ltcloud, the user will only be able to access the Firefox web browser.
  
-If you want additional software to be accessible in labtest, it must use a GUI.  You add to the lock file lines of the following format:+If you want additional software to be accessible in labtest, create a file in the labtest folder called "apps" (eg. /eecs/dept/www/course/9999/labtest/default/apps).  The file contains a list of ".desktop" files available on the system for Applications that you wish to be included in the app dock at the bottom of the screen. A .desktop file is a plain text configuration file used in Linux and Unix-like operating systems to create application shortcuts, define program launchers, and integrate software into a desktop environment's application menu. 
  
-  <app name>,<OPTIONAL app arguments>,<OPTIONAL app display name>+These applications are ALWAYS included no matter what your settings: Firefox, Logout, and LTRestore
  
-For example, if you want Eclipse to be available in lock mode, you would add to the lock file:+In labtest lock mode, no additional applications are added by default unless you add them to the app file.
  
-  eclipse+**DISCLAIMER: Not all applications are suitable for labtest lock mode.  For example, VSCode requires access to the terminal for compiling and debugging code. Consult with tech when adding new applications in lock mode. **
  
-By default, there are no optional arguments, and if no alternate display name is mentioned, then it will appear in the menu with the same name as the command name, but with the first letter capitalized ("Eclipse").+In regular labtest mode, these other applications are added by default:
  
-If you want to add Matlab:+org.gnome.Ptyxis (this is the terminal) 
 +eclipse 
 +org.gnome.Nautilus (this is the file manager)
  
-  matlab,-desktop+If you want to add an app, you need to find the desktop file for the app.  Desktop files are located in /eecs/local/share/applications/*.desktop.
  
-In order to run "Matlab", we have to pass "-desktop".  It would appear in the menu as "Matlab".+If you add an app, but still want some of the defaults to appear, you have to add the defaults back as well.  For example, if you want to add IntelliJ, but you want to continue with the existing defaults, then create the "app" file containing:
  
-On the other hand, if you wanted to include Visual Studio Code, you would add:+idea <- that's intellij 
 +org.gnome.Ptyxis (this is the terminal) 
 +eclipse 
 +org.gnome.Nautilus (this is the file manager)
  
-  code,,Visual Studio Code+** Please ensure that you're careful when allowing access to software in lock mode.  Giving access to additional software may have unintended side effects.  For example, if you allow access to Eclipse, then students can compile and run code which can give access to system resources that would otherwise not be available.  Access to a terminal is still blocked. **
  
-Now, "Visual Studio Code" will be displayed in the menu, but it will execute the command "code".+====== Accessing External Hosts In Labtest (optional) ======
  
-In labtest lock mode, the window environment is a little different in order to support the locked down nature of the environment.    +Your labtest may require students to access external websites.  For example, if you're teaching a course on web development, you may want your students to be able to access https://www.w3schools.com during your labtest. You can restrict access to a complete website, or even a part of a website!  In the next section we'll even cover restricting access to an eClass quiz. 
  
-When labtest mode is started, a web browser will appear with the labtest start page.  Additional software will be available by right clicking the desktop, or by clicking on the "Apps & Logout" menu in the bottom left corner of the desktop.+With host level access control, you can give your labtest access to specific websites such as https://www.w3schools.com.  Students will be able to access any URL on the given sites.
  
-Please ensure that you're careful when allowing access to software in lock mode.  Giving access to additional software may have unintended side effects.  For example, if you allow access to Eclipse, then students can compile and run code which can give access to system resources that would otherwise not be available.  Access to a terminal is still blocked.+Let's say you're teaching a course EECS9999, and you want students in your labtest to be able to access "https://www.w3schools.com" and "https://validator.w3.org" web sites during your test:
  
-====== Accessing External Hosts In Labtest (optional) ======+**Setup With Labtest Assistant**
  
-Your labtest may require students to access external websites.  For example, if you're teaching a course on web development, you may want your students to be able to access www.w3schools.com during labtest.  You may also want your students to complete a quiz on eclass.yorku.ca. You can restrict access to a complete website, or even a part of a website!  +From within Labtest Assistant, use the "restrict" command: 
 + 
 +<code> 
 +Labtest (9999) [labtest1]  > restrict add www.w3schools.com 
 + 
 +Restriction www.w3schools.com inserted. 
 + 
 +Labtest (9999) [labtest1]  > restrict add validator.w3.org 
 + 
 +Restriction validator.w3.org inserted. 
 +</code>
  
-With host level access control, you can give your labtest access to specific websites such as www.w3schools.com.  Students will be able to access any URL on the given sites.+You can use "restrict edit" to edit the restriction list in a text editor, or "restrict list" to list restrictions.  Use "restrict help" for more information on the options that are available.
  
-Create a file called "labtest.allow" in your labtest web directory (/eecs/dept/www/course/<COURSE>/labtest/labtest.allow).  Include in this file complete website names that you want students to be able to access during your test, one per line.  +**Setup Manually**
  
-For example, if you're teaching a course EECS9999, and you want students in your labtest to be able to access the "www.w3schools.com" and "validator.w3.org" web sites during your test, then create /eecs/dept/www/course/9999/labtest/labtest.allow containing:+If you are setting your labtest up manually, create a file called "labtest.allow" in your labtest web directory (/eecs/dept/www/course/<COURSE>/labtest/labtest.allow).  Include in this file complete website names that you want students to be able to access during your test, one per line.  For example:
  
 <code> <code>
Line 969: Line 1061:
 </code> </code>
  
-Please note that if the web site you are trying to access includes links to other sites that you want to work, or includes files from other sites (eg. css style file or font file), then you may need to add additional entries to your labtest.allow file.  Contact tech for assistance.+**Please note that if the web site you are trying to access includes links to other sites that you want to work, or includes files from other sites (eg. css style file or font file), then you may need to add additional entries to your labtest.allow file.  Contact tech for assistance.**
  
-Labtest also makes it possible to implement partial access to a website.  For example, if you wanted your students to only be able to access https://www.w3schools.com/html during your test (and not the main page https://www.w3schools.com, or https://www.w3schools.com/css, https://www.w3schools.com/jss, etc), then instead of just adding "www.w3schools.com" to your labtest.allow file, you would instead add "www.w3schools.com/html".+Labtest also makes it possible to implement partial access to a website.  For example, if you wanted your students to only be able to access https://www.w3schools.com/html during your test (and not the main page https://www.w3schools.com, or https://www.w3schools.com/css, https://www.w3schools.com/jss, etc), then you set it up like this:
  
-Now, if you try to visit anything but "https://www.w3schools.com/html", you will receive an error: "Access to this URL is blocked.".+**Setup with Labtest Assistant**
  
-However, you will also notice that the page doesn't display properly.  If you look at the page source you will realize that this is because the page is trying to access fonts from "https://www.w3schools.com/lib", and CSS from "https://www.w3schools.com/plus".  You can easily add these additional entries to labtest.allow for the site to display properly:+From within Labtest Assistant, use the "restrict" command again: 
 + 
 +<code> 
 +Labtest (9999) [labtest1]  > restrict add www.w3schools.com/html 
 + 
 +Restriction www.w3schools.com/html inserted. 
 + 
 +Labtest (9999) [labtest1]  > restrict list 
 + 
 +     1 www.w3schools.com/html 
 +</code> 
 + 
 +**Setup Manually** 
 + 
 +Add "www.w3schools.com/html" to your labtest.allow file instead of "www.w3schools.com" alone. 
 + 
 +Now, during your labtest, if you try to visit anything but "https://www.w3schools.com/html", you will receive an error: "Access to this URL is blocked.". 
 + 
 +However, you will also notice that the page doesn't display properly.  If you look at the page source you will realize that this is because the page is trying to access fonts from "https://www.w3schools.com/lib", and CSS from "https://www.w3schools.com/plus".  You can easily add these additional entries: 
 + 
 +**Setup with Labtest Assistant** 
 + 
 +Once again, use the restrict command: 
 + 
 +<code> 
 +Labtest (9999) [labtest1]  > restrict add www.w3schools.com/lib 
 + 
 +Restriction www.w3schools.com/lib inserted. 
 + 
 +Labtest (9999) [labtest1]  > restrict add www.w3schools.com/plus 
 + 
 +Restriction www.w3schools.com/plus inserted. 
 + 
 +Labtest (9999) [labtest1]  > restrict list 
 + 
 +     1 www.w3schools.com/html 
 +     2 www.w3schools.com/lib 
 +     3 www.w3schools.com/plus 
 +</code> 
 + 
 +**Setup Manually** 
 + 
 +Add "www.w3schools.com/lib" and "www.w3schools.com/plus" to labtest.allow.  It will now look like this:
  
 <code> <code>
Line 983: Line 1117:
 </code> </code>
  
-Now, let's say there's a particular URL under https://www.w3schools.com/html that you don't want the student to be able to access (eg. https://www.w3schools.com/html/html_editors.asp).  You could add this reject rule to your labtest.allow file:+Now, let's say there's a particular URL under https://www.w3schools.com/html that you don't want the student to be able to access (eg. https://www.w3schools.com/html/html_editors.asp).  This can easily be handled as well:
  
 +**Setup with Labtest Assistant**
 +
 +Again, use the restrict command:
 <code> <code>
--www.w3schools.com/html/html_editors.asp+Labtest (9999) [labtest1]  > restrict add -www.w3schools.com/html_editor.asp 
 + 
 +Restriction -www.w3schools.com/html_editor.asp inserted. 
 + 
 +Labtest (9999) [labtest1]  > restrict list 
 + 
 +     1 www.w3schools.com/html 
 +     2 www.w3schools.com/lib 
 +     3 www.w3schools.com/plus 
 +     4 -www.w3schools.com/html_editor.asp
 </code> </code>
 +
 +**Setup Manually**
 +
 +Add the following rule to labtest.allow:
 +
 +  -www.w3schools.com/html/html_editors.asp
  
 NOTE: Rejected URL fragments are processed before accepted URL fragments.  Add this rule to the bottom or top of your labtest.allow file, and it will have the same effect. NOTE: Rejected URL fragments are processed before accepted URL fragments.  Add this rule to the bottom or top of your labtest.allow file, and it will have the same effect.
Line 993: Line 1145:
 A few important notes: A few important notes:
  
-1) For every website that students needs to be able to access during labtest, you must specify the website name in the labtest.allow file.  You may include just the website name (in which case all URLs on that site will work), or you may include the URLs on that website that you want to be accessible. +1) For every website that students needs to be able to access during labtest, you must either use "restrict add <site>" in Labtest Assistant to add the restriction, or manually add the restriction to the labtest.allow file.  You may include just the website name (in which case all URLs on that site will work), or you may include the URLs on that website that you want to be accessible. 
  
 2) All external pages are rejected by default. 2) All external pages are rejected by default.
Line 1014: Line 1166:
 In this section, we will configure labtest to provide secure access to an eClass quiz. In this section, we will configure labtest to provide secure access to an eClass quiz.
  
-===== 1.  Allow lab machines to access eClass in labtest mode =====+===== 1.  Allow Lab Machines To Access eClass In Labtest Mode =====
  
-First, you need to allow the lab machines to access eClass in labtest mode.+First, you need to allow the lab machines limited access to eClass in labtest mode.
  
-If you're using Labtest Assistant:+If you're using Labtest Assistant, use the "restrict eclass" command:
  
-  * Use the "restrict eclass" command.+<code> 
 +labtest> restrict eclass 
 +</code>
  
-If you're setting your labtest up manually, you will need to create a labtest.allow file in your labtest directory which includes the allowed URL parts for eClass.  At an absolute minimum this would be:+If you're not using Labtest Assistant, you need to create a labtest.allow file in your labtest directory which includes the allowed URL parts for eClass:
  
-  eclass.yorku.ca+<code> 
 +eclass.yorku.ca/login 
 +eclass.yorku.ca/auth 
 +eclass.yorku.ca/pluginfile.php 
 +eclass.yorku.ca/theme 
 +eclass.yorku.ca/lib 
 +eclass.yorku.ca/local 
 +eclass.yorku.ca/repository 
 +eclass.yorku.ca/course/switchrole.php 
 +dm7crvy4e45rz.cloudfront.net 
 +eclass.yorku.ca/mod/quiz/startattempt.php 
 +eclass.yorku.ca/mod/quiz/attempt.php 
 +eclass.yorku.ca/mod/quiz/processattempt.php 
 +eclass.yorku.ca/mod/quiz/summary.php 
 +eclass.yorku.ca/mod/quiz/review.php 
 +eclass.yorku.ca/mod/quiz/autosave 
 +</code>
  
-If your labtest.allow file only includes "eclass.yorku.ca", then labtest will do the following:+===== 2. Determine Your eClass Quiz URL =====
  
-  * restrict user access to "Private Files". +Visit your eClass quiz from your machine that is **not** in labtest mode. Grab the quiz URL from the URL bar in your web browser.  The URL will look something like this: https://eclass.yorku.ca/mod/quiz/view.php?id=12345
-  * restrict user access to eClass communications (so they cannot chat with other students).+
  
-However, there are still problems:+You can also get this link in eClass if you go to: Activities >> Quizzes then hover your mouse over your quiz.
  
-  * Students will not be able to view images attached to quiz questions because eClass caches these on an external site which hasn't been allowed: dm7crvy4e45rz.cloudfront.net +===== 3. Allow Access To Your eClass Quiz ID In Labtest Mode =====
-  * Students would still be able to access eClass pages for any courses to which they are enrolled.+
  
-This labtest.allow file is best for eClass use because it resolves the remaining problems:+If you're using Labtest Assistant, use the following command to allow access your eClass quiz in labtest:
  
-  eclass.yorku.ca/login +<code> 
-  eclass.yorku.ca/auth +labtest> restrict add eclass.yorku.ca/mod/quiz/view.php?id=ID 
-  eclass.yorku.ca/pluginfile.php +</code>
-  eclass.yorku.ca/quiz +
-  -eclass.yorku.ca/mod/quiz/index.php +
-  eclass.yorku.ca/mod/quiz +
-  eclass.yorku.ca/theme +
-  eclass.yorku.ca/lib +
-  eclass.yorku.ca/local +
-  eclass.yorku.ca/repository +
-  eclass.yorku.ca/course/switchrole.php +
-  dm7crvy4e45rz.cloudfront.net+
  
-If you wish to use additional functionality in eClass (other than just quizzes), you may need to add additional URLs to labtest.allow.  For example, to add access to Virtual Programming Lab (VPL), add the following to labtest.allow:+Replace ID with your eClass Quiz ID.
  
-  eclass.yorku.ca/mod/vpl +If you're not using Labtest Assistant, add the following line to the end of your labtest.allow file in your labtest directory: 
-  vpl1.eecs.yorku.ca+ 
 +<code> 
 +eclass.yorku.ca/mod/quiz/view.php?id=ID 
 +</code> 
 +   
 +Replace ID with your eClass Quiz ID.
  
 Ensure that the labtest.allow file is readable: <code>chmod 644 /eecs/dept/www/course/COURSE/labtest/labtest.allow</code> Ensure that the labtest.allow file is readable: <code>chmod 644 /eecs/dept/www/course/COURSE/labtest/labtest.allow</code>
  
-===== 2. Provide a Link to Your eClass Quiz in Your Labtest Start Page =====+===== 4. Provide a Link to Your eClass Quiz in Your Labtest Start Page =====
  
-Your labtest start page (eg. /eecs/dept/www/course/<COURSE>/labtest/index.html) (or a PDF that your start page refers to) **must** include a direct link to your specific eclass quiz.  It will look something like this: https://eclass.yorku.ca/mod/quiz/view.php?id=XXXX  You can get this link in eClass if you go to: Activities >> Quizzes  then hover your mouse over your quiz, or, if you click on the quiz to start it, you can copy and paste the URL from your browser. +Your labtest start page (eg. /eecs/dept/www/course/<COURSE>/labtest/index.html) (or a PDF that your start page refers to) **must** include a direct link to your specific eclass quiz. You found this URL in step 2.
  
-If you're using Labtest Assistant, open your labtest start page using the "gedit" (GUI editor) or "edit" (text editor) commands.+If you're using Labtest Assistant, open your labtest start page using the "gedit" (GUI editor) or "edit" (text editor) commands and add a link to your eClass quiz on the page.  For example: 
 + 
 +<code> 
 +Click <a href="https://eclass.yorku.ca/mod/quiz/view.php?id=12345">here</a> to take the quiz. 
 +</code>
  
 If you're not using Labtest Assistant, open the index.html file in your labtest directory, and add the link manually. If you're not using Labtest Assistant, open the index.html file in your labtest directory, and add the link manually.
Line 1068: Line 1236:
 **IMPORTANT** If students try to access "https://eclass.yorku.ca" in their web browser during your labtest, **they will be blocked**.  Students can **only** visit your quiz by clicking on the link to the quiz from your labtest start page.  **IMPORTANT** If students try to access "https://eclass.yorku.ca" in their web browser during your labtest, **they will be blocked**.  Students can **only** visit your quiz by clicking on the link to the quiz from your labtest start page. 
  
-===== 3. Restrict IP Addresses Which Can Access Your Quiz From Within eClass =====+===== 5. Restrict IP Addresses Which Can Access Your eClass Quiz From Within eClass =====
  
 Login to eClass.  Restrict access to your eClass quiz to the IP addresses of the lab machines where the students will be writing the quiz.  If you don't do this, even though your in-lab students will be limited in the proper way, students who are outside of the lab would also be able to write your quiz.  Go to: Activities >> Quizzes >> Settings >> Extra restriction on attempts >> Show more... >> Require network address.  Please copy and paste the specific address list below: Login to eClass.  Restrict access to your eClass quiz to the IP addresses of the lab machines where the students will be writing the quiz.  If you don't do this, even though your in-lab students will be limited in the proper way, students who are outside of the lab would also be able to write your quiz.  Go to: Activities >> Quizzes >> Settings >> Extra restriction on attempts >> Show more... >> Require network address.  Please copy and paste the specific address list below:
Line 1084: Line 1252:
  
 NOTES:  NOTES: 
-  * If you are using all 3 of WSC105, WSC106, AND WSC108, use instead: 130.63.131.0/24+  * If you are using all 3 of WSC105, WSC106, AND WSC108, use instead: 130.63.131.0/24 --- however, if you're only using say 1 of the labs, and use 130.63.131.0/24, then the other 2 labs will be able to access your quiz **outside** of labtest mode.
   * If you are testing in ltcloud, please ensure that you include both the IP range for the required lab followed by a comma followed by the ltcloud range.   * If you are testing in ltcloud, please ensure that you include both the IP range for the required lab followed by a comma followed by the ltcloud range.
-  * If your test is being conducted in several labs, you can join two IP ranges with a comma in between them.  Note though that if the number of IP ranges separated by commas exceeds 18, the IP restrictions will not function correctly due to an eClass bug.  Please consult with tech to test your IP range prior to your test.+  * If your test is being conducted in several labs, you can join two IP ranges with a comma in between them.  Note though that if the number of IP ranges separated by commas exceeds around 14, the IP restrictions will not function correctly due to an eClass bug.  Please consult with tech to test your IP range prior to your test.
  
-===== 4. Limit the Start and End Time of Your Quiz in eClass =====+===== 6. Limit the Start and End Time of Your Quiz in eClass =====
  
 You will need to limit the start and end time of your quiz in eClass.  If you don't do this, then students on the lab machines will be able to access your quiz **before** your labtest!  Go to: Activities >> Quizzes >> Settings >> Timing and configure the "Open the quiz" and "Close the quiz" times.  Note that if students try to access the quiz before the open time, they will be denied because eclass will try to redirect them back to the course eclass page which has been blocked.  They should try again at the start time of your test. You will need to limit the start and end time of your quiz in eClass.  If you don't do this, then students on the lab machines will be able to access your quiz **before** your labtest!  Go to: Activities >> Quizzes >> Settings >> Timing and configure the "Open the quiz" and "Close the quiz" times.  Note that if students try to access the quiz before the open time, they will be denied because eclass will try to redirect them back to the course eclass page which has been blocked.  They should try again at the start time of your test.
 +
 +===== 7. Lock Access to eClass Only (optional) =====
 +
 +If you want your students to only be able to access eClass, and no additional software on our systems (eg. Eclipse/VScode), then you will configure Labtest "lock" mode. 
 +
 +If you're using Labtest Assistant, use the command: lock enable
 +
 +If you're not using Labtest Assistant, then touch the file called "lock" in your labtest directory:
 +
 +  % touch /eecs/dept/www/course/MYCOURSE/labtest/labtest1/lock
 +  % chmod 644 /eecs/dept/www/course/MYCOURSE/labtest/labtest1/lock
  
 Final Notes: Final Notes:
  
   * Some faculty would like to use eClass "assignment" in labtest. Note that eClass assignments do not permit IP address restriction.  A quiz with 1 question can replace an "assignment".   * Some faculty would like to use eClass "assignment" in labtest. Note that eClass assignments do not permit IP address restriction.  A quiz with 1 question can replace an "assignment".
 +  * If you're using VPL, you'll need to allow access to the following URL fragments with either "restrict add" in Labtest Assistant, or manually in your labtest.allow file:
 +    * eclass.yorku.ca/mod/vpl/view.php?id=ID
 +    * vpl1.eecs.yorku.ca
   * **Always test your eClass quiz using ltcloud!  Don't assume that just because it works fine from your unrestricted PC that it will work fine in labtest. Ensuring that your quiz works in ltcloud will guarantee an improved experience in your test session. **   * **Always test your eClass quiz using ltcloud!  Don't assume that just because it works fine from your unrestricted PC that it will work fine in labtest. Ensuring that your quiz works in ltcloud will guarantee an improved experience in your test session. **
  
Line 1211: Line 1393:
 \\ \\
 WARNING: Before you can re-use the same secureq directory for another test, at a minimum, you must move any existing “secureq/map” directory out of the way. This directory contains files which track which question each of your students received on the test, and on what machine. This will limit which question they can receive on your new test, and on what machine they can work WARNING: Before you can re-use the same secureq directory for another test, at a minimum, you must move any existing “secureq/map” directory out of the way. This directory contains files which track which question each of your students received on the test, and on what machine. This will limit which question they can receive on your new test, and on what machine they can work
 +
 +====== Labtest and Containers ======
 +
 +It may be helpful to some courses to use containers from within labtest.  This section will provide an example of downloading the latest Ubuntu image, modifying the image, and pushing the image to labtest.
 +
 +Download an Ubuntu image:
 +
 +<code>
 +% podman pull ubuntu:latest
 +</code>
 +
 +**NOTE:** Your EECS home directory has limited storage space and is on network storage.  **This is not ideal for working with containers.**  Faculty who have their own research servers or personal workstations can use this equipment to generate images, the result of which can be used in labtest.  Failing this, faculty can use /tmp space for **temporary** container development.  For more information, consult with tech.  For information on using containers in EECS click [[services:podman|here]].
 +
 +Start up the container from the ubuntu:latest image, and call it my-ubuntu:
 +
 +<code>
 +% podman run -it --name my-ubuntu ubuntu:latest bash
 +</code>
 +  
 +Make changes -- in this case, we'll just add an empty file named "file", but you could install additional packages, add users or groups, and configure the system in any way you like:
 +
 +<code>
 +# cd
 +# touch file
 +# exit
 +</code>
 +
 +Now let's stop the container:
 +
 +<code>
 +% podman stop my-ubuntu
 +</code>
 +
 +Commit the changes in my-ubuntu container to my-new-ubuntu image:
 +
 +<code>
 +% podman commit my-ubuntu my-new-ubuntu
 +</code>
 +
 +Save the image to a tar file:
 +
 +<code>
 +% podman save -o my-new-ubuntu.tar my-new-ubuntu
 +</code>
 +
 +Place my-new-ubuntu.tar into ltinit directory in the course labtest web directory:
 +
 +In ltinit/labtest.sh we can load the image, start the container, and open up a Terminal window connected to the container:
 +
 +<code>
 +podman load -i $HOME/ltinit/my-new-ubuntu.tar
 +podman run -dit --name labtest my-new-ubuntu
 +gnome-terminal -- podman exec -it labtest bash
 +</code>
 +
 +Now, when the user logs in, the image is unpacked and loaded. Podman run starts the container.  Note the following options:
 +
 +  * -d runs it in the background (detached).
 +  * -i keeps stdin open.
 +  * -t allocates a pseudo-tty.
 +  * --name labtest names the container labtest.
 +  * my-new-ubuntu is the image used to create the container
 +
 +**NOTE:** Large container downloads with large multi lab labtests could result in performance issues since all users will be downloading the container on login.  In this case, discuss with tech how we could instead add the container to the course labtest web directory, then include an alias in the users .cshrc file which will download the image with curl or wget, load the image, and start the container.  As users will be doing this manually, and will be doing this at different times, the chance of performance issue is much less.  
  
 ====== Labtest File Synchronization (ltsave) ====== ====== Labtest File Synchronization (ltsave) ======
Line 1373: Line 1619:
 Sometimes, during labtest mode, you may require a student to move from one machine to another machine.  This may be because the student is in the wrong area of the lab, or because there is some failure on the machine (eg. monitor).  Labtest home directories are stored on the local machine, and not a network drive.  Moving a student to another machine without some mechanism to copy student files from one machine to the other would mean starting with a brand new home directory, no files, and an unhappy student!  Sometimes, during labtest mode, you may require a student to move from one machine to another machine.  This may be because the student is in the wrong area of the lab, or because there is some failure on the machine (eg. monitor).  Labtest home directories are stored on the local machine, and not a network drive.  Moving a student to another machine without some mechanism to copy student files from one machine to the other would mean starting with a brand new home directory, no files, and an unhappy student! 
  
-When a student moves from one machine to the another, and logs in, the system will check if the student has files from another machine stored in the labtest save cache.  If they do, the student will see the following message: "Welcome!  It seems you have worked on this labtest on another machine.  You may ask one of the test supervisors for approval to transfer your work to this machine, or, hit Cancel to start again.".  At this point, if the student hits "Cancel", then they are logged in with a new environment without restoring their files.  If they want to restore their files from another machine, they need either **your** or your TAs approval!+When a student moves from one machine to the another, files are not copied automatically.  Once the student logs in, they should click on the "LTRestore" icon which is located on the dock at the bottom of the screen.  The student will see the following message: "This app allows a labtest administrator to restore your work fro ma previous session. Do you need to restore work from a previous session?".  If they click "Yes", then either the faculty or the TA (who has been specified in the admin list for the labtest) must authenticate. 
  
 To restore a students files from another machine, you will need to enter 3 pieces of information -- Labtest Admin (userid), Password, and Restore Machine.  Select the labtest admin from the dropdown list.  The labtest admins are specified by you when you request labtest mode.  The admins are also displayed in the pcmode schedule.  It's important that you check the list of admins before every labtest because neither the lab monitor nor tech staff will be able to restore a students files.   After selecting your name from the admin list, enter your system password.   Next, under "Restore Machine", a dropdown box lists all the machines where the student has been.  Select a machine from which you wish to restore the students files, and click "OK".   To restore a students files from another machine, you will need to enter 3 pieces of information -- Labtest Admin (userid), Password, and Restore Machine.  Select the labtest admin from the dropdown list.  The labtest admins are specified by you when you request labtest mode.  The admins are also displayed in the pcmode schedule.  It's important that you check the list of admins before every labtest because neither the lab monitor nor tech staff will be able to restore a students files.   After selecting your name from the admin list, enter your system password.   Next, under "Restore Machine", a dropdown box lists all the machines where the student has been.  Select a machine from which you wish to restore the students files, and click "OK".  
Line 1484: Line 1730:
 Access the Labtest Cloud URL here: Access the Labtest Cloud URL here:
  
-  * https://webapp.eecs.yorku.ca/ltcloud?id=<your labtest ID>+  * https://webapp.eecs.yorku.ca/ltcloud 
 + 
 +The best way to access ltcloud is directly from a web browser when you are connected to [[https://remotelab.eecs.yorku.ca|EECS Remotelab]]. 
 +If you want to access LTCloud directly from your home PC, you can use [[https://www.yorku.ca/uit/faculty-and-staff-services/internet-access/#vpn|York VPN]].
  
-Note that if you are accessing this URL from a non-EECS IP address (such as from home), you must be connected to [[https://staff.computing.yorku.ca/internet-access/secure-remote-access/|York VPN]] in order to to use the service. 
-  
 After connecting to the Labtest Cloud URL, you will be required to authenticate with your EECS username and password.  After you successfully authenticate, the system will take about 10 seconds to setup your Labtest Cloud instance.  Click on the "Connect to Labtest Cloud" button, and, right from your web browser, you'll be connected to a virtual system running labtest!  You will be logged in as "ltstu" (labtest student) which is a ugrad account.  Testing as a student is the best way to test your labtest. After connecting to the Labtest Cloud URL, you will be required to authenticate with your EECS username and password.  After you successfully authenticate, the system will take about 10 seconds to setup your Labtest Cloud instance.  Click on the "Connect to Labtest Cloud" button, and, right from your web browser, you'll be connected to a virtual system running labtest!  You will be logged in as "ltstu" (labtest student) which is a ugrad account.  Testing as a student is the best way to test your labtest.
  
services/labtest/start.1737996888.txt.gz · Last modified: by jas