vagrant

Commit Graph

Author	SHA1	Message	Date
Fabio Rehm	54656151cf	Convert specs to RSpec 2.14.8 syntax with Transpec This conversion is done by Transpec 1.10.2 with the following command: transpec test/unit/ * 507 conversions from: obj.should to: expect(obj).to * 394 conversions from: == expected to: eq(expected) * 260 conversions from: obj.should_receive(:message) to: expect(obj).to receive(:message) * 85 conversions from: obj.stub(:message) to: allow(obj).to receive(:message) * 25 conversions from: its(:attr) { } to: describe '#attr' do subject { super().attr }; it { } end * 19 conversions from: obj.should_not to: expect(obj).not_to * 7 conversions from: obj.should_not_receive(:message) to: expect(obj).not_to receive(:message) * 3 conversions from: Klass.any_instance.should_receive(:message) to: expect_any_instance_of(Klass).to receive(:message)	2014-03-14 12:02:07 -03:00
Paul Hinze	c25172d0f7	providers/virtualbox: support DHCP interfaces for NFS Previously, we required a host-only interface with a static IP for NFS to work in VirtualBox, because we needed access to the guest's IP in order to properly configure mount commands. After boot, VirtualBox exposes the IP addresses of a guest's network adapters via the "guestproperty" interface. This adds support for reading VirtualBox guest properties to the VirtualBox driver and utilizes that support to prepare NFS settings, which removes the necessity for a static IP for NFS to work. In this commit we also start building out scaffolding for unit testing vbox actions and drivers. Test plan: - Prepare a Vagrantfile with the following: * private network with type: :dhcp * synced folder with nfs: true - Boot a VM from this Vagrantfile using the virtualbox provider - Machine should boot successfully with working synced folder	2013-12-03 10:21:28 -05:00

Author

SHA1

Message

Date

Fabio Rehm

54656151cf

Convert specs to RSpec 2.14.8 syntax with Transpec

This conversion is done by Transpec 1.10.2 with the following command:
    transpec test/unit/

* 507 conversions
    from: obj.should
      to: expect(obj).to

* 394 conversions
    from: == expected
      to: eq(expected)

* 260 conversions
    from: obj.should_receive(:message)
      to: expect(obj).to receive(:message)

* 85 conversions
    from: obj.stub(:message)
      to: allow(obj).to receive(:message)

* 25 conversions
    from: its(:attr) { }
      to: describe '#attr' do subject { super().attr }; it { } end

* 19 conversions
    from: obj.should_not
      to: expect(obj).not_to

* 7 conversions
    from: obj.should_not_receive(:message)
      to: expect(obj).not_to receive(:message)

* 3 conversions
    from: Klass.any_instance.should_receive(:message)
      to: expect_any_instance_of(Klass).to receive(:message)

2014-03-14 12:02:07 -03:00

Paul Hinze

c25172d0f7

providers/virtualbox: support DHCP interfaces for NFS

Previously, we required a host-only interface with a static IP for NFS
to work in VirtualBox, because we needed access to the guest's IP in
order to properly configure mount commands.

After boot, VirtualBox exposes the IP addresses of a guest's network
adapters via the "guestproperty" interface.

This adds support for reading VirtualBox guest properties to the
VirtualBox driver and utilizes that support to prepare NFS settings,
which removes the necessity for a static IP for NFS to work.

In this commit we also start building out scaffolding for unit testing
vbox actions and drivers.

Test plan:
 - Prepare a Vagrantfile with the following:
   * private network with type: :dhcp
   * synced folder with nfs: true
 - Boot a VM from this Vagrantfile using the virtualbox provider
 - Machine should boot successfully with working synced folder

2013-12-03 10:21:28 -05:00

2 Commits