kolla-ansible/contrib/dev/vagrant/Vagrantfile.custom.example
Juan J. Martinez 056ecc55ea Update Vagrant dev environment
- Updated Ubuntu image to use 16.04.
 - VirtualBox provider to use centos/7 image + vagrant-vbguest plugin.
 - Improved docs so it is clear that vagrant-vbguest plugin is only
   required with VirtualBox.
 - Clarified comment and made it independent of the release.
 - Refactored the kolla and kolla-ansible paths to be based on the
   username used by Vagrant, that can change depending on the image.

Change-Id: I23d84dcc3297c43eb12eff9c443d282281fc6c82
2017-06-12 07:33:40 +00:00

98 lines
2.4 KiB
Ruby

# -*- mode: ruby -*-
# vi: set ft=ruby :
# This file is an example of Vagrant configuration.
# Copy it to Vagrantfile.custom and configure it to your liking to customize
# the Vagrant deployment. The Vagrantfile.custom file is sourced by the
# Vagrantfile, it has to be valid ruby code.
# Either libvirt or virtualbox
# PROVIDER = "libvirt"
# Either centos or ubuntu
# DISTRO = "centos"
# The libvirt graphics_ip used for each guest. Only applies if PROVIDER
# is libvirt.
# GRAPHICSIP = "127.0.0.1"
# Provisioning other boxes than the default ones may therefore
# require changes to bootstrap.sh.
# PROVISION_SCRIPT = "bootstrap.sh"
# The bootstrap.sh provisioning script requires CentOS or Ubuntu; see below
# for the supported versions for each provider.
#
# kolla and kolla-ansible will be mounted in $HOME and the username depends
# on the image.
#
# PROVIDER_DEFAULTS = {
# libvirt: {
# centos: {
# base_image: "centos/7",
# bridge_interface: "virbr0",
# vagrant_shared_folder: "/home/vagrant/sync",
# sync_method: "nfs",
# username: "vagrant"
# }
# },
# virtualbox: {
# centos: {
# base_image: "centos/7",
# bridge_interface: "wlp3s0b1",
# vagrant_shared_folder: "/home/vagrant/sync",
# sync_method: "virtualbox",
# username: "vagrant"
# },
# ubuntu: {
# base_image: "ubuntu/xenial64",
# bridge_interface: "wlp3s0b1",
# vagrant_shared_folder: "/home/vagrant/sync",
# sync_method: "virtualbox",
# username: "ubuntu"
# }
# }
# }
# Whether the host network adapter is Wi-Fi.
# On VirtualBox, the user must first manually create a NAT-Network
# named OSNetwork. The default network CIDR must be changed.
# The Neutron external interface will be connected to this Network.
# WIFI = false
# Whether to do Multi-node or All-in-One deployment
# MULTINODE = false
# The following is only used when deploying in Multi-nodes
# NUMBER_OF_CONTROL_NODES = 3
# NUMBER_OF_COMPUTE_NODES = 1
# NUMBER_OF_STORAGE_NODES = 1
# NUMBER_OF_NETWORK_NODES = 1
# NODE_SETTINGS = {
# aio: {
# cpus: 4,
# memory: 4096
# },
# operator: {
# cpus: 1,
# memory: 1024
# },
# control: {
# cpus: 1,
# memory: 2048
# },
# compute: {
# cpus: 1,
# memory: 1024
# },
# storage: {
# cpus: 1,
# memory: 1024
# },
# network: {
# cpus: 1,
# memory: 1024
# }
# }