Re: [vagrant-up] Is Vagrant appropriate for setting up non-virtual machine environments?

on top of the replies you got, can I ask: - what do you will like to use vagrant for? I am interested to hear more, can you share a couple of test cases of what you think? Thanks On Fri, Jul 11, 2014 at 3:38 AM, Matthew Krieger wrote: > Is there anything about Vagrant that makes it inappropr

Re: [vagrant-up] How to run provisioners after specific events

The vagrant file for multiple machines is processes top to bottom so your vms will be created like: master slave-1 slave-2 slave-3 in my very particular case, I do oracle rac cluster, so I did a reverse counter so my vms are created like node3 node2 node1 and node1 does the magic will this w

Re: [vagrant-up] SSL read error

Hello Try to download the box manually from that link, and then add it locally. If the box is on a non-paid dropbox account, it may be fail due load. alvaro. On Thu, Jul 10, 2014 at 7:05 PM, Martin Rumánek wrote: > Hi! > > I have this error,can anyone help me with this? > > Bringing machine

Re: [vagrant-up] vagrant-git - to get project and its vm ready for development

Hello, My humble opinion here.. if you can add something that create branches or just commits after 10 minutes or something will be awesome if sense there is a remote git server, say it create a branch 20140711 and push the commits there, I can then start from where It was left after the crash :)

Re: [vagrant-up] CentOS 7 - x86_64 Minimal basebox

Hello, on RedHat 7 at least wasn't an easy way to load VirtualBox additions into the VM, so no shared folders. I haven't buid a Centos 7 yet, but if you want to give it a try, use packer and this template+kickstar as start. You need to modify the bits to Centos ISO and md5sum https://github.com/

[vagrant-up] vagrant-git - to get project and its vm ready for development

Hello everyone, after i crashed my vagrant development environment today i had the idea to implements a liitle command tool that checkout a project and its related vagrant project and run vagrant up/provision to get a environment with all dependencies needed by this project. What do you think

[vagrant-up] Hyperv generation 2

Can Vagrant handle Hyper-V Gen 2? I created a new box got it up and running and vagrant added the box. That went fine. Vagrant init worked fine. When I vagrant up the new virtual machines gets created, but as a Gen 1 and this causes issues. It correctly creates the disk as a SCSI disk, but

[vagrant-up] Hyper-V Generation 2 systems

Not sure if any one else had this issue, but if you try to vagrant up a generation 2 system in hyperv it will create a generation 1 machine. Is this an issue with vagrant or something else. I have CentOS 7 working in a hyperv gen 2 instance, but once I packaged it up, added the box, and tried

[vagrant-up] Re: Unable to assign MAC address from Ruby hash & array to public_network

I did some voodoo and got this working. -- 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 vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://group

Re: [vagrant-up] Re: Bindler is deprecated, how to hard require plugins?

I would love to see bindler coming back to newer vagrant versions! Bindler I miss you :-/ ​P.S.: I guess we have to nag @mitchellh a bit more about this ;-) https://github.com/mitchellh/vagrant/issues/3468 ​ On Thu, Jul 10, 2014 at 9:03 PM, Reuben Avery wrote: > Yeah, I was hoping for someth

Re: [vagrant-up] Re: Is Vagrant appropriate for setting up non-virtual machine environments?

@Matthew: vagrant-managed-servers is an approach to this, it basically makes `up` and `destroy` noops but lets you use the other vagrant commands such as `provision` and `ssh`: https://github.com/tknerr/vagrant-managed-servers HTH, Torben On Thu, Jul 10, 2014 at 6:24 PM, wrote: > Vagrant is u

[vagrant-up] Re: Bindler is deprecated, how to hard require plugins?

Add something like this to your Vagrantfile: unless Vagrant.has_plugin?('vagrant-host') raise 'Required plugin vagrant-host is not found.' end This will prevent a vagrant up from occurring until the plugin is installed & found. -- You received this message because you are subscribed to the G

Re: [vagrant-up] Re: Bindler is deprecated, how to hard require plugins?

Yeah, I was hoping for something a bit nicer than that. I'd like to tie in to the message queue that Vagrant builds, adding a message like ==> default: Error: Vagrant module "foo" is required for provisioning. Aborting. On Jul 10, 2014, at 2:56 PM, bmurt...@coredial.com wrote: > Add somethin

[vagrant-up] Bindler is deprecated, how to hard require plugins?

I was pleased to discover Bindler but it's abandoned and doesn't seem to want to work Running Bindler 0.1.4 on Vagrant 1.6.3-- $ vagrant bindler setup Vagrant failed to initialize at a very early stage: The plugins failed to load properly. The error message given is shown below. cannot load su

[vagrant-up] Re: Is Vagrant appropriate for setting up non-virtual machine environments?

Vagrant is used to quickly spin up, provision, and destroy (and rinse-repeat) VMs for development, testing, etc. You can install Vagrant on a physical server and spin up Vagrant VMs (which is probably what most ppl do) and provision servers as needed to your specifications. If you had a virtual

[vagrant-up] Unable to assign MAC address from Ruby hash & array to public_network

Hi ya'll, So in my Vagrantfile, I have an array of hashes for various VMs that are needed to boot our environment. There is also a corresponding Ruby hash of name & MAC addresses that are required for proper DHCP IP assignment. If I explicitly declare a MAC address *node_config.vm.network :publ

[vagrant-up] Is Vagrant appropriate for setting up non-virtual machine environments?

Is there anything about Vagrant that makes it inappropriate for use in physical (non-virtual machine) environments? I see that most of the verbiage in the docs etc about Vagrant is about VMs. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsu

[vagrant-up] CentOS 7 - x86_64 Minimal basebox

Has anyone built and shared or have a location of a shared one ? Cheers, Tony 'Thinking of getting a Kittel Cut' R. -- 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

[vagrant-up] How to run provisioners after specific events

Hi, I have a master node which is being provisioned using Puppet. After its provisioning is finished, there are 3 others slave nodes which are being provisioned in a similar fashion. What I want to do is run a provisioner (shell, Puppet) on the master node, but after the 3 slaves have been alr

[vagrant-up] SSL read error

Hi! I have this error,can anyone help me with this? Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'https://dl.dropboxusercontent.com/s/xymcvez85i29lym/vagrant-debian-wheezy64.box' could not be found. Attempting to find and install... default: Box Provider: vi

Re: [vagrant-up] Can't get MongoDB to work with shared folders

You don't want to try nfs :) Not according to the MongoDB employee that spent three days with us at work this week.[1] The MongoDB docs also specifically state that HGFS and vbox shared folders will no