forked from freedomofpress/securedrop
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Vagrantfile
161 lines (149 loc) · 7.7 KB
/
Vagrantfile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Added snap.rb file holds the digital ocean api token values
# so we do not accidently check them into git
require_relative 'snap.rb'
include MyVars
Vagrant.configure("2") do |config|
# Vagrant 1.7.0+ removes the insecure_private_key by default
# and substitutes a dynamically generated SSH key for each box.
# Unfortunately this breaks Ansible provisioning with Vagrant,
# so the key insertion feature should be disabled.
config.ssh.insert_key = false
config.vm.define 'development', primary: true do |development|
development.vm.hostname = "development"
development.vm.box = "trusty64"
development.vm.network "forwarded_port", guest: 8080, host: 8080
development.vm.network "forwarded_port", guest: 8081, host: 8081
development.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
development.vm.provision "ansible" do |ansible|
ansible.playbook = "install_files/ansible-base/securedrop-development.yml"
ansible.skip_tags = [ "non-development" ]
ansible.verbose = 'v'
end
development.vm.provider "virtualbox" do |v|
v.name = "development"
# Running the functional tests with Selenium/Firefox has started causing out-of-memory errors.
#
# This started around October 14th and was first observed on the task-queue branch. There are two likely causes:
# 1. The new job queue backend (redis) is taking up a significant amount of memory. According to top, it is not (a couple MB on average).
# 2. Firefox 33 was released on October 13th: https://www.mozilla.org/en-US/firefox/33.0/releasenotes/ It may require more memory than the previous version did.
v.memory = 1024
end
end
# The staging hosts are just like production but allow non-tor access
# for the web interfaces and ssh.
config.vm.define 'mon-staging', autostart: false do |staging|
staging.vm.hostname = "mon-staging"
staging.vm.box = "trusty64"
staging.vm.network "private_network", ip: "10.0.1.3", virtualbox__intnet: true
staging.hostmanager.aliases = %w(securedrop-monitor-server-alias)
staging.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
staging.vm.synced_folder './', '/vagrant', disabled: true
staging.vm.provider "virtualbox" do |v|
v.name = "mon-staging"
end
end
config.vm.define 'app-staging', autostart: false do |staging|
staging.vm.hostname = "app-staging"
staging.vm.box = "trusty64"
staging.vm.network "private_network", ip: "10.0.1.2", virtualbox__intnet: true
staging.vm.network "forwarded_port", guest: 80, host: 8082
staging.vm.network "forwarded_port", guest: 8080, host: 8083
staging.vm.synced_folder './', '/vagrant', disabled: true
staging.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
staging.vm.provider "virtualbox" do |v|
v.name = "app-staging"
# Running the functional tests with Selenium/Firefox has started causing out-of-memory errors.
#
# This started around October 14th and was first observed on the task-queue branch. There are two likely causes:
# 1. The new job queue backend (redis) is taking up a significant amount of memory. According to top, it is not (a couple MB on average).
# 2. Firefox 33 was released on October 13th: https://www.mozilla.org/en-US/firefox/33.0/releasenotes/ It may require more memory than the previous version did.
v.memory = 1024
end
staging.vm.provision "ansible" do |ansible|
ansible.playbook = "install_files/ansible-base/securedrop-staging.yml"
ansible.verbose = 'v'
# Taken from the parallel execution tips and tricks
# https://docs.vagrantup.com/v2/provisioning/ansible.html
ansible.limit = 'all'
# Quickest boot
#ansible.skip_tags = [ "common", "ossec", 'app-test' ]
# Testing the web application installing local securedrop-app-code deb
# package
#ansible.skip_tags = [ "common", "ossec", 'fpf_repo' ]
# Testing the web app from repo
#ansible.skip_tags = [ "install_local_pkgs", "common", "ossec" ]
# Creating the apparmor profiles
#ansible.skip_tags = [ "grsec", "ossec", "app-test" ]
# Testing the full install install with local access exemptions
# This requires to also up mon-staging or else authd will error
ansible.skip_tags = [ "install_local_pkgs" ]
end
end
# The prod hosts are just like production but are virtualized. All access to ssh and
# the web interfaces is only over tor.
config.vm.define 'mon-prod', autostart: false do |prod|
prod.vm.box = "mon-prod"
prod.vm.box = "trusty64"
prod.vm.network "private_network", ip: "10.0.1.5", virtualbox__intnet: true
prod.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
prod.vm.synced_folder './', '/vagrant', disabled: true
prod.vm.provider "virtualbox" do |v|
v.name = "mon-prod"
end
end
config.vm.define 'app-prod', autostart: false do |prod|
prod.vm.hostname = "app-prod"
prod.vm.box = "trusty64"
prod.vm.network "private_network", ip: "10.0.1.4", virtualbox__intnet: true
prod.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
prod.vm.synced_folder './', '/vagrant', disabled: true
prod.vm.provider "virtualbox" do |v|
v.name = "app-prod"
# Running the functional tests with Selenium/Firefox has started causing out-of-memory errors.
#
# This started around October 14th and was first observed on the task-queue branch. There are two likely causes:
# 1. The new job queue backend (redis) is taking up a significant amount of memory. According to top, it is not (a couple MB on average).
# 2. Firefox 33 was released on October 13th: https://www.mozilla.org/en-US/firefox/33.0/releasenotes/ It may require more memory than the previous version did.
v.memory = 1024
end
prod.vm.provision "ansible" do |ansible|
ansible.playbook = "install_files/ansible-base/securedrop-prod.yml"
ansible.verbose = 'v'
# the production playbook verifies that staging default values are not
# used will need to skip the this role to run in Vagrant
ansible.skip_tags = [ "validate" ]
# Taken from the parallel execution tips and tricks
# https://docs.vagrantup.com/v2/provisioning/ansible.html
ansible.limit = 'all'
end
end
config.vm.define 'build', autostart: false do |build|
build.vm.box = "build"
build.vm.box = "trusty64"
build.vm.box_url = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
build.vm.provision "ansible" do |ansible|
ansible.playbook = "install_files/ansible-base/build-deb-pkgs.yml"
ansible.verbose = 'v'
#ansible.skip_tags = [ "ossec" ]
end
build.vm.provider "virtualbox" do |v|
v.name = "build"
end
end
# "Quick Start" config from https://github.com/fgrehm/vagrant-cachier#quick-start
#if Vagrant.has_plugin?("vagrant-cachier")
# config.cache.scope = :box
#end
# This is needed for the Snap-ci to provision the digital ocean vps
config.vm.provider :digital_ocean do |provider, override|
override.ssh.private_key_path = "/var/snap-ci/repo/id_rsa"
override.vm.box = 'digital_ocean'
override.vm.box_url = "https://github.com/smdahlen/vagrant-digitalocean/raw/master/box/digital_ocean.box"
provider.token = SNAP_API_TOKEN
provider.image = 'snapVagrantSSHkey'
provider.region = 'nyc2'
provider.size = '512mb'
end
end