Hi all, ive just recently been reading through the vagrant docs and have a
few quesitons about organization and using one set of vagrant configs from
different users on different PCs.
I read that loading other vagrant files is possible so you can chain them,
so my thoughts were to do the following structure
/environment_name/
|-> common/
|-> servers/
|-> <hostnames ...>/
|-> app_groups/
|-> <groupname ...>/
The idea being that each level has a vagrant file, the environment
directory includes all vagrant files servers, servers include only common,
and app groups include specific servers.
The rationale for such a setup is that I want to use this for dev,prod, and
disaster recovery by having multiple ops users working off the same git
repo, but im concerned that they might run 'vagrant down' in a production
setting if I do just one giant vagrant file. My hope is with this I can
tell them never run commands from within env dir unless in disaster
recovery or some automated Jenkins env rebuild type scenario and always use
individual server or app group directories otherwise. That way if they dont
explicitly specify the host or whatever they dont break a production
environment only a smaller subset.
My concerns are primarily with vagrant states and how that would work with
multiple users using the same code. I understand that the global state is
per user, but what if I did a vagrant up under the hostname dir for server
and then went into an app group that also contained it and tried to run a
vagrant down/destroy/status would this even work or would it have problems
with the state? What if one user ran vagrant up on a host and another user
tried to do vagrant down/status/destroy would state cause a problem here?
Would either of these two scenarios behave differently based on whether its
run against Vbox/VMWare vs a cloud provider?
Id appreciate any thoughts/recommendations,
Thanks,
--
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.
