gistfile1.txt

# HPE VM Essentials
Welcome to HPE VM Essentials. The following document provides only a basic guide to getting started. 
For more installation guidance please refer to the documentation available at https://hpevm-docs.morpheusdata.com.

## Requirements

* HPE VM Essentials currently requires a base installation of Ubuntu 22.04 on all Hypervisor Hosts.
* At this time, all Hosts in the desired Cluster must have the same configuration (network interface names, storage, and CPU)

## Getting Started

HPE VM Essentials is currently delivered as an `.iso` file containing the initial `hpe-vm` console debian package
and the HPE VME Management Virtual Machine (`.QCOW2`). The `hpevm` package contains the appropriate dependencies to 
load the required packages from ubuntu as well as provides a useful ANSI console for performing network configurations
and more in the future. It also provides an automated installer process for installing the HPE VME Management Console.

1. Install the `.deb` package on this ISO with `apt` and not `dpkg` to ensure all dependencies are loaded

```
sudo apt install -f /path/to/hpevm.deb
```

2. Ensure proper network configuration for all hosts
    * A bond/network interface must be configured with a **STATIC** IP Adddress for the management network.
    * For Layer2 Networking create an untagged trunk interface
    * Storage options differ on requirements, please see documentation for details.
3. Prepare for specifying the information needed to deploy the Management VM.
   * IP Address / Netmask / Gateway / DNS
   * Proxy Configuration (if needed)
   * Initial SSH User Credentials
4. Kick off the Morpheus Console Installation with `hpe-vm`
   * Choose "Install Morpheus" and follow the on screen prompts
   * Be sure to specify the full path to the QCOW2 file on the ISO.
     
     (i.e. `/mnt/cd/hpe-vme-8.0.0.qcow2.gz`)
5. Wait for HPE VME Management console to come online and point your browser to the appliance URL to continue first time setup.
6. Once your `LICENSE` is applied, create your first Cloud and HPE VM Cluster. Further setup instructions can be found at https://hpevm-docs.morpheusdata.com

Should we be more explicit to tell them to

• Transfer the ISO on one of the Hypervisor Host.
• Mount the ISO file
  mount -o loop /path/to/isofile

So that later when they specify the QCOW2 file, we can refer to the same path where they have mounted the iso?

Under requirement we should ask for an IP and FQDN for HPE VME Management Console. Make it clear we expect IP --> FQDN and FQDN --> IP to be inplace to ensure successful deployment.

• For Layer2 Networking create an untagged trunk interface

it can be tagged or untagged. If its tag, they must configure the VLAN ID accordingly.

I agree with the FQDN comment. Maybe we should add that as a workaround, if DNS is not available or the FQDN entry can't be added for any reason, they can add the IP as the appliance's URL as (https://).