Hi,

My solution ended up using mounted directories from Vagrant and sharing
uploaded files via the NFS server.

grtz
BjornW

On 30-12-15 08:48, pixel fairy wrote:
> can you show us?
> 
> ive done similar things, but usually use ansibles synchronize module or
> just work from /vagrant
> 
> On Tuesday, December 8, 2015 at 2:54:06 AM UTC-8, Bjorn W wrote:
> 
>     Hi,
>     I'm using Vagrant to model a production environment with 5 machines:
> 
>     - 1 database server
>     - 1 storage server
>     - 2 webservers
>     - 1 loadbalancer.
> 
>     So far most of it works as theorized except for storage.
> 
>     My initial idea was to sync shared folders from my host laptop via
>     Vagrant to the storage server VM and run a NFS server re-sharing the
>     shared Vagrant folders the (guest) from storage server to, in this
>     case, the webservers. However sharing synced (tried both default as
>     well as NFS) Vagrant folders using this approach does not work: the
>     storage server mounts the shared Vagrant folder and allows access to
>     it. I can see a mount and I'm able to write something to it (on the
>     webserver machine and see the result on the storage server as well).
>     However existing folders on the storage server seem empty when I
>     view them from the webserver machine. Any clues on what is causing
>     this? Also I'm interested in how you would model a production
>     environment like I described and in particular how would you share
>     data (between the guest VM's as well as between the host and the
>     guest VM's). 
> 
>     ps: For now I'm going to test a workaround: Using Vagrant shared
>     folders as the storage machine instead. So basically I mount the
>     shared folders on the webserver VM's directly instead of via a
>     storage server.
>      
> 
> -- 
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this
> mailing list.
>  
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vagrant-up/H2xqIBMEoOQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/f3c3e019-8527-47e4-ae5a-50488c1661d6%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/f3c3e019-8527-47e4-ae5a-50488c1661d6%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


-- 

met vriendelijke groet,
Bjorn Wijers

* b u r o b j o r n .nl *
digitaal vakmanschap | digital craftsmanship

Postbus 14145
3508 SE Utrecht
The Netherlands

tel: +31 6 49 74 78 70
http://www.burobjorn.nl

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/56839F8C.1000307%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to