...
- Run batch (pipeline) jobs using Gleam, both for MC generation and for real data reconstruction
- Build Gleam and related software (need access to legacy compiler, external libs) e.g. via Release Manager
- Provide interactive development environment for Gleam programmers (interactive login, editor, debugger, etc.).
- Allow for creation and installation of new version of VM including, for example, new build of Gleam
What should a batch job do?
...
Resource access and security
For the VM to do anything useful, it our intended uses VMs must have input from the outside world and must be able to write output somewhere which is accessible to non-VMs. However , however the VM is perhaps running an unpatched legacy OS with known security holes.
There is no need for the VMs to be general purpose machines. Restrictions like the following should keep the machines (and other SLAC resources) from being trashed without interfering with the functions we require.
- VMs should not have write access to any "regular" public space (space to which centrally-supported public log-in machines also have access).
- VMs need have no access at all to regular user home directories.