create_zone_users capability needs to add vagrant public key
create_zone_users needs to use proper sudo interpolation
adding zonegate utilities
minor fixes in zonenat
updating zonegate shell script to ensure the currently running zone will get natted when the script runs
Ensure vagrant RSA key gets written in local zone

zlogin echo > file was executing the > in the gz
gitignore .vagrant
Add vagrantfile for local development
Install zonegate (disabled by default)

zonegate currently seems to break our ability to
talk to the gz or the lz
Zonegate smf start should exit 0
Allow vboxfs in zones
Whoops typo
Create vnic in global zone, on which we will create zones
oh yeah right. routes.
Hard code zone creation to use vnic

This will need to be made dynamic, so that the IP can be chosen
at run time in order to support multiple zones. Multiple zones
are not currently supported, so there you go.

We use this vnic so that when we start zonegate in the global zone
ipnat will forward everything on port 22 to the local zone.

Outstanding issues:
- when zonegate starts, we no longer have any access to the global
  zone
- almost all zones vagrant commands require access to the global zone
WIP smartos communicator
Alphabetize actions
Oh alphabetical order
Set up port forward for global zone

WIP - the GZ does not listen on 2222. We'll need to
ensure that zonegate routes this to 22 in the GZ.

The SmartOS communicator can hopefully grab the gz_ssh
port forward configuration and use that.
Forward 2222 in the GZ to 22 in the GZ

This allows us to access the GZ via a secondary
port forward, even when the rest of the networking
is automatically forwarded by the GZ to the zone.