578393ac8e
Add cleanup routine to synced folder plugin implementation
2013-12-02 11:19:09 +01:00
0b9861db7d
providers/virtualbox: fix broken NFS check
2013-11-22 17:29:35 -08:00
35ac7da5a0
providers/virtualbox: don't use NFS middleware anymore
2013-11-22 17:13:53 -08:00
9d3818a380
providers/virtualbox: use new SyncedFolders middleware
2013-11-22 16:21:14 -08:00
0f4ba6dc3b
providers/virtualbox: Run post-boot after boot but before wait for SSH
...
[GH-2048]
2013-08-29 16:44:32 -07:00
261d0ef6cd
core: WaitForCommunicator - more robust wait for boot
...
This is a new built-in middleware that is more robust for
waiting for boots. The "max_tries" configuration is now gone, it is
timeout based. Future commits will make this even better as the
SSH communicator will implement the new "wait_for_ready" in a better
way.
2013-08-29 16:27:00 -07:00
d4c7e20110
core: ProvisionerCleanup task to run cleanup on provisioners
2013-08-29 11:13:43 -07:00
5f34a694f5
VBoxManage customizations can run at different events [GH-1247]
2013-07-23 17:36:47 -05:00
e941c549f2
box_url downloading happens before config validation [GH-1061]
2013-07-10 20:10:33 -07:00
780a312fc9
Built-in DestroyConfirm middleware
2013-04-19 14:14:29 -06:00
88b34d3b71
Message on `up` that VM is already running [GH-1558]
2013-04-08 09:09:23 -07:00
df23c2a8fa
Move guest addition check to later, after boot [GH-1179]
2013-03-21 13:59:13 -07:00
c9ad55d9e7
Built-in hostname middleware for setting hostname
2013-02-27 21:28:09 -08:00
5d82123da9
VirtualBox should use the new port forwarding collision detection stuff
2013-02-26 13:38:00 -08:00
6afb4326fa
Move NFS to a built-in middleware
2013-02-08 15:34:04 -08:00
165dd63f78
New HandleBoxUrl built-in middleware to handlet the "box_url" config
2013-02-01 11:31:08 -08:00
ab4046d8af
Fix issue where set name doesn't work if saved
2013-01-31 11:26:45 -08:00
1392d9b4a5
Detect if a VM name is already taken for VirtualBox
2013-01-30 23:22:45 -08:00
4fa194899d
VirtualBox config: "name" to set the VM name [GH-1126]
2013-01-30 23:03:21 -08:00
9d2f26604e
Properly handle paused VirtualBox VMs [GH-1184]
2013-01-30 22:47:45 -08:00
7c8125905d
Set the proper force halt environment
2013-01-22 13:37:44 -08:00
4780f1c07f
Use the proper env for branching on Halt in VirtualBox
2013-01-22 13:35:52 -08:00
31448c4cd4
Use the new GracefulHalt built-in for VirtualBox
2013-01-22 12:07:37 -08:00
003ebc811c
VirtualBox uses the new validation middleware
2013-01-18 13:29:20 -08:00
5c9f27626c
Provisioner built-in uses new API
2013-01-13 16:09:32 -08:00
84c45a854c
Remove the ProvisionerCLeanup action from VirtualBox
2013-01-13 16:03:34 -08:00
212e634c3b
Make Provision a built-in action.
...
This allows other providers to just use it.
2013-01-12 16:22:37 -08:00
da7f227fff
Forwarded ports use the new high-level configuration
2013-01-11 14:51:49 -08:00
2d8f9baf7f
New Network VirtualBox middleware to handle the changes.
...
Note this is a WIP (hence committed on a branch)
2013-01-11 14:16:00 -08:00
559cf25b5f
Temporarily disable Network action while it is broken
2013-01-04 16:25:20 -10:00
640b296f5a
Explicitly set error handling for port collision on resume
2013-01-04 16:11:40 -10:00
be36c702d6
Booting new VirtualBox VM should check for port collisions
2013-01-04 16:08:37 -10:00
85a4fb82a8
`vagrant package` a single VM works!
2012-08-15 21:04:37 -07:00
b659191a02
`vagrant up`!
2012-08-14 22:38:41 -07:00
aaeb060f33
`vagrant provision`
2012-08-14 21:21:31 -07:00
7aa083d259
`vagrant reload` now works with the new machine abstraction
2012-08-14 21:12:41 -07:00
0cc63c05e2
`vagrant destroy` fully works
2012-08-13 23:31:12 -07:00
2fc18f7207
`destroy` gets a little farther, and properly halts the VM
2012-08-13 23:18:50 -07:00
bca8663742
`vagrant resume` works with the new machine abstraction
2012-08-13 20:03:35 -07:00
83b908f3d8
`vagrant suspend` works with new machine abstraction
2012-08-13 19:30:41 -07:00
5e70ad0ec2
`vagrant ssh -c` now uses a middleware sequence
2012-08-10 00:57:23 -07:00
e0ec679838
`vagrant ssh` with full console works with new provider.
...
This works by now calling the `:ssh` action on the provider. This action
is allowed to do whatever it pleases, but should at some point probably
call the `SSHExec` built-in middleware.
The `SSHExec` built-in middleware was added. This uses the information
returned by `Machine#ssh_info` and uses the `Vagrant::Util::SSH` helper
to exec into the remote machine. The provider should do any work upfront
in verifying that the machine is ready to be SSHed into.
2012-08-05 13:45:24 -07:00
9db982f7a4
Expose the provider via the machine object.
2012-08-04 11:16:31 -07:00
1e997f87d7
Clean up the actions a bit, move logic into actual middleware.
...
This is a good idea because in the future it will allow plugins to
properly override these behaviors.
2012-07-28 19:58:10 -07:00
31a3a3f2e2
Start moving the halt commands over to the new provider interface
2012-07-28 10:43:16 -07:00
e5f250121a
Call now only yields the environment
2012-07-27 19:34:46 -07:00
118377e6f0
Destroy sequence asks the user for confirmation.
2012-07-27 19:29:40 -07:00
90517a0f9b
The `Call` built-in middleware allows for conditional MW sequences.
...
Read the documentation for more information.
2012-07-26 23:56:47 -07:00
5eed3b8417
Building up the `destroy` action again using new provider API.
...
This shows me moving the built-in middleware sequences to the provider
and how I'm organizing all that.
2012-07-26 22:39:27 -07:00
Emiliano Ticci
Mitchell Hashimoto