Allow for editing network settings on Environment creation

[echristoffersen]

In the getting started with Vagrant tutorial (http://help.skytap.com/vagrant-getting-started.html), the created environment creates a single machine with IP address 10.0.0.1.

I get the following (expected) error on startup:

account@hubert:~/skytap_test$ vagrant up
==> runtime: New Skytap environment created: https://cloud.skytap.com/configurations/12345678
There were no available options for connecting to the VM.
Currently, the provider supports connections over VPN only.

To resolve this issue, I had to navigate to the configuration and change the network subnet and attach/connect VPN. I then rerun vagrant up.

This is a a request to have the ability to modify the network settings of the environment / machines on configuration creation to avoid the necessary manual step described above.

[sumitmehrotra]

@echristoffersen, wanted to provide you with an update on this. We looked at private_network support in Vagrant. However, it does not have all the interfaces required to support the SDN model in Skytap yet. So the assumption, when using a VPN connection, is that either the 'target' template has the right network address space already or has been configured through additional scripting. We explored adding more Skytap specific network settings, but that adds more custom attributes to the VagrantFile.

Meanwhile, the Getting Started has been updated to support a model where the Vagrant host VM is also in Skytap. This was a new feature we added in the provider. In this case, the plugin automatically detects the network address space of the 'provisioned' VM and everything works.

Happy to hear your thoughts on this.