Modifying Skytap VMs and environments created by Vagrant

This article provides instructions for modifying existing Skytap environments and VMs that have been created by Vagrant.

Changing the settings for a VM

To edit the VM CPU and RAM settings

Edit the box.cpu and box.ram settings in the VM definition of the Vagrantfile. For instructions, see Customizing a Vagrantfile.
Use vagrant reload to reload the existing environment.

Adding a VM to an environment

To add a VM

Add the VM definition to the Vagrantfile. For instructions, see Customizing a Vagrantfile.
Use vagrant up to start the new VM and add it to the existing environment.

Removing VMs from an environment

To remove a VM

Use vagrant destroy <vm-name> to delete the VM.
Remove the VM definition from the Vagrantfile.

The Skytap Vagrant provider has basic support for sharing portals. Publishing an environment gives full anonymous access to the Skytap environment to anyone with the URL (and optional password). A sharing portal provides browser-based access to a shared view of all VMs in the environment—including details, thumbnails, and desktop access using the Secure Remote Access (SRA) browser client. For more information about sharing portals, see Sharing VMs and environments with sharing portals.

You can set a password (See Vagrant Commands, Password). You can revoke anonymous access by deleting the sharing portal with vagrant publish-url delete (Skytap users with appropriate permissions can still access the environment through the Skytap UI).

Syncing local folders with VM folders

Skytap supports Vagrant’s NFS synced folders.

To use NFS-synched folders

Add vm.network settings in the VM definition of the Vagrantfile. For instructions, see Enable NFS synced folders.
Use vagrant reload to reload the existing environment.

Adding port forwarding

To add port forwarding to a VM

Add vm.network settings in the VM definition of the Vagrantfile. For instructions, see Enable port forwarding.
Use vagrant reload to reload the existing environment.