search

vmware-archive / vagrant-vmware-appcatalyst

Vagrant provider for VMware AppCatalyst®
Apache License 2.0
73 stars 16 forks source link

Provider doesn't handle state of appcatalyst-daemon #11

Closed mootpt closed 8 years ago

mootpt commented 9 years ago

Appcatalyst provider does not work out of the box and requires the appcatalyst-daemon to be started before vagrant will function properly. This behavior is unexpected for most, as the existing VMware providers don't require a separate daemon to be running for vagrant up to function as expected:

vagrant up --provider=vmware_appcatalyst        
Can't connect to AppCatalyst, please verify connectivity.

Ideally, the daemon should be handled by the provider and/or this requirement should be documented.

frapposelli commented 9 years ago

Thanks for reporting this @mootpt

It's something that we're considering adding, both from the AppCatalyst standpoint (starting up the daemon on boot, having a menubar helper to start/stop the daemon) and from the Vagrant provider (adding a do you want to start the daemon? [y/n] prompt).

mootpt commented 9 years ago

Thanks @frapposelli.

Xe commented 8 years ago

It is apparently unvagranty to prompt the user for any input on the provisioning of a machine. If the user is wanting to use the appcatalyst stack it makes sense to do one of two things:

  1. Fix it for the user and tell them that it was fixed.
  2. Explode with a better error message to tell the user how to fix it.
Xe commented 8 years ago

This issue should have been closed by #20, oops.