aboutsummaryrefslogtreecommitdiff
path: root/dev/vagrant/Vagrantfile.custom.example
AgeCommit message (Collapse)AuthorFilesLines
2016-10-14Move demos and dev directory into a new contrib directoryChristian Berendt1-92/+0
TrivialFix Change-Id: Ifb8f19afa1514488bd288670d08b96f84982a4e1
2016-03-21Attach external NIC to a NAT-Network if on Wi-FiAndrei-Lucian Șerb1-0/+6
On computers with wi-fi adapters, promiscuous mode on the VirtualBox (or maybe other hypervisors as well) NICs does not work, which means the default way of connecting the Neutron external interface to a bridged adapter, will not allow communication to and from the Nova VMs over floating IPs with any computer on the external network (except the host computer) or with the wi-fi router. This means no ability to connect to the Nova VMs and no internet access inside the Nova VMs. According to VirtualBox documentation (excerpt): "Bridging to a wireless interface is done differently from bridging to a wired interface, because most wireless adapters do not support promiscuous mode. All traffic has to use the MAC address of the host’s wireless adapter, and therefore VirtualBox needs to replace the source MAC address in the Ethernet header of an outgoing packet to make sure the reply will be sent to the host interface. When VirtualBox sees an incoming packet with a destination IP address that belongs to one of the virtual machine adapters it replaces the destination MAC address in the Ethernet header with the VM adapter’s MAC address and passes it on. VirtualBox examines ARP and DHCP packets in order to learn the IP addresses of virtual machines." To fix this issue, a new flag has been introduced: WIFI. If true, the default Vagrant public network is not created anymore. Instead, the 3rd NIC will be connected to a NAT-Network named OSNetwork. The NAT-Network has a virtual gateway, which will be used to communicate with the external physical wi-fi router. Since Vagrant does not have a high-level mechanism to attach an adapter to a NAT-Network, the code uses the low-level Vagrant construct vm.customize which makes it provider specific. Promiscuous mode is now activated by default on the 3rd NIC. The WIFI flag is false by default. This commit only addresses VirtualBox, and it is currently unknown if the problem described and fixed in this commit is present in other hypervisors. DocImpact Closes-Bug: #1558766 Change-Id: I0b4dbbc562d87191b2179f47b634cdd6f6361a5e Signed-off-by: Andrei-Lucian Șerb <lucian.serb@icloud.com>
2016-03-15Unify vagrant bootstrap.sh scriptsDaniel Gonzalez1-3/+5
Merge the vagrant bootstrap scripts for centos and ubuntu into a single file. Change-Id: Ia07931b4717cd393fe51141907fc561166cc05e4 Closes-Bug: 1554140
2016-03-02Make Vagrant libvirt graphics_ip configurableÉric Lemoine1-0/+4
TrivialFix Change-Id: I5c6153016f15b8a0922bdb28c4a03de561b240ee
2016-02-22Harmonise vagrant provider defaultsDaniel Gonzalez1-5/+5
Ensure that provider defaults of libvirt and virtualbox use the same paths and provisioning scripts. Change-Id: Ie968b118aa0540204751c348ef3408a6fe24d32a Partial-Bug: #1547114
2016-02-22Change ubuntu base_image for vagrant to wily64Daniel Gonzalez1-1/+1
The ubuntu-bootstrap.sh script tries to install the packet linux-image-generic-ls-wily when the kernel version is older than 4.2. This fails when using the default base image ubuntu/vivid64. Therefore this patch updates the base_image to ubuntu/wily64. Change-Id: Ieaf2d35a9a4304de2d1d78d8245d115dcb32bb0e Partial-Bug: #1547114
2015-11-18Allow to customize vagrant deploymentMartin André1-0/+80
Extract the Vagrantfile configuration to a Vagrantfile.custom file, to permit easy customization of the Vagrant deployment without the need to modify a file under version control. Closes-Bug: #1517475 Change-Id: I03e3ef373ec47e3d622b77fa9cf88748db99adaa