Currently, all the below takes place on Krypton (192.168.40.60)
-
for all stopping and starting of vip instances you must be in nathans home directory
+
1. Shut down pixel streaming with `sudo systemctl stop signalling`
-
This stops all instances:
-
```
-
./run_vip_instances.sh stop
-
```
+
2. Shut down all currently running instances of VIP by cding to home `cd ~` and running `./run_vip_instances.sh stop`
-
This starts n number of instances (18 is the max)
-
```
-
./run_vip_instances.sh start <n>
-
```
+
3. `cd /opt/vip/build` and remove old versions of vip with `sudo rm -r Vip_0.9` and `rm Vip_0.9.zip`
+
4. Build the project in UE5 and then Zip the built project folder
-
**Stopping and starting the pixel streaming server**
+
5. Using filezilla or any other protocol for transfering files over ssh, move the zip into Krypton (e.g. into the Downloads folder)
-
This stops pixel streaming:
+
6. Move the file from `~/Downloads` into `/opt/vip/build` using: `sudo mv ~/Downloads/Vip_0.9.zip /opt/vip/build/`
-
```
-
systemctl stop signalling
-
```
+
7. cd into the dir `cd /opt/vip/build`
-
This starts pixel streaming:
-
```
-
systemctl start signalling
-
```
+
8. unzip with `sudo unzip Vip_0.9.zip -d Vip_0.9`
+
9. check it worked with `ls /opt/vip/build/Vip_0.9`
-
**Stopping and starting vip-sentinel (the booking system)**
+
10. run this script in the terminal to make sure the project is executable and that the instance booter is aware of the new folder (shouldnt be necessary if naming is all the same but do it just in case)
-
This stops sentinel:
-
-
```
-
systemctl stop vip-sentinel
```
+
sed -i 's|^UE_BIN=".*"|UE_BIN="/opt/vip/build/Vip_0.9/Vip_0.9/Linux/VIP.sh"|' ~/run_vip_instances.sh
13. Redeploy VIP at `cd ~` with `./run_vip_instances.sh start 18`
+
+
14. Wait for all instances to come online. You can monitor this with `nvtop` and watch for GPU usage to stabilise across all gpus
-
> [!WARNING]
-
> BOOT ORDER: From a state of VIP instances and Pixel streaming both being offline, first boot your VIP instances, wait until their activity is stable (i.e. watch in nvtop) and then launch the pixel streaming server. FIRST VIP THEN PIXEL
+
15. Redeploy pixel streaming with `sudo systemctl start signalling`
