Significant portions of the users, who run OVF on some Server without UI (headless mode) will not be able to use OVF because they'll don't know IP address of PMM server based on our current instructions
PMM Server as a Virtual Appliance page contains a script that imports the PMM Server appliance and configures it to bridge the en0 adapter from the host. Then the script routes console output from the appliance to /tmp/pmm-server-console.log. This is done because the script then starts the appliance in headless (without the console) mode.
Steps to reproduce:
- Import image
VBoxManage import pmm-server-2.11.1.ova
- Modify NIC settings if needed
VBoxManage list bridgedifs
VBoxManage modifyvm 'PMM Server 2.11.1' --nic1 bridged --bridgeadapter1 'en0: Wi-Fi (AirPort)'
- Log console output into file
VBoxManage modifyvm 'PMM Server 2.11.1' --uart1 0x3F8 4 --uartmode1 file /tmp/pmm-server-console.log
- Start instance
VBoxManage startvm --type headless 'PMM Server 2.11.1'
- Wait for 1 minute and get IP address from the log
grep cloud-init /tmp/pmm-server-console.log
The 'pmm-server-console.log' doesn't contain IP adress.
The user can get the IP address from the log.
Note: desired state - current instructions work, no actions on the user side. If this is completely not possible or significant impact - let's discuss changes we can do