I'm trying to standardize my project development setup using Vagrantfiles
such that project components may be installed on multiple virtualization
platforms - Virtual Box, VMware, Parallels, ... - as well as in Docker
containers. Project components will be developed on separate VMs, then
integrated for production using Docker containers on another VM.
*For development of components:*
- I have created minimal base boxes for all platforms, and add Provider
definitions for each in the Vagrantfile of components. Components are then
Provisioned with Puppet. This is the typical way Vagrant is used.
*For production (integration of components):*
- The aim is to the have the production Vagrantfile's Provisioner
(Puppet) execute component Vagrantfiles on the VM. These will create Docker
containers for each project component and Provision with Puppet. I believe
this will require a Docker Provider, similar to Fabio Rehm's attempt
(github.com/fgrehm/docker-provider). However, it seems as though it is not
possible to provision the Docker container ('machine mode') through Vagrant
using this project.
*My queries:*
1. Has anybody else attempted something similar? What are your comments
on this approach?
2. Is it necessary to install Vagrant on the production VM to execute
the Docker Vagrantfiles? Or is it possible to use the Vagrant installation
on the hypervisor to provision internal Vagrantfiles over SSH?
3. As this use case shows, I would have thought that Docker is more of a
Vagrant Provider than a Provisioner, though perhaps I am misunderstanding
something?
Any advice would be greatly appreciated.
Thanks,
Slicer
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
