1ebbb7f19b
A couple of comments during my latest CORS review indicated that there is a misunderstanding on why the Vagrantfile in ironic exists. In those comments, the assumption appeared to be that vagrant is used to provision ironic, not just the development resources necessary to work on ironic. This patch adds documentation to clarify that. Change-Id: I7d71adaba402a62343d1e0399ee53410b76c973f
32 lines
985 B
Ruby
32 lines
985 B
Ruby
# -*- mode: ruby -*-
|
|
# vi: set ft=ruby :
|
|
|
|
# WARNING: This Vagrantfile is for development purposes only. It is intended to
|
|
# bootstrap required services - such as mysql and rabbit - into a reliably
|
|
# accessible VM, rather than forcing the engineer to install and manage these
|
|
# services manually. This Vagrantfile is not intended to assist in provisioning
|
|
# Ironic. For that, please use the bifrost project.
|
|
|
|
VAGRANTFILE_API_VERSION = '2'
|
|
|
|
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
|
|
|
|
config.vm.box = 'ubuntu/trusty64'
|
|
|
|
config.vm.define 'ironic' do |ironic|
|
|
ironic.vm.provider :virtualbox do |vb|
|
|
vb.customize ['modifyvm', :id, '--memory', '512', '--cpuexecutioncap', '25']
|
|
end
|
|
|
|
ironic.vm.network 'private_network', ip: '192.168.99.11' # It goes to 11.
|
|
|
|
ironic.vm.provision 'ansible' do |ansible|
|
|
ansible.verbose = 'v'
|
|
ansible.playbook = 'vagrant.yml'
|
|
ansible.extra_vars = {
|
|
ip: '192.168.99.11'
|
|
}
|
|
end
|
|
end
|
|
end
|