On 16 Jan 2015, at 6:22, Motonori Shindo wrote:
2015-01-16 5:26 GMT+09:00 Andy Zhou <az...@nicira.com>:
On Thu, Jan 15, 2015 at 9:58 AM, Thomas Graf
<tg...@noironetworks.com>
wrote:
We might need to move the providers into the individual vm
definitions
when we start adding more distributions. Due to the outer is
executed
first rule that was fixed earlier.
Make sense. I will make the change.
I used to be opposed to using config.vm.define block as it was simply
a
single machine setup, not a multi-machine setup. Another reason I was
against it was when it is extended to a multi-flavor environment (as a
matter of fact, I am working on it right now)
You may find something re-usable here:
https://github.com/dave-tucker/ovs-vagrant
At the time I put this together, the plan was to provide a set of boxes
with the build toolchain installed.
One minor difference being that I'm using puppet to provision the VMs
instead of inlining the shell script.
BTW, do you really think we should run all these provisioning commands
as
"root"? I personally prefer to execute it with "privileged: false" by
default and sudo for only commands that requires root privilege. Will
you
give me more rationale behind your proposed change?
The default behaviour is for shell scripts to be run as root by default.
I've never seen a reason to change this in any project where I've used
Vagrant before.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
