From 04d941ed13d7a4cd8089fecd0e470982a8cb4c6f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A1tvik=20Karanam?=
 <89281036+skara9@users.noreply.github.com>
Date: Fri, 16 Aug 2024 13:43:43 -0400
Subject: [PATCH] Update worker_vm.md

---
 _docs/developer/getting_started/worker_vm.md | 23 +++++---------------
 1 file changed, 5 insertions(+), 18 deletions(-)

diff --git a/_docs/developer/getting_started/worker_vm.md b/_docs/developer/getting_started/worker_vm.md
index e0868d23..d8d920aa 100644
--- a/_docs/developer/getting_started/worker_vm.md
+++ b/_docs/developer/getting_started/worker_vm.md
@@ -53,30 +53,17 @@ machines* in addition to your primary vagrant virtual machine.
 
    When this is finished, you should see the Submitty duck ASCII art for each new worker machine.
 
-6. Verify that all expected machines are running
+6. You can verify that all the worker machines are running with:
    ```
-   vagrant global-status
+   vagrant workers status
    ```
 
-   Which should print out a line for the primary machine, and an additional line for each worker machine:
-
+7. `vagrant ssh` into the main virtual machine and run:
    ```
-   id       name         provider  state     directory                                    
-   ------------------------------------------------------------------------------------
-   abab893  ubuntu-22.04 qemu      running   /SOMETHING/GIT_CHECKOUT/Submitty 
-   0fe6810  worker-1     qemu      running   /SOMETHING/GIT_CHECKOUT/Submitty 
+   refresh_vagrant_workers   # (runs python3 /usr/local/submitty/GIT_CHECKOUT/Submitty/.setup/bin/refresh_vagrant_workers.py)
+   submitty_install
    ```
 
-
-7. Connect to the primary machine and complete the
-
-   NOTE: This is mirroring the manual connection done on the production machine
-
-   http://localhost:4000/sysadmin/installation/worker_installation
-
-
-  `vagrant ssh` into the main virtual machine and do a `submitty_install`
-
 ---
 
 ## Connecting to the Worker Machine