vm flag and wip vsh rework

Signed-off-by: Ava Hahn <a.hahn@f5.com>

README.md

@@ -8,8 +8,12 @@ This is a set of scripts that roughly does the following:
 
 ## Prerequisites
 - SECRET.sh must contain the following
-  - USERN=<username on your VMs> 
-  - PASSP=<password for said user>
+```sh
+USERN= # username on your VMs
+PASSP= # password for said user
+VM_PARALLEL= # number of CPU cores a VM has
+HOST_PARALLEL= # number of CPU cores to build with locally on the hypervisor
+```
 - sshpass, virsh, libvirt, etc
 - cloned repos of nginx, nginx-tests, and nginx-otel
 
@@ -53,3 +57,26 @@ Invoke `test.sh` with some or all of the following flags:
 
 Logs are in logging directory shown. They are split out into files per VM per phase.
 User may set test_log_dir to provide their own logging directory.
+
+When running, you may view the combined status using a command like one of the following.
+The logging dir will be specified in the first second of output from the test.sh script.
+```sh
+tail -f <LOGGING DIR>/on*
+tail -f <LOGGING DIR>/sync*
+tail -f <LOGGING DIR>/build_nginx*
+tail -f <LOGGING DIR>/build_otel*
+tail -f <LOGGING DIR>/test_nginx*
+tail -f <LOGGING DIR>/test_otel*
+tail -f <LOGGING DIR>/off*
+```
+
+Additionally, virt.sh and nginx.sh can be sourced in a shell profile so that their
+functions can be used at terminal prompt. For example, sourcing virt.sh will provide
+the `vsh` function which turns on a VM, opens an SSH connection to it, and then turns it off again. Functions such as `vms_avail`, `vms_on`, and `vms_off` may also be of use.
+
+In the future, routines will be added to nginx.sh that automate several local development and testing processes.
+
+# Contributions
+Any contributions which make the procedures defined in these scripts portable across
+shells and platforms is welcomed. Any additional feature add for any enclosed script
+is also welcomed.