如何在vagrant和puppet之间共享主机文件

Question

I am currently converting a large number of EC2 instances to a series of puppet scripts and then using Vagrant to virtualise the rig for local development.

I have gotten stuck on managing the network in vagrant and mapping that onto production.

First I have something like this:

# Main Web Server
config.vm.define :app do |app_config|
    app_config.vm.host_name = "web1"
    app_config.vm.network :hostonly, "10.0.0.2"
    app_config.vm.box = "precise64"

    ...etc
        puppet.manifest_file = "persist/web.pp"
end 

# First DB server
config.vm.define :db1 do |db1_config|
    db1_config.vm.host_name = "db1"
    db1_config.vm.network :hostonly, "10.0.0.3"
    db1_config.vm.box = "precise64"
    ...etc
        puppet.manifest_file = "persist/db.pp"
end

etc.

Then in this case web.pp and db.pp are reasonably simply they just setup python, uwsgi, nginx, mysql etc.

So the problem: I need inside for example puppet/modules/hosts/files/hosts have to specify something like:

10.0.0.3    db1.X.com
10.0.0.4    db2.X.com
etc.

In production we use a combination of our sites DNS and ec2 instances DNS records (which I cant put into hosts). Typically our haproxy hosts have a public DNS record and they hold the EC2 names in their config (which makes using a hosts file impossible).

So how can I build a file that both puppet and vagrant can import and use a global mapping such as:

hosts = {
         web => 10.0.0.2,
         db1 => 10.0.0.3,
         db2 => 10.0.0.4,
}

Which I can access from within puppet templates for example haproxy.cfg but also access from within Vagrant files so i can set vm.network to it as well.

Restrictions:

• Cannot be IP only, must be symbolic name to either IP or DNS
• Cannot use a puppet master (unfortunately not flexible on this one).
• Virtualising the DNS server as well seems messy so id rather not.

Also I am really new to ruby, if you provide examples (which would be great) please describe it enough for me to be able to find my way through the ruby docs.

Answer 1

2 Options:

1) You can have vagrant read a hash that you shown from a file ( placed in it's dir, DB, whatever ) and then generate Vagrantfile using that content. Vagrant's config just runs some ruby code ( i think ) if not

2) Have a shell script generate Vagrantfile and/or puppet config / static file.

Implementation details are trivial.