Feature: Vagrant Back-end Support
We would like to add support for Vagrant as an Occam execution back-end.
Vagrant makes use of virtualization through other providers such as VirtualBox, KVM, Docker, or VMWare. You define a Vagrant machine in a configuration file, and can start that machine via vagrant up
. A Vagrant back-end would have to be started and stopped much like a docker container typically would.
Adding Vagrant support yields the following possible benefits:
- Simple Windows support. This would resolve simple use cases for #9. We would still need to look into the licensing problem associated with Windows use in this manner.
- Support for Linux kernels / OSs different from the host Occam instance.
- We would be able to reuse work from the Vagrant community with respect to provisioning. Ideally users would use Occam the normal way to resolve dependencies, but some environments may not be able to be created in this way. We could host our own on-site Vagrant Cloud in Occam to handle the concern of archival / repeatability.
Supersedes #5 (closed) :
This would go into the Backend component as several plugins. Some presumptions in Occam's code about Docker's usage may surface. Suddenly all objects have multiple backends that could be used; this could present some UI/UX issue.
Edited by wilkie