From e2c43c6875303baad8cc70d4908c38ee228e564c Mon Sep 17 00:00:00 2001 From: "Z. Cliffe Schreuders" Date: Fri, 22 Mar 2019 10:57:58 +0000 Subject: [PATCH] Guidance to create SecGen base boxes (#127 #138 #135) --- README-Creating-Bases.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 README-Creating-Bases.md diff --git a/README-Creating-Bases.md b/README-Creating-Bases.md new file mode 100644 index 000000000..6306a1eab --- /dev/null +++ b/README-Creating-Bases.md @@ -0,0 +1,18 @@ +# Creating new SecGen bases + +We encourage you to use the existing bases when developing scenarios. Introducing new base boxes require careful thought and testing of modules for compatibility. This guide is mostly indended for those who wish to extend SecGen onto further VDI platforms (in addition to VirtualBox, and oVirt), which involves recreating our existing base images on these other platforms. + +When creating base images for SecGen, follow [guidelines on creating Vagrant base boxes](https://www.vagrantup.com/docs/boxes/base.html), with these additional considerations. + +## Make sure these packages are installed on every base +- puppet +- curl + +Install VM guest tools software, to enable copy-paste between VMs, graphics, etc. + +## Avoid SecGen leaving extra files on the VMs +You should have these directories mounted as tmpfs, so that the files used by Vagrant to provision the VMs (including puppet files, SecGen module names, etc), don't get accidental left on the VMs that are generated. +- /tmp/ +- /vagrant/ + +This can be achieved via /etc/fstab