EOX GitLab Instance

Vagrantfile 3.18 KB
Newer Older
1
2
3
# -*- mode: ruby -*-
# vi: set ft=ruby :

4
5
6
7
8
9
10
11
12
# Change me! (every time you want to build a different RPM) And make sure somebody
# wrote a identically named puppet module. See puppet/modules for a list of 
# available modules
project = 'eox-release'

#
# You should not need to change anything below this line!
#

13
14
15
16
17
18
19
20
21
22
23
24
25
Vagrant::Config.run do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # This box is a minimal install of centos 6.3  
  config.vm.box = "centos63"
  config.vm.box_url = 'http://puppet-vagrant-boxes.puppetlabs.com/centos-63-x64.box'
  config.vm.host_name = "centos-63-64-rpmbuild.vagrant"
  config.vm.customize ["modifyvm", :id, "--memory", 1024]

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
26
  #config.vm.box_url = "http://domain.com/path/to/above.box"
27
28

  # Boot with a GUI so you can see the screen. (Default is headless)
29
  #config.vm.boot_mode = :gui
30
31
32
33
34

  # Assign this VM to a host-only network IP, allowing you to access it
  # via the IP. Host-only networks can talk to the host machine as well as
  # any other machines on the same network, but cannot be accessed (through this
  # network interface) by any external networks.
35
  #config.vm.network :hostonly, "192.168.33.10"
36
37
38
39

  # Assign this VM to a bridged network, allowing you to connect directly to a
  # network using the host's network device. This makes the VM appear as another
  # physical device on your network.
40
  #config.vm.network :bridged
41
42
43

  # Forward a port from the guest to the host, which allows for outside
  # computers to access the VM, whereas host only networking does not.
44
  #config.vm.forward_port 80, 8088
45
46
47
48
49

  # Share an additional folder to the guest VM. The first argument is
  # an identifier, the second is the path on the guest to mount the
  # folder, and the third is the path on the host to the actual folder.
  # config.vm.share_folder "v-data", "/vagrant_data", "../data"
50
51
52
53
  config.vm.share_folder "specs", "/home/vagrant/rpmbuild/SPECS", "build/SPECS"
  config.vm.share_folder "sources", "/home/vagrant/rpmbuild/SOURCES", "build/SOURCES"
  config.vm.share_folder "rpms", "/home/vagrant/rpmbuild/RPMS", "build/RPMS"
  config.vm.share_folder "srpms", "/home/vagrant/rpmbuild/SRPMS", "build/SRPMS"
54
55
56
57
58

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file rpmbuild.pp in the manifests_path directory.
59
  config.vm.provision :puppet, :facter => { "project" => project } do |puppet|
60
61
62
    puppet.manifests_path = "puppet/manifests"
    puppet.manifest_file  = "rpmbuild.pp"
    puppet.module_path = "puppet/modules"
63
    puppet.facter
64
65
66
67
68
69
70
71
72
73
  end

  # Auto update guest additions, to use this, please install vagrant-vbguest
  # vagrant gem install vagrant-vbguest
  Vagrant::Config.run do |config|
    # set auto_update to false, if do NOT want to check the correct additions
    # version when booting this machine
    #config.vbguest.auto_update = false
  end
end