You can pretty well ignore the salt provisioning setup.
-----
# -*- mode: ruby -*-
# vim: ft=ruby:et:sw=2:ts=8:sts=2
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "mokote/debian-7"
config.vm.network "public_network"
config.vm.hostname = "dev"
config.vm.synced_folder "states/", "/srv/salt"
config.vm.synced_folder "pillar/", "/srv/pillar"
config.vm.provision :salt do |salt|
salt.install_master = true
salt.run_highstate = false # love to, but it's broken in current vagrant
salt.minion_config = "dev/minion"
salt.minion_key = "dev/minion.key"
salt.minion_pub = "dev/minion.pem"
salt.master_config = "dev/master"
salt.master_key = "dev/master.key"
salt.master_pub = "dev/master.pem"
salt.seed_master = { :dev => salt.minion_pub }
end
end
On Thu, Oct 9, 2014 at 2:13 PM, Alvaro Miranda Aguilera <[email protected]>
wrote:
> can you share your Vagrantfile?
>
> feelfree to change the bridge ip is you like
>
> On Fri, Oct 10, 2014 at 10:09 AM, Travis Parker <[email protected]>
> wrote:
>
>>
>> On Thu, Oct 9, 2014 at 2:06 PM, Alvaro Miranda Aguilera <
>> [email protected]> wrote:
>>
>>> the machines where are you testing these are on the same network?
>>>
>> yes, there is only a single machine involved. I'm trying to communicate
>> between the VM and it's own host machine.
>>
>>>
>>> if they are not on the same network, you would need to setup a gw/router
>>> on the guest vm
>>>
>>> On Fri, Oct 10, 2014 at 8:34 AM, Travis Parker <[email protected]>
>>> wrote:
>>>
>>>> Hello vagrant-up,
>>>>
>>>> I've tried 3 different debian wheezy images now (chef/debian-7.6,
>>>> chef/debian-7.4, and mokote/debian-7) and can't get any of them to have
>>>> basic network connectivity through a public_network/bridged device.
>>>>
>>>> My super simple test is:
>>>>
>>>> vagrant@box$ ip addr
>>>> <copy the eth1 IPv4 address, should be in the same subnet as the host>
>>>> vagrant@box$ nc -l 5000
>>>>
>>>> me@host$ nc <vm ip> 5000
>>>>
>>>> It works as expected with the ubuntu/trusty64 image, so it's not a host
>>>> sysctl or anything.
>>>>
>>>> Any help would be much appreciated!
>>>>
>>>> --travis
>>>>
>>>> --
>>>> 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/d/optout.
>>>>
>>>
>>> --
>>> 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/0xdeAhWEeFc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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/d/optout.
>>
>
> --
> 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/0xdeAhWEeFc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
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/d/optout.
