michaelphagen/vm-manage

A collection of scripts for creating and managing GUI-less virtual machines running on VMware Fusion on MacOS.

vm-manage's Issues

Improvement: Replace ssh calls with vm-connect

Goal

Replace all ssh calls such as ssh $uservar@$ip calls with calls to the vm-connect script to simplify code.

Possible Implementations

vm-connect will need to be modified to accept the 3 calls for vm-create/initialize in order to fully replace all ssh calls. #1 must be fixed prior to this

Feature: Add vm-delete/vm-remove

Goal

Create a vm-delete or vm-remove script to delete a particular VM from the command line

Possible Implementations

Simple script that will check the VM directory for all VMs and delete the specified one (after double checking and confirming)

Improvement: Replace hard coded MAC address in vm-create

Goal

Replace hard coded MAC address in vm-create by looking at the .vmx file for the template to find the clone's MAC address.

Possible Implementations

See above. This should be a simple fix, and would improve the flexibility of templates greatly.

Feature: Add vm-list

Goal

Create a vm-list script to list all VMs and whether they are running or not

Possible Implementations

Check the VM directory for all VMs and list them by name. list whether they are running by comparing with vmrun list.

This script should also replace all vmrun list calls.

Feature: Create first release

Goal

Create a release using Packages or JAMF Composer and release it via this repo

Possible Implementations

See Above.

Notes

Issues #1, #2, #3, #4, and #5 should be resolved prior to the release

(vm-create.bash) arp -a does not list new VM

What's wrong

Running arp -a on the local machine does not include the new VM. This prevents the first ssh as root into the new server and thereby prevents the initialization of that server in scripts/vm-create.bash

To fix

• Put Current IP of DHCP Handshake on template into settings file (since currently we are changing the MAC Address to 00:00:00:00:00:00 before cloning. This could be attempted after some number of failures.

• Correctly find IP of new vm using arp. Docs cite pinging the broadcast address, but this hasn't worked in partial testing.

• Add second virtual network address device to allow the ssh into new machine locally.