ipng/lab
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
Pim van Pelt
2023-05-06 22:06:56 +00:00
parent ba4a3e9fef
commit 6414b290fa
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -114,7 +114,7 @@ clones are destroyed. Obviously this is the most dangerous operation of the bunc
of the lab is that the VMs can be re-created off of a stable base image and a generated build. of the lab is that the VMs can be re-created off of a stable base image and a generated build.
``` ```
lab:~/src/lab$ LAB=0 ./destroy ## remove VMs and ZFS clones on hvn0.lab.ipng.ch lab:~/src/lab$ LAB=0 ./command destroy ## remove VMs and ZFS clones on hvn0.lab.ipng.ch
``` ```
### Create ### Create
@ -129,7 +129,7 @@ Typically, it's necessary to destroy/create, only when the build or the base ima
the lab can be brought back into a _factory default_ state by rolling back to the `pristine` snapshot. the lab can be brought back into a _factory default_ state by rolling back to the `pristine` snapshot.
``` ```
lab:~/src/lab$ LAB=0 ./create ## create ZFS 'pristine' snapshots and start VMs lab:~/src/lab$ LAB=0 ./create ## create ZFS clones, copy in the build
``` ```
### Pristine ### Pristine
@ -140,6 +140,7 @@ brought back into a default state by rolling back the disks to the `pristine` sn
the virtual machines. the virtual machines.
``` ```
lab:~/src/lab$ LAB=0 ./pristine ## return the lab to the latest 'pristine' snapshot lab:~/src/lab$ LAB=0 ./command start ## Start the VMs
lab:~/src/lab$ LAB=0 ./vishall start ## Start the VMs lab:~/src/lab$ LAB=0 ./command shutdown ## Start the VMs
lab:~/src/lab$ LAB=0 ./command pristine ## return the lab to the latest 'pristine' snapshot
``` ```