# Hardware Requirements

- **Operating System:** Ubuntu 22.04
- **CPU:** One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
- **Memory:** 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
- **Disk Space:** For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while HPE Morpheus Enterprise will configure Ceph for multi-node clusters
- **Network Connectivity:** HVM hosts must be assigned static IP addresses. They also need DNS resolution of the HPE Morpheus Enterprise appliance and Internet access in order to download and install system packages for HVM dependencies, such as KVM, Open vSwitch (OVS), and more

NOTE

Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.

NOTE

Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.

Table 1. HVM Network Communication Ports

       | Description | Source | Destination | Port | Protocol |
| --- | --- | --- | --- | --- |
| HPE Morpheus Enterprise Agent communication with the HPE Morpheus Enterprise appliance | HVM Host | HPE Morpheus Enterprise appliance server | 443 | TCP |
| HPE Morpheus Enterprise Agent communication with the HVM Host for hypervisor console | HPE Morpheus Enterprise appliance server | HVM Host | 7443 | TCP |
| HVM host configuration and management | HPE Morpheus Enterprise appliance server | HVM Host | 22 | TCP |
| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
| HPE Morpheus Enterprise server SSH access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 22 | TCP |
| HPE Morpheus Enterprise server WinRM (HTTP) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5985 | TCP |
| HPE Morpheus Enterprise server WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5986 | TCP |
| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
| pcsd | HVM Host | HVM Host | 2224 | TCP |
| dlmd | HVM Host | HVM Host | 21064 | TCP |
|  | HVM Host | HVM Host | 9929 | TCP |
|  | HVM Host | HVM Host | 9929 | UDP |
|  | HVM Host | HVM Host | 3121 | TCP |
