weekly refresh: 2026-05-22T17:39Z — 1161 content change(s) across 7 bundle(s)
1161 content change(s) across 7 bundle(s)
1161 sidecar metadata update(s)
7 new bundle(s) added
Bundles with content changes:
hvm_deployment_guide (NEW): 32 page(s)
- GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA
- GUID-28F18596-4902-4CD1-83F3-1411430C5534
- GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259
- GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C
- GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB
... and 27 more
hvm_release_notes_8_1_0 (NEW): 1 page(s)
- sd00007497en_us
hvm_release_notes_8_1_1 (NEW): 1 page(s)
- sd00007609en_us
hvm_release_notes_8_1_2 (NEW): 1 page(s)
- sd00007734en_us
hvm_user_manual_8_1_0 (NEW): 374 page(s)
- GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
- GUID-02679208-A796-4A58-80AC-33DCF6A4899F
- GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
- GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
- GUID-0503F050-177F-4360-9B1A-49439AF366B8
... and 369 more
hvm_user_manual_8_1_1 (NEW): 376 page(s)
- GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
- GUID-02679208-A796-4A58-80AC-33DCF6A4899F
- GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
- GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
- GUID-0503F050-177F-4360-9B1A-49439AF366B8
... and 371 more
hvm_user_manual_8_1_2 (NEW): 376 page(s)
- GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
- GUID-02679208-A796-4A58-80AC-33DCF6A4899F
- GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
- GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
- GUID-0503F050-177F-4360-9B1A-49439AF366B8
... and 371 more
This commit is contained in:
hvm-docs-refresh
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA",
|
||||||
|
"title": "VME Manager sizing",
|
||||||
|
"ordinal": 5,
|
||||||
|
"parent_title": "Planning and preparation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,32 @@
|
|||||||
|
# VME Manager sizing
|
||||||
|
|
||||||
|
VM Essentials manager can be deployed via the console as one of three predefined sizes: small, medium, or large. The greater the capacity, the greater amount of resources and cluster sizes the VM Essentials manager can manage. For large production environments, it’s recommended you select a large manager.
|
||||||
|
|
||||||
|
**Manager VM sizing options**
|
||||||
|
|
||||||
|
| | | | |
|
||||||
|
| --- | --- | --- | --- |
|
||||||
|
| Size | vCPUs | Memory | Use Case |
|
||||||
|
| Small | 2 | 12GB | Testing environments, small clusters |
|
||||||
|
| Medium | 4 | 16GB | Standard production, moderate workloads |
|
||||||
|
| Large | 4 | 32GB | Large production, high-performance environments |
|
||||||
|
|
||||||
|
**Performance guidelines**
|
||||||
|
|
||||||
|
**Small configuration:**
|
||||||
|
|
||||||
|
- Maximum clusters: Up to One (1) HVM cluster
|
||||||
|
- Concurrent operations: Limited provisioning
|
||||||
|
- Recommended for: Development, testing, proof-of-concept
|
||||||
|
|
||||||
|
**Medium configuration:**
|
||||||
|
|
||||||
|
- Maximum clusters: Up to Three (3) HVM clusters with moderate VM density
|
||||||
|
- Concurrent operations: Standard provisioning and monitoring
|
||||||
|
- Recommended for: Production environments, typical enterprise use
|
||||||
|
|
||||||
|
**Large configuration:**
|
||||||
|
|
||||||
|
- Maximum clusters: Up to Ten (10) HVM clusters with high VM density
|
||||||
|
- Concurrent operations: High-volume provisioning, extensive monitoring
|
||||||
|
- Recommended for: Large enterprises, service providers, intensive workloads
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-28F18596-4902-4CD1-83F3-1411430C5534",
|
||||||
|
"title": "Installing HVM OS on host servers",
|
||||||
|
"ordinal": 16,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,125 @@
|
|||||||
|
# Installing HVM OS on host servers
|
||||||
|
|
||||||
|
## Prerequisites
|
||||||
|
|
||||||
|
Ensure that before you download the **HVM\_Install\_\*\*\*\*\*\*.iso**, you have the required license.
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
Use the HPE-Provided HVM OS ISO to install your hosts. Download **HVM\_Install\_\*\*\*\*\*\*.iso** from [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/product-details/HPE_VME_EVAL/-/sw360_hpe_internal).
|
||||||
|
|
||||||
|
The following example considers a simple active-backup network bond which does not require any advanced configurations on the network switches. It also assumes that the network ports are trunk ports and require the VLANs to be tagged at the host.
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Mount the HVM OS Install ISO to the DVD drive device on the host machine. You can also mount the ISO using the server's Out of Band Management console.
|
||||||
|
2. Boot the server from the DVD drive.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
To install the HVM OS, you must select the uploaded ISO image to boot the system. This will involve updating the boot order to select the device with the ISO mounted before other devices or manually selecting a boot device during the boot sequence. The exact steps to do this will vary depending on the specific manufacturer and system. Refer your system documentation for specific instructions.
|
||||||
|
3. Select HVM Install 24.04 when the boot menu appears.
|
||||||
|
|
||||||
|
|
||||||
|
4. Proceed through the installer.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Use your keyboard’s **Tab** key to navigate the installer TUI.
|
||||||
|
5. In the Network configuration screen, create your network bond and add a VLAN.
|
||||||
|
1. Select **Create bond**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
For details on Bonds, see [Example Network Configurations](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.html).
|
||||||
|
2. Select the network interfaces to be added to the bond.
|
||||||
|
|
||||||
|
|
||||||
|
3. Under Bond mode, select **active-backup**.
|
||||||
|
|
||||||
|
|
||||||
|
4. Select **[Create]**
|
||||||
|
|
||||||
|
|
||||||
|
5. Your bond will show in the interface selection screen.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
To simplify future configurations, it is highly recommended to create a bond even if only one interface will be used.
|
||||||
|
6. Select your bond to configure it.
|
||||||
|
|
||||||
|
- If your management network needs to be on a tagged VLAN, select **Add a VLAN tag**.
|
||||||
|
|
||||||
|
|
||||||
|
- Add your Management VLAN ID.
|
||||||
|
|
||||||
|
|
||||||
|
- A new interface with your VLAN ID will show, select it and select **Edit IPv4**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
A static IP is required for successful configuration later on.
|
||||||
|
- Select **Manual** for the IPv4 Method.
|
||||||
|
|
||||||
|
|
||||||
|
- Enter your network configuration.
|
||||||
|
|
||||||
|
|
||||||
|
- Select **[Done]** at the bottom.
|
||||||
|
|
||||||
|
|
||||||
|
6. Next configure the Storage.
|
||||||
|
1. Leave the default selection to **Use an entire disk** and **Set up this disk as an LVM group** selected and select **[Done]**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
The installer selects the disk automatically, check it selected the right one and change it if necessary.
|
||||||
|
2. In the **Guided storage configuration** screen, under **Used Devices**, select **ubuntu-lv**, open the **Options** menu, and select **Edit**.
|
||||||
|
|
||||||
|
|
||||||
|
3. Modify the Size to match the maximum disk size, then **Save**.
|
||||||
|
|
||||||
|
|
||||||
|
4. When you are back in the Storage Configuration page, select **Done**.
|
||||||
|
5. On the Confirm Destructive Action prompt, select **Continue**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
This prompt might not appear at this stage.
|
||||||
|
7. In the Proxy Configuration screen, configure proxy settings if your environment requires a proxy. Enter the proxy details when prompted during the installation. If a proxy is not required, leave the Proxy address field blank and continue with the installation.
|
||||||
|
8. Next, in the **Profile configuration** screen, enter the required details and select **Done**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
1. The system proceeds with the installation process.
|
||||||
|
2. When the process finishes, select **[Reboot Now]**.
|
||||||
|
|
||||||
|
|
||||||
|
3. Make sure your ISO is either unmounted or removed from the server.
|
||||||
|
9. After the HVM host reboots, login using the user created during installation either via the server's console or using SSH.
|
||||||
|
10. To make sure you have all the latest system packages, update your system:
|
||||||
|
|
||||||
|
```
|
||||||
|
```
|
||||||
|
sudo apt update && sudo apt upgrade -y
|
||||||
|
```
|
||||||
|
```
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
All packages will be pulled from a repository curated and maintained by HPE.
|
||||||
|
11. Make sure to configure time synchronization (NTP) by following this KB Article: [Configuring NTP for HVM host via /etc/systemd/timesyncd.conf](https://support.hpe.com/hpesc/public/docDisplay?docId=sf000109519en_us&docLocale=en_US).
|
||||||
|
|
||||||
|
NTP configuration is crucial in any system that needs to coordinate tasks between different services.
|
||||||
|
12. Configure locale settings and make further networking configurations using the hpe-vm console. See [Configuring the HVM host using the hpe-vm console](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html).
|
||||||
|
13. Repeat this process for all your host servers.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259",
|
||||||
|
"title": "Scenario 1: Recommended Converged Networking Setup",
|
||||||
|
"ordinal": 8,
|
||||||
|
"parent_title": "Example Network Configurations",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,41 @@
|
|||||||
|
# Scenario 1: Recommended Converged Networking Setup
|
||||||
|
|
||||||
|
This is where management and VM traffic is converged over the same bonded interface and storage traffic is independent. This is where management and VM traffic is converged over the same bonded interface and storage traffic is independent, for use cases where management and traffic separation is needed, review Scenario 2.
|
||||||
|
|
||||||
|
In an ideal scenario, you would have at least four network interfaces spread across at least two network cards on the host (shown in green on the diagram below). Ideally you would also have two separate network switches to help ensure resiliency and redundancy. As mentioned in the prior section, these networking examples are all created with resiliency and redundancy in mind. One storage lane is connected to each switch and likewise one management/VM lane is connected to each switch, which are bonded in and active/backup configuration. Consult the bonding table in the prior section for more details on the benefits and drawbacks to different types of network bonds.
|
||||||
|
|
||||||
|
**Example 1**
|
||||||
|
|
||||||
|
In this scenario, the bond handles management/VM traffic failover while multipathing handles storage failover. A diagram of such a network setup is shown below:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Example 2**
|
||||||
|
|
||||||
|
In the example below, we have native VLAN on the trunk ports and on the storage ports. This means the network switch is tagging all the traffic for you and you don't have to tag it yourself. This allows you to put your IP addresses directly on the interfaces and bonds. Here, the storage VLANS get their own IP address directly on the interface while the management IP address goes directly on the bond as shown in the diagram below. With this configuration, all can be done in the installation wizard as long as the VLANs are piped to the interfaces as expected from the network switches. More specific guidance on using the installation wizard is included in later sections covering the software installation.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Your environment an configurations will vary. You may or may not have a native VLAN set up for storage traffic as it is best practice to isolate storage traffic when possible. The need for VLAN tagging on specific interfaces is dependent on whether there is a native VLAN on that interface.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Below is a chart showing the connection from the bonded network interfaces created in the example network configuration above to OVS bridges (a virtual switch that connects VMs to the physical network), Virtual Networks (logical virtual networks managed by Libvirt), Libvirt Portgroups (subgroups within Libvirt Networks that can expose configurations, such as VLAN tagging), and tap interfaces (the virtual connection that connects the VM to the OVS bridge).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Example 3**
|
||||||
|
|
||||||
|
The prior example included native VLANs on the trunk ports and storage ports so we'll now take a look at an example configuration without native VLANs. You need to create VLAN tags on the interfaces because the switch is no longer handling the tagging for you. Your IP addresses then go on those VLAN tags. In this example bond0 becomes the compute interface and bond0.x becomes the management interface when configuring the cluster in a later step (see [Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)). When not using a native VLAN, the storage VLANs still get their own IP address and interface but a VLAN interface gets created on the bond and the management IP address goes on the VLAN interface.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Just as in the similar chart above, the chart below shows the connection from the bonded network interfaces created in the example network configuration above to OVS bridges (a virtual switch that connects VMs to the physical network), Virtual Networks (logical virtual networks managed by Libvirt), Libvirt Portgroups (subgroups within Libvirt Networks that can expose configurations, such as VLAN tagging), and tap interfaces (the virtual connection that connects the VM to the OVS bridge).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Example 4**
|
||||||
|
|
||||||
|
The same networking setup can be used with an LACP bond, however this does require extra configuration on the network switch side. The exact setup steps would depend on the specific hardware in your environment. The network setup would look something like the example below:
|
||||||
|
|
||||||
|
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C",
|
||||||
|
"title": "Setup from the HVM host",
|
||||||
|
"ordinal": 25,
|
||||||
|
"parent_title": "Upgrading the manager",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,3 @@
|
|||||||
|
# Setup from the HVM host
|
||||||
|
|
||||||
|
Confirm the manager VM name (`virsh list`) and connect with `virsh console <vm name>`. This starts a local VNC serial connection. This method only works if the host has GUI capabilities installed.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB",
|
||||||
|
"title": "Planning and preparation",
|
||||||
|
"ordinal": 3,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
# Planning and preparation
|
||||||
|
|
||||||
|
Describes sizing, networking and storage requirements, and VM Essentials host and virtual machine features requirements.
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Host Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.html)**
|
||||||
|
- **[VME Manager sizing](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.html)**
|
||||||
|
- **[Example Network Configurations](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.html)**
|
||||||
|
- **[Required ports](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.html)**
|
||||||
|
- **[Supported storage protocols](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.html)**
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-456E190C-E912-4079-A691-8D2368D63748",
|
||||||
|
"title": "Configuring the VM Essentials manager for initial setup",
|
||||||
|
"ordinal": 20,
|
||||||
|
"parent_title": "VM Essentials manager installation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-456E190C-E912-4079-A691-8D2368D63748.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,60 @@
|
|||||||
|
# Configuring the VM Essentials manager for initial setup
|
||||||
|
|
||||||
|
## Prerequisites
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
With VM Essentials manager up and running, you can now access the UI front end by pointing your web browser to the appliance URL that you set in a previous step. You’ll be presented with a workflow for the initial VM Essentials manager configuration where you’ll have to fill in the requested information.
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Fill in the Account Name for the Master Tenant.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This is just your organization’s name to set it up in the manager.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
HPE Morpheus VM Essentials does not support multi-tenancy, this is just an identifier for the manager to use. (Upgrade or refer to HPE Morpheus Enterprise to enable multi-tenancy capabilities.)
|
||||||
|
2. Enter the first user’s information.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This user will become the first System Administrator and will have all the permissions.
|
||||||
|
3. Enter a name for the VM Essentials manager appliance.
|
||||||
|
|
||||||
|
|
||||||
|
4. Toggle the **Enable Backups** toggle if you want automated manager database backups to be taken and if you want to enable the native virtual machine backup feature.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Integrated backups will reside on the manager’s local storage by default, you should enable an external repository later.
|
||||||
|
5. Enter your license and select **Complete Setup**. If you don’t have a valid license or are just evaluating the solution, a 30 day evaluation period is activated by default.
|
||||||
|
|
||||||
|
- The main Appliance Setting screen opens with several configuration options. The next steps focus on the main items you’ll need to configure to create your first cluster.
|
||||||
|
- You need a pre-existing Group and Cloud to add your first HVM cluster. Groups define logical groupings of resources and users access those resources based on the Groups associated with their Roles. A Cloud can represent a grouping of HVM clusters or a connection into a VMware vCenter environment. You can read more on [Groups](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007230en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html) and [Clouds](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007230en_us&docLocale=en_US&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html) in the HPE Morpheus VM Essentials Software Documentation. This guide will go through the process of adding Private Cloud-type Clouds which house HVM clusters. For VMware-type Clouds, see the associated [integration guide](https://hpevm-docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware.html).
|
||||||
|
6. Create the first group.
|
||||||
|
1. Go to Infrastructure > Groups on the top menu.
|
||||||
|
|
||||||
|
|
||||||
|
2. Click Create.
|
||||||
|
|
||||||
|
|
||||||
|
3. Give the group a name and click Save Changes.
|
||||||
|
|
||||||
|
|
||||||
|
7. Create the first Cloud.
|
||||||
|
1. Go to Infrastructure > Clouds and click Add.
|
||||||
|
2. Select PRIVATE CLOUD.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
To add additional CLOUDs other than HVM or VMware, upgrade to HPE Morpheus Enterprise.
|
||||||
|
|
||||||
|
|
||||||
|
3. Assign a name and then click Next at the bottom.
|
||||||
|
4. Select your existing Group.
|
||||||
|
|
||||||
|
|
||||||
|
5. Review and complete the wizard.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7",
|
||||||
|
"title": "Deployment",
|
||||||
|
"ordinal": 14,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,15 @@
|
|||||||
|
# Deployment
|
||||||
|
|
||||||
|
Provides essential information about how to deploy HPE Morpheus VM Essentials including HVM host and VM Essentials manager installation.
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Solution overview](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099_2.html)**
|
||||||
|
Provides an overview of the components included in HPE Morpheus VM Essentials including HVM, and VM Essentials manager.
|
||||||
|
- **[Installation overview](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.html)**
|
||||||
|
- **[Installing HVM OS on host servers](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html)**
|
||||||
|
- **[Configuring the HVM host using the hpe-vm console](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html)**
|
||||||
|
- **[VM Essentials manager installation](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.html)**
|
||||||
|
- **[Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)**
|
||||||
|
- **[Configuring Linux images for use with HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.html)**
|
||||||
|
- **[Configuring Windows Images for Use with HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.html)**
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA",
|
||||||
|
"title": "Upgrading the manager",
|
||||||
|
"ordinal": 24,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,27 @@
|
|||||||
|
# Upgrading the manager
|
||||||
|
|
||||||
|
Explains how to upgrade the VM Essentials manager, the Morpheus Agent, and how to update HVM hosts.
|
||||||
|
|
||||||
|
To upgrade the VM Essentials manager, you’ll need to obtain the `.deb` upgrade package(s) from the VM Essentials page on the HPE Software Center. Reach out to your account manager if you’re unable to access the downloads as described in the next paragraphs. For an upgrade, you’ll need the debian package (not the ISO, which is for first-time installation). If you are performing an offline upgrade, you will also need the “supplemental” debian package.
|
||||||
|
|
||||||
|
Once logged into [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/dashboard/entitlement), click on the “Software” section from the side navigation.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Within the “Software” section, search for HPE Morpheus VM Essentials Software amongst your other software entitlements. A “Product Info” type search for the term “HPE Morpheus VM Essentials Software” may work but depending on the entitlements present in the account and future changes to search functionality, a slightly different search might be required. Once VM Essentials is successfully returned, click on the dropdown menu under “Action” and click on “Get License.”
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
From the download page, you’ll see software packages, signature files and license files. Mark the checkbox next to any that you need and download them to your computer.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
For an upgrade, we only need the `.deb` file available in the software center (and potentially the “supplemental” debian package as well if this will be an offline upgrade). To continue, copy the `.deb` file(s) over to the VM Essentials manager VM. On Linux, this could be done with `scp` (`scp /path/to/file.deb username@<VM IP address>:/path/to/destination`). You’ll need the VM user’s password unless you’re using SSH keys. Alternatively, you may also click the "curl Copy" button to download a .txt file containing a curl command which you can paste into a terminal session connected to the HPE Morpheus VM Essentials Manager VM.
|
||||||
|
|
||||||
|
With the `.deb` file in place, we need to open a console connection to the VM Essentials manager VM to perform the actual upgrade. There are a number of methods to accomplish this but below are two examples from either an HVM host or from your own computer.
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Setup from the HVM host](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.html)**
|
||||||
|
- **[Setup from another computer](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-54192A74-516A-4605-9623-49538D67D590.html)**
|
||||||
|
- **[Upgrade process](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.html)**
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-54192A74-516A-4605-9623-49538D67D590",
|
||||||
|
"title": "Setup from another computer",
|
||||||
|
"ordinal": 26,
|
||||||
|
"parent_title": "Upgrading the manager",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-54192A74-516A-4605-9623-49538D67D590.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,7 @@
|
|||||||
|
# Setup from another computer
|
||||||
|
|
||||||
|
- Confirm the manager VM name (run `virsh list` on the HVM host).
|
||||||
|
- Next, make note of the VNC port and password for the VM Essentials manager VM. This is done by running `virsh edit <vm name>` on the HVM host and finding it within the block beginning `<graphics`. This block is typically near the bottom of the XML.
|
||||||
|
- Having obtained this information, move back over to your own computer (must be a computer with a desktop terminal, access to the VME host, and GUI capabilities).
|
||||||
|
- Connect to the SSH tunnel: `ssh -L <VNC PORT>:127.0.0.1:<VNC PORT> <VME Host User>@<Host IP/hostname>`.
|
||||||
|
- Then, using a VNC viewer (for example, VNCViewer64), connect to `localhost:<VNCPort>`. Use the password obtained from the VM XML viewed earlier.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98",
|
||||||
|
"title": "Updating HVM OS",
|
||||||
|
"ordinal": 28,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,100 @@
|
|||||||
|
# Updating HVM OS
|
||||||
|
|
||||||
|
Explains how to update HVM OS, the base operating system for HVM Hosts
|
||||||
|
|
||||||
|
HVM OS is preconfigured with trusted `apt` update repositories, which are hosted by HPE. These repositories enabled customers to apply updates to HVM OS during scheduled maintenance or downtime windows. This ensures systems remain secure and up to date.
|
||||||
|
|
||||||
|
The following repositories are configured by default:
|
||||||
|
|
||||||
|
HPE Zion Private Repository
|
||||||
|
|
||||||
|
- Types: deb
|
||||||
|
- URIs: <https://update1.linux.hpe.com/repo/hpevme/zion-private-ubuntu/>
|
||||||
|
- Suites: pulp
|
||||||
|
- Components: upload
|
||||||
|
- Check-Valid-Until: False
|
||||||
|
- Trusted: True
|
||||||
|
- Signed-By: /etc/apt/keyrings/zion\_repo\_public.key
|
||||||
|
|
||||||
|
This repository is used for HPE-provided, platform-specific packages required for the HVM OS environment. It may include custom components, integrations, or fixes validated by HPE.
|
||||||
|
|
||||||
|
HPE Zion OS Updates Repository (Ubuntu 24.04 - Noble)
|
||||||
|
|
||||||
|
- Types: deb
|
||||||
|
- URIs: : <https://update1.linux.hpe.com/repo/hpevme/zion-os-updates-prod/ubuntu2404-os-updates/>
|
||||||
|
- Suites: noble-updates
|
||||||
|
- Components: main
|
||||||
|
- Check-Valid-Until: False
|
||||||
|
- Trusted: True
|
||||||
|
- Signed-By: /etc/apt/keyrings/zion\_repo\_public.key
|
||||||
|
|
||||||
|
This repository provides curated Ubuntu 24.04 (Noble) OS updates aligned with HPE validation and support requirements for HVM OS deployments.
|
||||||
|
|
||||||
|
Update Process and Customer Responsibility
|
||||||
|
|
||||||
|
Customers can use standard `apt` tooling to apply updates when newer OS packages are available (`apt update` and `apt upgrade`). Updates should be performed only during approved maintenance windows to minimize operational impact.
|
||||||
|
|
||||||
|
Complete the update process on one host at a time. Hosts are placed into maintenance mode and the update is run only after confirming the host has successfully entered maintenance. Hosts are placed into maintenance by:
|
||||||
|
|
||||||
|
1. Navigating to the cluster detail page
|
||||||
|
2. Selecting the Hosts tab
|
||||||
|
3. Selecting an individual host
|
||||||
|
4. Selecting the ACTIONS menu
|
||||||
|
5. selecting "Enter Maintenance"
|
||||||
|
|
||||||
|
Once the host has entered maintenance mode, run `sudo apt update` and `sudo apt upgrade`. After completing the update, bring the host back out of maintenance mode and continue to the next host only after confirming the prior host has successfully left maintenance.
|
||||||
|
|
||||||
|
All repositories are:
|
||||||
|
|
||||||
|
- Explicitly marked as trusted
|
||||||
|
- Signed using the HPE Zion public repository key
|
||||||
|
- Configured with "Check-Valid-Until: False" to avoid update interruptions caused by metadata expiration
|
||||||
|
|
||||||
|
IMPORTANT
|
||||||
|
|
||||||
|
Only packages obtained from the preconfigured HPE repositories are supported. Adding external or upstream Ubuntu repositories may lead to unsupported configurations.
|
||||||
|
|
||||||
|
Offline HVM OS Updates
|
||||||
|
|
||||||
|
For air-gapped environments where cluster hosts don't have access to the public Internet, use the following process to update the underlying base OS (HVM OS). This process should be completed on one host at a time to avoid any cluster downtime.
|
||||||
|
|
||||||
|
1. Download the offline upgrade bundle to your workstation from My HPE Software Center
|
||||||
|
2. Copy the offline upgrade bundle to the HVM Host. This can be done using `scp` or a similar tool like `WinSC` (ex. `scp hvm-upgrade-bundle.zip user@x.x.x.x:/home/user`)
|
||||||
|
3. Remotely access the HVM Host (ex. `ssh user@x.x.x.x`)
|
||||||
|
4. From the directory where you copied the offline upgrade bundle, unzip the bundle into its own new directory (ex. `unzip hvm-upgrade-bundle.zip -d hvm-upgrade-bundle/`)
|
||||||
|
5. Navigate into the new directory (ex. `cd hvm-upgrade-bundle/`)
|
||||||
|
6. The directory contains a tar bundle and a repository key. First, copy the repository key to `/etc/apt/keyrings/` (ex. `sudo cp zion_repo_public.key /etc/apt/keyrings/`)
|
||||||
|
7. Convert the key using `sudo gpg --dearmor -o /etc/apt/keyrings/zion_repo_public.gpg zion_repo_public.key`
|
||||||
|
8. Set permissions on the converted key using `sudo chmod 644 /etc/apt/keyrings/zion_repo_public.gpg`
|
||||||
|
9. The `.key` file can now be deleted using `sudo rm /etc/apt/keyrings/zion_repo_public.key`
|
||||||
|
10. Untar the bundle (ex. `tar xvzf hvm_upgrade_bundle_xxx.tar.gz`)
|
||||||
|
11. Move up one directory level (`cd ../`)
|
||||||
|
12. Move the extracted bundle to `/var/local` (ex. `sudo cp -a hvm-upgrade-bundle /var/local`)
|
||||||
|
13. Change the directory owner (ex. `sudo chown -R root:root /var/local/hvm-upgrade-bundle`)
|
||||||
|
14. Create a new file for a new addition to the local `apt` repository (ex. `sudo vi /etc/apt/sources.list.d/hpe-local-repo.sources`)
|
||||||
|
15. Within the text editor, add the following content to the new file. Then, save the file:
|
||||||
|
|
||||||
|
```
|
||||||
|
```
|
||||||
|
Types: deb
|
||||||
|
URIs: file:/var/local/hvm-upgrade-bundle/ubuntu2404-os-updates
|
||||||
|
Suites: noble-updates
|
||||||
|
Components: main
|
||||||
|
Check-Valid-Until: False
|
||||||
|
Signed-By: /etc/apt/keyrings/zion_repo_public.gpg
|
||||||
|
```
|
||||||
|
```
|
||||||
|
16. Within the HPE Morpheus Software UI, put the HVM Host we just worked with into Maintenance Mode. To do this, navigate to **Infrastructure > Clusters > Selected HVM Cluster > Hosts tab > Selected Host**. Once on the HVM Host detail page, click ACTIONS and then click "Enter Maintenance Mode."
|
||||||
|
17. Back on the HVM Host, validate that all VMs have stopped with `sudo virsh list --all`. This should show that there are no running VMs
|
||||||
|
18. Validate that Pacemaker has entered standby mode with `sudo pcs status`. Status should show standby
|
||||||
|
19. Stop Pacemaker with `sudo systemctl stop pacemaker`
|
||||||
|
20. Stop Corosync with `sudo systemctl stop corosync`
|
||||||
|
21. Update `apt` package data with `sudo apt update`. You will very likely see errors and should confirm these are for online repositories which cannot be reached in an offline environment. Once you've confirmed this is the source of the error, you may ignore the errors and proceed
|
||||||
|
22. Upgrade HVM OS with `sudo apt upgrade`
|
||||||
|
23. Reboot the system with `sudo reboot -f now`
|
||||||
|
24. Validate Pacemaker came back up as expected with `sudo systemctl status pacemaker`
|
||||||
|
25. Validate Corosync came back up as expected with `sudo systemctl status corosync`
|
||||||
|
26. Bring Corosync back from standby with `sudo pcs node unstandby`
|
||||||
|
27. Confirm the HVM Host came out of standby with `sudo pcs status`
|
||||||
|
28. Back in HPE Morpheus Software UI once again, take the HVM Host out of Maintenance Mode by navigating to the Host detail page as described previously. Click on the ACTIONS menu and select "Exit Maintenance Mode."
|
||||||
|
29. Once the HVM Host is confirmed back from Maintenance Mode, complete this process on all other HVM Hosts which make up the cluster
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB",
|
||||||
|
"title": "User manual",
|
||||||
|
"ordinal": 29,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# User manual
|
||||||
|
|
||||||
|
Provides further information on configuration and workflows.
|
||||||
|
|
||||||
|
For further information about HPE Morpheus VM Essentials configurations and management, see [HPE Morpheus VM Essentials Software Documentation](https://www.hpe.com/support/morpheus-vm-essentials-documentation-latest)
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A",
|
||||||
|
"title": "VM Essentials manager installation",
|
||||||
|
"ordinal": 18,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
# VM Essentials manager installation
|
||||||
|
|
||||||
|
The Morpheus VM Essentials manager is delivered as a virtual appliance that runs on top of any of the HVM hosts in the cluster. Getting it up and running is a simple, two-step process that involves deploying the appliance virtual machine and initializing the actual VME manager application with some initial settings. The following sections outline both steps:
|
||||||
|
|
||||||
|
- [Installing the VM Essentials manager](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html)
|
||||||
|
- [Configuring the VM Essentials manager for initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-456E190C-E912-4079-A691-8D2368D63748.html)
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Installing the VM Essentials manager](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html)**
|
||||||
|
- **[Configuring the VM Essentials manager for initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-456E190C-E912-4079-A691-8D2368D63748.html)**
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8",
|
||||||
|
"title": "Supported storage protocols",
|
||||||
|
"ordinal": 11,
|
||||||
|
"parent_title": "Planning and preparation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
# Supported storage protocols
|
||||||
|
|
||||||
|
HPE Morpheus VM Essentials supports different types of storage for storing virtual machines.
|
||||||
|
|
||||||
|
Local server storage
|
||||||
|
: While local disks in the HVM hosts can be used to store virtual machines, using local storage doesn’t allow the virtual machines to be migrated live to other hosts and the virtual machines won’t be able to be recovered should the host fail.
|
||||||
|
|
||||||
|
External block storage
|
||||||
|
: VM Essentials supports connecting to external storage arrays using either iSCSI or Fiber Channel, in both cases datastores using GFS2 (Global Filesystem 2) can be created on volumes exported to the hosts. With this type of storage, the minimum number of supported HVM hosts in a cluster is three (3).
|
||||||
|
|
||||||
|
NFS
|
||||||
|
: VM Essentials can use NFS shares as external shared data stores, in this case the minimum number of HVM hosts in a cluster is two (2) if virtual machine availability is desired.
|
||||||
|
|
||||||
|
HPE Alletra MP B10000 Plugin
|
||||||
|
: VM Essentials also includes an integration plugin that allows it to create storage volumes that are directly mapped to each virtual machine’s disk without needing an intermediary clustered filesystem thus simplifying management tasks and improving performance.
|
||||||
|
|
||||||
|
HPE SimpliVity
|
||||||
|
: HPE also offers an HCI solution through HPE SimpliVity that allows the creation of high availability clusters using the hosts' local disk while enabling advanced data services like data reduction, backup and replication.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290",
|
||||||
|
"title": "Network Bonding",
|
||||||
|
"ordinal": 7,
|
||||||
|
"parent_title": "Example Network Configurations",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,9 @@
|
|||||||
|
# Network Bonding
|
||||||
|
|
||||||
|
Network bonding is the combining of multiple network adapters into a single logical interface. This is done to build in redundancy and to increase throughput. Network bonds are configured at the operating system level and there are multiple types of network bonds depending on hardware support and other factors.
|
||||||
|
|
||||||
|
In the scenarios described in the following sections, we will call out two types of network bonds that are effective for virtualization (active-backup and LACP) and show them in example configurations. VMware LBT bonds are also shown in the table below for the sake of comparison, though only the other two have been utilized in verified scenarios.
|
||||||
|
|
||||||
|
Once established, we can later offer up these bonded interfaces as a compute network (for virtual machine traffic) or storage network (for interacting with external storage) when creating our cluster within the VM Essentials manager.
|
||||||
|
|
||||||
|
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-88494051-74D1-4BD9-BAFF-134A573FF77B",
|
||||||
|
"title": "API reference",
|
||||||
|
"ordinal": 30,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# API reference
|
||||||
|
|
||||||
|
Contains the full API reference for interacting programmatically with HPE Morpheus VM Essentials.
|
||||||
|
|
||||||
|
See the HPE Morpheus VM Essentials [API reference](https://apidocs.morpheusdata.com/docs/getting_started) for a complete endpoint list and example call formation.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-8D494112-C361-4300-B7BF-B4DFE06E871C",
|
||||||
|
"title": "Configuring Linux images for use with HVM Clusters",
|
||||||
|
"ordinal": 22,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,59 @@
|
|||||||
|
# Configuring Linux images for use with HVM Clusters
|
||||||
|
|
||||||
|
**Prerequisites**: Read: [System requirements](https://ubuntu.com/server/docs/reference/installation/system-requirements/).
|
||||||
|
|
||||||
|
This is an example image prep process for creating a deployable Ubuntu 24.04 image for HVM Clusters.
|
||||||
|
|
||||||
|
1. Download the latest Ubuntu 24.04 Server ISO from Canonical.
|
||||||
|
2. Upload the downloaded Ubuntu ISO as a Virtual Image in the HPE Morpheus VM Essentials Software Manager:
|
||||||
|
|
||||||
|
1. Navigate to Library > Virtual Images
|
||||||
|
2. Click Add
|
||||||
|
3. Select the downloaded ISO
|
||||||
|
4. Configure the "Operating System" (Ubuntu 24.04 64-bit) and leave all other configurations on the default selections. Drag and drop the ISO on the Drop Files Here dropzone near the bottom of the modal.
|
||||||
|
5. Wait until the ISO has completely uploaded. There is a progress bar to provide information on the upload process.
|
||||||
|
6. Once the ISO has fully uploaded, click Save changes.
|
||||||
|
3. Provision a new HVM workload to your HVM Cluster:
|
||||||
|
|
||||||
|
1. Navigate to Provisioning > Instances.
|
||||||
|
2. Click + ADD.
|
||||||
|
3. From the Type tab of the provisioning wizard, select HVM and click Next.
|
||||||
|
4. From the Group tab, select the correct Group and Cloud for your HVM Cluster, provide a name for this Instance, and click Next.
|
||||||
|
5. On the Configure tab, the exact configurations for the following fields will depend on the environment and available resources. Use the guidelines below to make appropriate selections. At this point, we simply need an accessible VM so we can successfully install the OS, make a few additional configurations (such as installing cloud-init), and save it as a deployable image.
|
||||||
|
|
||||||
|
Plan
|
||||||
|
: A number of default plans ship with Morpheus, using a smaller default plan is fine for this purpose.
|
||||||
|
|
||||||
|
Resource Pool
|
||||||
|
: Select a cluster this VM can run on, when getting started there may only be one.
|
||||||
|
|
||||||
|
Root volume
|
||||||
|
: Smaller size is fine for this purpose and a specific datastore could be manually selected if desired.
|
||||||
|
|
||||||
|
Network
|
||||||
|
: Select the network configured for the instance.
|
||||||
|
|
||||||
|
IMAGE
|
||||||
|
: Select the ISO that was just uploaded.
|
||||||
|
6. Click Next and Complete through the next two tabs to stand up the Instance.
|
||||||
|
4. Install and configure your new VM for image creation:
|
||||||
|
|
||||||
|
1. Click into the newly created Instance to view the Instance detail. Launch the console view so installation and configurations can be completed (ACTIONS > Open Console)
|
||||||
|
2. Complete the Ubuntu installation process. In most environments, the default installation configurations will work fine for our purposes here, just ensure the VM will be able to get out to the Internet. During installation, a user profile will be created which will be used to perform additional configurations in the steps ahead.
|
||||||
|
3. When installation is complete, reboot the VM. You will be warned that the ISO is still mounted to the virtual machine. Eject the ISO using the UI tools in the Manager (ACTIONS > Eject Disks). Once ejected, continue with the reboot.
|
||||||
|
4. Following reboot, log in as the user configured during installation and complete these prep steps:
|
||||||
|
|
||||||
|
1. Run updates: `sudo apt update && sudo apt upgrade -y`
|
||||||
|
2. Install cloud-init: `sudo apt install -y cloud-init`
|
||||||
|
3. Verify cloud-init is installed: `cloud-init --version`
|
||||||
|
4. Enable cloud-init services: `sudo systemctl enable cloud-init cloud-init-local cloud-config cloud-final`
|
||||||
|
5. Check status of the service: `sudo systemctl status cloud-init`
|
||||||
|
6. Configure cloud-init data sources by editing the following config file: `sudo vi /etc/cloud/cloud.cfg.d/90_dpkg.cfg` with the following configuration: `datasource_list: [ NoCloud, None ]`. Then, save and close the config file
|
||||||
|
7. Disable things that break templating: `sudo truncate -s 0 /etc/machine-id` and `sudo rm -f /var/lib/dbus/machine-id`
|
||||||
|
8. Clear SSH keys: `sudo rm -f /etc/ssh/ssh_host_*`
|
||||||
|
9. Remove persistent network config: `sudo rm -f /etc/netplan/*.yaml`
|
||||||
|
10. Clean cloud-init state: `sudo cloud-init clean --logs`
|
||||||
|
5. Close the console window and shut down the VM using the Manager UI tools from the Instance detail page (ACTIONS > Stop Server.)
|
||||||
|
6. Still on the Instance detail page, create an image from your stopped Instance (ACTIONS > Import as Image.)
|
||||||
|
7. Back on the Virtual Images list page, you should see a new Virtual Image object being created
|
||||||
|
8. Once the image is completely created (status shows as Active), you are ready to provision. Repeat the steps above to add a new Instance but substitute the new deployable image rather than the ISO that was used originally. Now, the disk, network, and default user configurations made during Instance provisioning will apply successfully to new Instances. You can continue to build on this by installing specific software stacks and saving new images for specific service types. Additionally, setup scripts can be written and applied at provision time to add additional orchestration at deployment time.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-94742592-9C85-4F2E-83F2-E68404A73F3B",
|
||||||
|
"title": "Upgrade process",
|
||||||
|
"ordinal": 27,
|
||||||
|
"parent_title": "Upgrading the manager",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,54 @@
|
|||||||
|
# Upgrade process
|
||||||
|
|
||||||
|
Having copied over the needed files and connected to the VM Essentials manager VM, the upgrade is completed in just a few commands. These commands will stop the current services, install the package, and then reconfigure the Manager. Replace the placeholder `.deb` file in the commands below with the correct path and file name of the package you’ve copied over.
|
||||||
|
|
||||||
|
IMPORTANT
|
||||||
|
|
||||||
|
Upgrading VM Essentials manager will result in downtime of 10-15 minutes. Ensure users are not doing critical work during the upgrade window. This downtime applies only to the Manager itself and has no effect on the hypervisor host(s) or any provisioned VMs currently running.
|
||||||
|
|
||||||
|
```
|
||||||
|
```
|
||||||
|
sudo morpheus-ctl stop morpheus-ui
|
||||||
|
sudo dpkg -i xxxx.deb
|
||||||
|
sudo dpkg -i xxxx.supplemental.deb # Optional -- Only for offline upgrades
|
||||||
|
sudo morpheus-ctl reconfigure
|
||||||
|
```
|
||||||
|
```
|
||||||
|
|
||||||
|
All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once the UI service is up and running, the upgrade process is complete. Attempt to reach your appliance normally through a web browser to confirm success.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
- Services will be stopped during package installation and started during the reconfigure process, including the `morpheus-ui` service.
|
||||||
|
- If the reconfigure process is interrupted or fails, the `morpheus-ui` service may need to be manually started or restarted.
|
||||||
|
- In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
|
||||||
|
|
||||||
|
Following upgrade, it's advisable to check for any available HVM Host Agent upgrades. To upgrade the HVM Host Agent, navigate to an HVM Host detail page, expand the ACTIONS menu, and click "Upgrade Agent." This process must be repeated for each HVM Host that makes up the HVM Cluster.
|
||||||
|
|
||||||
|
Alternatively, you could also select "Download Agent Script" to download an Agent upgrade script which can be run when connected to the host through a terminal session. The Agent upgrade scripts are Host-specific so an individual script would need to be downloaded for each HVM Host.
|
||||||
|
|
||||||
|
## Upgrade sequence procedure
|
||||||
|
|
||||||
|
This section contains a table of compatible upgrade paths. The far left column contains the HPE Morpheus VM Essentials Manager version you're starting from. The columns to the right indicate versions compatible for upgrade from your starting version. If the version number is listed, it is a compatible upgrade path. If an "**X**" is listed instead, the upgrade path is unsupported.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
It is possible to span multiple versions in a single upgrade. For example, you can upgrade directly from HPE Morpheus VM Essentials version 8.0.3 to version 8.0.6, or from version 8.0.7 to version 8.0.11, and so on. Consult the table below for compatible or incompatible version upgrade hops.
|
||||||
|
|
||||||
|
| From Version | To Version | | | | | | | | | | | | | | |
|
||||||
|
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|
||||||
|
| 8.0.1 → | 8.0.2 | 8.0.3 | 8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.2 → | | 8.0.3 | 8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.3 → | | | 8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.4 → | | | | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.5 → | | | | | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.6 → | | | | | | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.7 → | | | | | | | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.8 → | | | | | | | | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.9 → | | | | | | | | | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.10 → | | | | | | | | | | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.11 → | | | | | | | | | | | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.12 → | | | | | | | | | | | | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.0.13 → | | | | | | | | | | | | | 8.1.0 | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.1.0 → | | | | | | | | | | | | | | 8.1.1 | 8.1.2 |
|
||||||
|
| 8.1.1 → | | | | | | | | | | | | | | | 8.1.2 |
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB",
|
||||||
|
"title": "Required ports",
|
||||||
|
"ordinal": 10,
|
||||||
|
"parent_title": "Planning and preparation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,22 @@
|
|||||||
|
# Required ports
|
||||||
|
|
||||||
|
Table 1. HVM Network Communication Ports
|
||||||
|
|
||||||
|
| Description | Source | Destination | Port | Protocol |
|
||||||
|
| --- | --- | --- | --- | --- |
|
||||||
|
| HPE Morpheus VM Essentials Agent communication with the HPE Morpheus VM Essentials manager | HVM Host | HPE Morpheus VM Essentials manager | 443 | TCP |
|
||||||
|
| HPE Morpheus VM Essentials Agent communication with the HVM Host for hypervisor console | HPE Morpheus VM Essentials manager | HVM Host | 7443 | TCP |
|
||||||
|
| HVM host configuration and management | HPE Morpheus VM Essentials manager | HVM Host | 22 | TCP |
|
||||||
|
| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
|
||||||
|
| HPE Morpheus VM Essentials manager SSH access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 22 | TCP |
|
||||||
|
| HPE Morpheus VM Essentials manager WinRM (HTTP) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5985 | TCP |
|
||||||
|
| HPE Morpheus VM Essentials manager WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus VM Essentials manager | 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 |
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-99397996-8315-49C1-9E2F-2EED51CE03F3",
|
||||||
|
"title": "Creating an HVM cluster",
|
||||||
|
"ordinal": 21,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,59 @@
|
|||||||
|
# Creating an HVM cluster
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
An HVM cluster is the basic unit of management in VM Essentials, you need to create a cluster even if you are only using one HVM host for testing or for edge data centers. A cluster is a construct that allows you to access the advanced functionality of the solution.
|
||||||
|
|
||||||
|
Once the VM Essentials manager is configured, you are ready to create your HVM cluster.
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Go to Infrastructure > Clusters and click + Add Cluster.
|
||||||
|
|
||||||
|
|
||||||
|
2. Select HVM as the cluster type and click Next.
|
||||||
|
3. Select the Group the cluster will belong to.
|
||||||
|
|
||||||
|
|
||||||
|
4. Give your cluster a name and, optionally, enter a description and any label to identify it.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Only fields with a green mark on the left are mandatory.
|
||||||
|
|
||||||
|
|
||||||
|
5. Fill in the required fields.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Leave the layout at the default HVM 1.2 Cluster on HVM/Ubuntu 24.04.
|
||||||
|
- For SSH Hosts, click the + sign on the right to add as many hosts as you need. Enter a name for each host and its management IP address. The exact name entered here is not vital as it's simply an identifier for that specific host within the user interface. It could be the hostname or some other identifier specific to that host.
|
||||||
|
- Enter an SSH Username and SSH Password. This is a set of credentials for an admin user account configured on each host.
|
||||||
|
6. Enter the network interfaces in the designated fields.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Management net interface: Enter the tagged bond you created for host management.
|
||||||
|
- Compute net interface: To route virtual machine traffic using different VLANs through the same ports your management network uses, enter the untagged bond you created.
|
||||||
|
- Compute VLANs: Enter any VLANs you need, the respective Portgroups will be created.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
- You can obtain the interface names from the host's CLI using the command: `ip address show`.
|
||||||
|
- Selecting the bond with NO TAGGING is crucial for the virtual switch to allow VLANs to flow through.
|
||||||
|
7. You can safely leave all the remaining settings by default. Here is a short description.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- CPU Type: Only x86\_64 is supported.
|
||||||
|
- CPU Model: This setting will define the CPU used for virtual machines, you should leave it as “host-passthrough” unless your cluster nodes have different CPU families each.
|
||||||
|
- Dynamic placement: If enabled, the cluster will balance the load automatically by live migrating virtual machines between nodes.
|
||||||
|
- Power policy: Defines if the hosts will optimize for performance or for power consumption.
|
||||||
|
8. Click Next and then Complete.
|
||||||
|
|
||||||
|
You are taken back to the cluster screen where you’ll see your cluster name and an icon showing the cluster is being created.
|
||||||
|
|
||||||
|
|
||||||
|
9. To follow up on the creation process, click on the cluster name and then go to the History tab. When the Provision and the Post-Provision activities finish with a green check mark, your cluster is ready to run virtual machines.
|
||||||
|
|
||||||
|
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC",
|
||||||
|
"title": "Websites",
|
||||||
|
"ordinal": 32,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
# Websites
|
||||||
|
|
||||||
|
## General websites
|
||||||
|
|
||||||
|
Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
|
||||||
|
: <https://www.hpe.com/storage/spock>
|
||||||
|
|
||||||
|
Technical papers and analyst reports
|
||||||
|
: <https://www.hpe.com/us/en/resource-library>
|
||||||
|
|
||||||
|
For additional websites, see [Support and other resources](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=Standard-Support_and_other_resources.html).
|
||||||
@@ -0,0 +1,31 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
|
||||||
|
"title": "Host Features",
|
||||||
|
"ordinal": 12,
|
||||||
|
"parent_title": "VM Essentials features",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Host Features",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
|
||||||
|
"clustering_title": "Host Features"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
|
||||||
|
"clustering_title": "Host Features"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
|
||||||
|
"clustering_title": "Host Features"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
# Host Features
|
||||||
|
|
||||||
|
- Automated HVM cluster provisioning
|
||||||
|
- CEPH storage configuration for multi-node clusters
|
||||||
|
- CEPH summary, a high-level dashboard of CEPH components and status
|
||||||
|
- DRS, automatic rebalancing of clusters based on resource consumption
|
||||||
|
- Compatibility validation of network and storage devices at time of cluster provisioning
|
||||||
|
- Hypervisor console
|
||||||
|
- Configuration and deployment of OVS networks (VLANs)
|
||||||
|
- Cluster and individual host monitoring
|
||||||
|
- Add hosts to existing clusters
|
||||||
|
- Console support for cluster hosts
|
||||||
|
- Add, edit and remove networks and datastores from clusters
|
||||||
|
- Gracefully take hosts out of service with maintenance mode
|
||||||
|
- Migration of workloads across hosts
|
||||||
|
- Configurable automatic failover of running workloads when a host is lost
|
||||||
|
- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
|
||||||
|
- Governance through VM Essentials RBAC
|
||||||
|
- Pass host-attached NVME, USB, and GPU hardware through to VMs running on the host
|
||||||
@@ -0,0 +1,31 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
|
||||||
|
"title": "VM Features",
|
||||||
|
"ordinal": 13,
|
||||||
|
"parent_title": "VM Essentials features",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "VM Features",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
|
||||||
|
"clustering_title": "VM Features"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
|
||||||
|
"clustering_title": "VM Features"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
|
||||||
|
"clustering_title": "VM Features"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
# VM Features
|
||||||
|
|
||||||
|
- Workload provisioning and monitoring (Linux or Windows workloads)
|
||||||
|
- Console support for running workloads
|
||||||
|
- Affinity placement, pin VMs to hosts
|
||||||
|
- Brownfield discovery of existing VMs
|
||||||
|
- Reconfigure VM sizing
|
||||||
|
- Disk migration across datastores
|
||||||
|
- UEFI support
|
||||||
|
- Migration of VMs across hosts
|
||||||
|
- Configure automatic failover for individual VMs in the event a host is lost
|
||||||
|
- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
|
||||||
|
- Backup and restore VM workloads, with optional synthetic full backups
|
||||||
|
- Clone VMs
|
||||||
|
- Take snapshots and revert to snapshots
|
||||||
|
- VM Essentials library and automation support
|
||||||
|
- Claim and consume host-attached NVME, USB, and GPU hardware to run hardware-accelerated workloads on VMs
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-ADC37453-056E-43C8-8177-8211A44790FD",
|
||||||
|
"title": "Configuring the HVM host using the hpe-vm console",
|
||||||
|
"ordinal": 17,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,83 @@
|
|||||||
|
# Configuring the HVM host using the hpe-vm console
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
The hpe-vm console is an utility built by HPE to simplify host management tasks like setting up the timezone, configure the networks and bootstrapping the VM Essentials manager. Use it to configure important settings in the network bond and to configure the iSCSI storage networks, if iSCSI storage is applicable.
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Open the hpe-vm console utility by running: `sudo hpe-vm`.
|
||||||
|
|
||||||
|
|
||||||
|
2. Select **Configure Network**. You are presented with a menu where you can make all the needed network configuration changes without any manual editing using the host's CLI.
|
||||||
|
|
||||||
|
|
||||||
|
3. Adjust bond configuration.
|
||||||
|
|
||||||
|
For the active-backup bond to perform interface failover, the mii-monitor-interval needs to be configured as described in this KB article [Setting active/backup bond type parameters with the hpe-vm cli tool](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000109520en_us). You can do this from the hpe-vm console.
|
||||||
|
|
||||||
|
1. Navigate to **Device Type** and select **bond**.
|
||||||
|
|
||||||
|
|
||||||
|
2. Select your bond.
|
||||||
|
|
||||||
|
|
||||||
|
3. Navigate to the Bond section and select **<edit>** in the parameters option.
|
||||||
|
|
||||||
|
|
||||||
|
4. Enter the following values and then select **<Done>**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Mii-monitor-interval: 100
|
||||||
|
- up delay: 200
|
||||||
|
- down delay: 200
|
||||||
|
5. Select **<Done>** to navigate away from the bond menu
|
||||||
|
|
||||||
|
|
||||||
|
6. Select **<Save>**.
|
||||||
|
|
||||||
|
|
||||||
|
7. Select **Confirm** in the pop-up notification.
|
||||||
|
4. Next, configure the iSCSI interfaces, if applicable.
|
||||||
|
|
||||||
|
iSCSI interfaces are just ethernet adapters so you can configure them from the same hpe-vm console.
|
||||||
|
|
||||||
|
1. Make sure **ethernet** is selected under **Device type**.
|
||||||
|
2. Select **Add**.
|
||||||
|
|
||||||
|
|
||||||
|
3. Under **Device ID**, enter the interface name and select **<Continue>**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
The interface name can be obtained by running `ip a` at the host’s CLI.
|
||||||
|
4. Select **<edit>** on the addresses row to configure the IP Address.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
iSCSI traffic is not usually routed, you won’t need to configure other network parameters unless your specific network requires it.
|
||||||
|
|
||||||
|
Switch ports for iSCSI traffic are usually untagged access ports.
|
||||||
|
5. Set the MTU to `9000`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Most iSCSI storage networks use Jumbo Frames for performance, this configuration needs to be consistent across the network.
|
||||||
|
6. Select <Done> and then <Save> from the main network configuration menu.
|
||||||
|
7. Repeat this process for the second interface.
|
||||||
|
|
||||||
|
TIP
|
||||||
|
|
||||||
|
It is not advised to bond storage interfaces as the storage layer at the host handles multipathing to the storage array.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
- Do not use the same subnet for both storage interfaces, this might cause storage access problems.
|
||||||
|
- iSCSI networks should not be routable and do not need a gateway.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170",
|
||||||
|
"title": "Example Network Configurations",
|
||||||
|
"ordinal": 6,
|
||||||
|
"parent_title": "Planning and preparation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,9 @@
|
|||||||
|
# Example Network Configurations
|
||||||
|
|
||||||
|
If you have the capability to do so, it’s recommended you set up networking with full redundancy. Such a setup could include two network switches and hosts with at least four network interfaces spread across two network cards. This would allow for failover in the event of the loss of a switch and/or one of the host network cards in addition to separating management and compute network traffic to their own interfaces. Hosts with only four NICs each can still be configured for full redundancy but would have to converge management and compute traffic across the same interfaces. Keep in mind also that these examples use MPIO (multi-path input/output) for storage. It would also be possible to use bonding for storage depending on capabilities of the environment. MPIO is recommended whenever fibre channel or iSCSI LUNs are being used for GFS2 datastores.
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Network Bonding](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.html)**
|
||||||
|
- **[Scenario 1: Recommended Converged Networking Setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.html)**
|
||||||
|
- **[Scenario 2: Recommended Decoupled Networking Setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.html)**
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2",
|
||||||
|
"title": "Host Requirements",
|
||||||
|
"ordinal": 4,
|
||||||
|
"parent_title": "Planning and preparation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,13 @@
|
|||||||
|
# Host Requirements
|
||||||
|
|
||||||
|
- **Operating System:** HVM OS provided by Hewlett Packard Enterprise.
|
||||||
|
- **Hardware:** HPE Proliant server hardware or another compatible server type is recommended (see the [compatibility matrix](https://www.hpe.com/support/vme-compatibility-matrix) for a list of recommended compute server choices). This list is continually expanded as additional hardware SKUs are tested and verified.
|
||||||
|
- **CPU:** One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
|
||||||
|
- **Memory:** Minimum of 8GB for the HVM runtime OS
|
||||||
|
- **Storage:** Minimum of 100GB for operating system storage
|
||||||
|
- **Network:** 10 Gbps recommended for production environments
|
||||||
|
- **IP Addressing:** One static IP address for management network
|
||||||
|
- **Internet Connectivity:** Internet access is required to download and install the required packages and dependencies
|
||||||
|
- **Network services:**
|
||||||
|
- Hostnames should be resolvable by the network's DNS servers.
|
||||||
|
- NTP is also crucial in distributed systems.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099",
|
||||||
|
"title": "Solution overview",
|
||||||
|
"ordinal": 1,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
# Solution overview
|
||||||
|
|
||||||
|
Provides an overview of the components included in HPE Morpheus VM Essentials including HVM, and VM Essentials manager.
|
||||||
|
|
||||||
|
HPE Morpheus VM Essentials is a simplified virtualization solution designed for organizations seeking efficient virtual machine (VM) management. It provides core capabilities for provisioning, monitoring, and managing VMs across hybrid environments powered by HPE HVM and VMware by Broadcom environments, enabling enterprises and cloud providers to optimize resources and reduce operational overhead.
|
||||||
|
|
||||||
|
Its main components are a virtualization runtime called HVM which is installed on the hosts to run the virtual workloads and a centralized management interface called VME Manager that streamlines VM lifecycle operations—such as provisioning, configuration, and monitoring—while enforcing governance policies and enabling automation for routine tasks. Together, these components deliver a cost-effective, user-friendly platform that enhances agility while leveraging compliance and control in virtualized environments.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**What is HVM?**
|
||||||
|
|
||||||
|
HVM is the HPE‑powered virtualization runtime OS that gets installed on the servers that will support running virtual machines. This runtime is installed using an HPE‑provided ISO, which installs the required runtime libraries and components to create an HVM Cluster to create, run, and manage virtual machines. HVM provides a console that runs on top of the HVM Cluster to simplify configuration tasks like keyboard mapping, time synchronization and even the complete networking configuration.
|
||||||
|
|
||||||
|
**What is the HPE VM Essentials manager?**
|
||||||
|
|
||||||
|
The HPE VM Essentials manager is a centralized management interface that offers a unified control plane for administrators to manage the lifecycle of the HVM hosts, HVM Clusters and virtual machines. It streamlines VM lifecycle operations—such as provisioning, configuration, and monitoring—while enforcing governance policies and enabling automation for routine tasks.
|
||||||
|
|
||||||
|
Once deployed, HPE VM Essentials Manager takes advantage of powerful features including live migration of VMs across the HVM Cluster hosts with zero downtime, dynamically distribute workloads based on load, automatic failover of workloads following the loss of a host, and similar HVM capabilities at operational level. Provisioning new workloads is also made easy with the VM Essentials image library, automation tools, and powerful provisioning wizard. In addition to HVM clusters, VM Essentials also includes a deep integration into VMware vCenter, which also takes advantage of the same powerful provisioning wizard, automation engine, and monitoring capabilities.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B",
|
||||||
|
"title": "CLI reference",
|
||||||
|
"ordinal": 31,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# CLI reference
|
||||||
|
|
||||||
|
Provides the information needed to install the Morpheus CLI to manage the solution.
|
||||||
|
|
||||||
|
See the HPE Morpheus VM Essentials [CLI reference](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006978en_us&docLocale=en_US) for a complete list of commands and options, as well as a guide to installing the tool.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289",
|
||||||
|
"title": "Installing the VM Essentials manager",
|
||||||
|
"ordinal": 19,
|
||||||
|
"parent_title": "VM Essentials manager installation",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,52 @@
|
|||||||
|
# Installing the VM Essentials manager
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
Deploy the VM Essentials manager virtual appliance in one of your HVM hosts. The VM Essentials virtual appliance is delivered inside an ISO (**HPE\_VM\_Essentials\_SW\_image\_´\*\*\*\*\*.iso**) containing the needed .qcow2 file; you can either upload the qcow2 file to your HVM host or upload the complete iso and mount it. This example will run you through the ISO method.
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Upload the **HPE\_VM\_Essentials\_SW\_image\_´\*\*\*\*\*.iso** downloaded from [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/product-details/HPE_VME_EVAL/-/sw360_hpe_internal) using your preferred SCP client.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
There are multiple SCP client options available for Windows client machines.
|
||||||
|
2. Mount the ISO to a path in your HVM host system:
|
||||||
|
|
||||||
|
```
|
||||||
|
```
|
||||||
|
sudo mount -o loop HPE_VM_Essentials_SW_image_v8.0.12_S5Q83-11039.iso /media
|
||||||
|
```
|
||||||
|
```
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
- The indicated filename might be different, this is dictated by your download.
|
||||||
|
- The mount point can be any one you choose, /media is used as an example.
|
||||||
|
3. Enter `sudo hpe-vm` to open the hpe-vm console, and select **<Install VME Manager>**.
|
||||||
|
4. Fill in the required information.
|
||||||
|
|
||||||
|
|
||||||
|
5. When filling the information, consider the following guidelines:
|
||||||
|
|
||||||
|
- Use the IP address that will be configured for the VM Essentials manager
|
||||||
|
- For DNS Server, if multiple entries are needed, a comma-delimited list may be added. Bear in mind, the installer does not currently validate for the proper delimiter. This will be fixed in a future release but for now the user must validate the delimiter for themselves.
|
||||||
|
- The appliance URL should be resolvable via DNS (including related PTR record) from the hosts to enable communications between them and the VM Essentials manager.
|
||||||
|
- The username is the user with admin privilege that will be used to login to the manager’s CLI.
|
||||||
|
- For the Image URI, you can select and browse to the qcow2 file in the ISO you mounted previously
|
||||||
|
|
||||||
|
|
||||||
|
- If your VM Essentials manager will use the same network for management access as the host’s management network, select the same vlan tagged network interface you configured for the HVM host.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Leave the **Use Compute VLAN** box unchecked unless you want your VM Essentials manager to use a different network than the management one.
|
||||||
|
6. Wait for the installation to finish.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
At a certain phase in the install process, you’ll see a message in the progress bar modal stating “Starting Morpheus Services…”. At this point, you can direct a web browser to the appliance URL and see if you can access the appliance. If you get a response returned, even if it is just telling you the appliance is still loading, that is a good sign the web server is installed and things are working even if your progress bar seems to get stuck at a high percentage.
|
||||||
|
|
||||||
|
The exact time for this installation to complete is highly dependent on the amount of compute available, the size of the network pipe, and the level of network congestion. It is common for this process to take long enough for the "Morpheus is Loading" graphic to change to a timeout graphic. This is not an indicator that the process has failed. If there are no other failure indicators, allow at least an hour before considering the installation to be irrecoverably stuck (though it would be very rare for the process to take anywhere near that length of time). To view the setup logs, run the `sudo morpheus-ctl tail morpheus-ui` command from the manager VM through SSH.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849",
|
||||||
|
"title": "Qualification Matrix",
|
||||||
|
"ordinal": 2,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# Qualification Matrix
|
||||||
|
|
||||||
|
Contains the list of hardware and software that has been tested for compatibility with HPE Morpheus VM Essentials Software.
|
||||||
|
|
||||||
|
Hardware and software is continually being tested and certified for compatibility with HPE Morpheus VM Essentials Software. For full details, see [The Qualification Matrix for HPE Morpheus VM Essentials Software](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006551en_us&page=GUID-EA7C0803-E66B-4B17-B994-30D4025A258F.html). Items not listed in that document may be compatible but are untested.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2",
|
||||||
|
"title": "Scenario 2: Recommended Decoupled Networking Setup",
|
||||||
|
"ordinal": 9,
|
||||||
|
"parent_title": "Example Network Configurations",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# Scenario 2: Recommended Decoupled Networking Setup
|
||||||
|
|
||||||
|
When hosts have six or more network interfaces spread across at least two cards, management and VM traffic can be separated for even greater network throughput. The overall configuration is very similar. The storage lanes are still separated as they were previously. In this case, create an additional bond across two of the interfaces for VM traffic. As previously, a bond is also created for management traffic. In this example, these bonds are created in an active/passive configuration. 
|
||||||
|
|
||||||
|
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C",
|
||||||
|
"title": "Configuring Windows Images for Use with HVM Clusters ",
|
||||||
|
"ordinal": 23,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,52 @@
|
|||||||
|
# Configuring Windows Images for Use with HVM Clusters
|
||||||
|
|
||||||
|
This section will go through the steps to prepare a Windows image for deployment on HVM clusters. This image can serve as a template from which additional images and VM Essentials Library items can be built. This section only discusses the Virtual Image configuration fields needed to be successful with this example Windows deployment. For more generalized information on Virtual Images, including configurations needed for successful Linux deployment, see the **Library** **>** **Virtual Images** of the product user manual.
|
||||||
|
|
||||||
|
1. In this example case, we’ll start from downloading a Windows Server ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
|
||||||
|
2. With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
|
||||||
|
- **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2025 ISO”
|
||||||
|
- **OPERATING SYSTEM:** “Windows Server 2025”
|
||||||
|
- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
|
||||||
|
3. In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
|
||||||
|
4. With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space in your VME Manager appliance to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large drop zone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled **Add File** and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal.
|
||||||
|
|
||||||
|
|
||||||
|
5. After the file has completely uploaded, click SAVE CHANGES. Rather than dropping and uploading the file through this modal, users may also select the URL/PATH radio button. This results in a URL field replacing the file drop zone where a URL to external storage containing the image may be entered.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Alternatively, you can source the file from an integrated bucket (if any currently exist) by selecting the bucket in the BUCKET field and entering a path to the image in the URL field. When uploading the image via URL or path, the Virtual Image can be saved and closed as soon as all configurations are finished. Image upload will continue in the background. When uploading via file drop, the modal must remain open until the upload process is completed.
|
||||||
|
6. Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
|
||||||
|
7. On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
|
||||||
|
8. On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration).
|
||||||
|
9. Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
|
||||||
|
10. As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
|
||||||
|
|
||||||
|
|
||||||
|
11. The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
|
||||||
|
12. Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
|
||||||
|
13. Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then **Open Console**. This will open a new window with a console session into the VM.
|
||||||
|
|
||||||
|
|
||||||
|
14. After selecting the language, click **Next**. On the following screen, click **Install Now**. This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click **Next**.
|
||||||
|
|
||||||
|
|
||||||
|
15. Accept the licensing terms and click **Next**.
|
||||||
|
|
||||||
|
|
||||||
|
16. On the next screen, choose a custom install.
|
||||||
|
|
||||||
|
|
||||||
|
17. The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
|
||||||
|
|
||||||
|
|
||||||
|
18. After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
|
||||||
|
|
||||||
|
|
||||||
|
19. Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
|
||||||
|
|
||||||
|
|
||||||
|
20. Step through the installer. Simply click **Next** or **Install** through each step, there are no configuration changes needed. Once the installer has completed, click **Finish**. You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
|
||||||
|
|
||||||
|
|
||||||
|
21. We can now eject the two virtual disks, drives D: and E: in my case.
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_deployment_guide",
|
||||||
|
"page_id": "GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932",
|
||||||
|
"title": "Installation overview",
|
||||||
|
"ordinal": 15,
|
||||||
|
"parent_title": "Deployment",
|
||||||
|
"doc_id": "sd00007332en_us",
|
||||||
|
"version": null,
|
||||||
|
"product": "Deployment Guide",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.html"
|
||||||
|
}
|
||||||
@@ -0,0 +1,27 @@
|
|||||||
|
# Installation overview
|
||||||
|
|
||||||
|
To install HPE Morpheus VM Essentials, you must install the HVM OS on all hosts and deploy the VM Essentials manager as a virtual appliance on one of them. The overview of the installation process is outlined below.
|
||||||
|
|
||||||
|
- Install the HVM OS Install ISO provided by HPE.
|
||||||
|
|
||||||
|
- Go to [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/product-details/HPE_VME_EVAL/-/sw360_hpe_internal).
|
||||||
|
- Click **Go to Download Page**.
|
||||||
|
- Download the ISO: **HVM\_Install\_\*\*\*\*\*\*.iso**
|
||||||
|
|
||||||
|
This ISO will get the base system up and running including all the required packages to create and run virtual machines.
|
||||||
|
|
||||||
|
See [Installing HVM OS on host servers](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html).
|
||||||
|
- Patch the HVM host to make sure it’s running the latest package versions
|
||||||
|
|
||||||
|
See Step 8 in [Installing HVM OS on host servers](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html).
|
||||||
|
- Configure the HVM hosts’ networks
|
||||||
|
|
||||||
|
See [Configuring the HVM host using the hpe-vm console](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html).
|
||||||
|
- Deploy the VM Essentials manager using the VM Essentials Console on one of the hosts
|
||||||
|
|
||||||
|
See [Installing the VM Essentials manager](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html).
|
||||||
|
- Launch the VM Essentials manager UI, apply the license and configure go through the initial configuration process. Note that a short-term evaluation license will automatically be applied for testing purposes if a permanent license is not immediately available
|
||||||
|
|
||||||
|
See [Configuring the VM Essentials manager for initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-456E190C-E912-4079-A691-8D2368D63748.html).
|
||||||
|
|
||||||
|
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_0",
|
||||||
|
"page_id": "sd00007497en_us",
|
||||||
|
"title": "v8.1.0 Release Notes",
|
||||||
|
"ordinal": 1,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007497en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "Release Notes",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007497en_us",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "v8.1.0 Release Notes",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_1",
|
||||||
|
"page_id": "sd00007609en_us",
|
||||||
|
"clustering_title": "v8.1.1 Release Notes"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_2",
|
||||||
|
"page_id": "sd00007734en_us",
|
||||||
|
"clustering_title": "v8.1.2 Release Notes"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,54 @@
|
|||||||
|
# v8.1.0 Release Notes
|
||||||
|
|
||||||
|
# v8.1.0 LTS Release Notes
|
||||||
|
|
||||||
|
- Compatible Plugin API version: 1.3.0
|
||||||
|
- Compatible HPE Morpheus VM Essentials Worker version: 5.4.8+
|
||||||
|
|
||||||
|
Release Dates
|
||||||
|
|
||||||
|
- v8.1.0 February 2026
|
||||||
|
|
||||||
|
IMPORTANT
|
||||||
|
|
||||||
|
After upgrading to v8.1.0, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
|
||||||
|
|
||||||
|
# New Features
|
||||||
|
|
||||||
|
Alletra MP Plugin
|
||||||
|
: - For complete update details, see the [Alletra MP plugin release notes](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007519en_us)
|
||||||
|
|
||||||
|
Appliance
|
||||||
|
: - There is now a single binary installer for both HPE Morpheus Enterprise Software and HPE Morpheus VM Essentials Software. Feature access is controlled solely by licensing. Previously, HPE Morpheus Enterprise and HPE Morpheus VM Essentials had separate binary packages
|
||||||
|
- For newly-installed environments without a paid license configured, the evaluation period has been extended from 30 to 60 days
|
||||||
|
|
||||||
|
Aruba CX Plugin
|
||||||
|
: - Version 1.9.0 of the plugin has been released
|
||||||
|
- The serial numbers and health status for each switch are now shown within the network tab of the integration detail
|
||||||
|
- Other internal improvements
|
||||||
|
|
||||||
|
Aruba CX DSS Plugin
|
||||||
|
: - Version 1.5.0 of the plugin has been released
|
||||||
|
- Users may now specify a Policy Distribution Target (PDT) when creating a DSS port group
|
||||||
|
|
||||||
|
HVM
|
||||||
|
: - Added vCPU placement (NUMA and L3 boundaries) control for HVM clusters
|
||||||
|
|
||||||
|
Library
|
||||||
|
: - HPE Morpheus VM Essentials now includes a default library of example images that can be provisioned to HVM Clusters or integrated VMware Clouds right out of the box
|
||||||
|
|
||||||
|
Security
|
||||||
|
: - Updates to internal dependency libraries to close potential security vulnerabilities
|
||||||
|
|
||||||
|
Tenants
|
||||||
|
: - Storage volume detail pages now show the volume UUID
|
||||||
|
|
||||||
|
# Fixes
|
||||||
|
|
||||||
|
API & CLI
|
||||||
|
: - Improved the efficiency of making calls to list instances (/api/instances) which, in some environments, could be slow to respond
|
||||||
|
|
||||||
|
HVM
|
||||||
|
: - Fixed an issue that caused GFS2 to change to a read-only state when rebooting the HVM Host
|
||||||
|
|
||||||
|
Published: February 2026
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_1",
|
||||||
|
"page_id": "sd00007609en_us",
|
||||||
|
"title": "v8.1.1 Release Notes",
|
||||||
|
"ordinal": 1,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007609en_us",
|
||||||
|
"version": "8.1.1",
|
||||||
|
"product": "Release Notes",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007609en_us",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "v8.1.1 Release Notes",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_0",
|
||||||
|
"page_id": "sd00007497en_us",
|
||||||
|
"clustering_title": "v8.1.0 Release Notes"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_2",
|
||||||
|
"page_id": "sd00007734en_us",
|
||||||
|
"clustering_title": "v8.1.2 Release Notes"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,40 @@
|
|||||||
|
# v8.1.1 Release Notes
|
||||||
|
|
||||||
|
# v8.1.1 LTS Release Notes
|
||||||
|
|
||||||
|
- Compatible Plugin API version: 1.3.3
|
||||||
|
- Compatible HPE Morpheus VM Essentials Worker version: 5.4.8+
|
||||||
|
|
||||||
|
Release Dates
|
||||||
|
|
||||||
|
- v8.1.1 March 2026
|
||||||
|
|
||||||
|
IMPORTANT
|
||||||
|
|
||||||
|
After upgrading to v8.1.1, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
|
||||||
|
|
||||||
|
# New Features
|
||||||
|
|
||||||
|
Aruba CX DSS Plugin
|
||||||
|
: - Updated the add/edit DSS port group modal to allow users to select one or more security groups
|
||||||
|
- Renamed "Default Firewall Policy" field to "Firewall"
|
||||||
|
- Users may now (optionally) make a Security Group selection for DSS Port Groups
|
||||||
|
|
||||||
|
Catalog
|
||||||
|
: - Added CentOS 10 Stream image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||||
|
- Added Debian 13 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||||
|
- Added Alma Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||||
|
- Added Rocky Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
|
||||||
|
|
||||||
|
HVM
|
||||||
|
: - HVM Host hardware sensor data can now be surfaced into the UI. See HVM cluster documentation for details on configuring hosts to gather and surface this data
|
||||||
|
|
||||||
|
# Fixes
|
||||||
|
|
||||||
|
Instances
|
||||||
|
: - Fixed manually added VMs, converted to managed, still appearing as discovered
|
||||||
|
|
||||||
|
Migrations
|
||||||
|
: - Fixed OVA export timeouts in vCenter which were left even after successful migrations
|
||||||
|
|
||||||
|
Published: March 2026
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_2",
|
||||||
|
"page_id": "sd00007734en_us",
|
||||||
|
"title": "v8.1.2 Release Notes",
|
||||||
|
"ordinal": 1,
|
||||||
|
"parent_title": null,
|
||||||
|
"doc_id": "sd00007734en_us",
|
||||||
|
"version": "8.1.2",
|
||||||
|
"product": "Release Notes",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007734en_us",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "v8.1.2 Release Notes",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_0",
|
||||||
|
"page_id": "sd00007497en_us",
|
||||||
|
"clustering_title": "v8.1.0 Release Notes"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_release_notes_8_1_1",
|
||||||
|
"page_id": "sd00007609en_us",
|
||||||
|
"clustering_title": "v8.1.1 Release Notes"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,52 @@
|
|||||||
|
# v8.1.2 Release Notes
|
||||||
|
|
||||||
|
# v8.1.2 LTS Release Notes
|
||||||
|
|
||||||
|
- Compatible Plugin API version: 1.3.4
|
||||||
|
- Compatible HPE Morpheus VM Essentials Worker version: 5.4.8+
|
||||||
|
|
||||||
|
Release Dates
|
||||||
|
|
||||||
|
- v8.1.2 April 2026
|
||||||
|
|
||||||
|
IMPORTANT
|
||||||
|
|
||||||
|
After upgrading to v8.1.2, it is recommended to check for HVM Host agent upgrades as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host. Though many do, it is possible that some version upgrade hops will not contain an HVM Host agent upgrade.
|
||||||
|
|
||||||
|
# New Features
|
||||||
|
|
||||||
|
Localization
|
||||||
|
: - Added support for the Japanese keyboard layout (101/102 hardware) on hypervisor console sessions using the HPE Morpheus key extension (VMware, vCD, and HVM/KVM). It also includes a new keyboard tips pop-over in the console UI ("?" button). Japanese keyboard layout on 106/109 hardware is a planned future enhancement
|
||||||
|
|
||||||
|
# Fixes
|
||||||
|
|
||||||
|
API & CLI
|
||||||
|
: - Errors are no longer returned when sending valid DELETE calls to `/api/clusters/{cluster_id}/servers/{server_id}`
|
||||||
|
- Instance resizes to add or remove network interfaces (`PUT /api/instances/{id}/resize`) on HVM or VMware Instances no longer return success messages without actually changing the network interface(s)
|
||||||
|
|
||||||
|
HVM
|
||||||
|
: - Fixed VM clones failing when the storage datastore type was changed (ex. local storage to Alletra plugin storage) from the original VM to the clone VM
|
||||||
|
- After restoring a VM from SimpliVity backup and successfully reconfiguring the restored VM, it can now be powered on successfully
|
||||||
|
- HVM Hosts will no longer fail to enter maintenance mode when a VM being live migrated to another Host transitions to a shut off state during migration
|
||||||
|
- Fixed an issue where certain maintenance mode sequences could cause HVM hosts to go offline or become fenced
|
||||||
|
- Disabling networks (unmarking the Active checkbox and saving) will no longer cause spontaneous changes to the "Enable IPV4" and/or the "DHCP Server" checkboxes on the next edit
|
||||||
|
- Volume attach/detach operations on VirtIO controllers no longer fail when attempted while snapshots are in progress
|
||||||
|
- Fixed intermittent provisioning failures when multiple VMs are simultaneously provisioned using the copy operation
|
||||||
|
- Fixed AltGR key input for HVM console sessions
|
||||||
|
|
||||||
|
Kubernetes
|
||||||
|
: - Updating worker node counts for Azure AKS clusters now works properly
|
||||||
|
|
||||||
|
Labels
|
||||||
|
: - Fixed Cloud filtering by Label for Clouds shared down to child Tenants from a parent Tenant
|
||||||
|
|
||||||
|
NSX
|
||||||
|
: - When NSX segments are shared across multiple clusters in a VDC, Morpheus can now associate the NSX segment with multiple vCenter segments
|
||||||
|
|
||||||
|
Security
|
||||||
|
: - Added security enhancements
|
||||||
|
|
||||||
|
Virtual Images
|
||||||
|
: - Creating Windows VMs with static IP addresses when cloudinit (Cloudbase-init) is set on the Virtual Image now works
|
||||||
|
|
||||||
|
Published: April 2026
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
|
||||||
|
"title": "Global Backups Settings",
|
||||||
|
"ordinal": 205,
|
||||||
|
"parent_title": "Initial Backups Setup",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Global Backups Settings",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
|
||||||
|
"clustering_title": "Global Backups Settings"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
|
||||||
|
"clustering_title": "Global Backups Settings"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,27 @@
|
|||||||
|
# Global Backups Settings
|
||||||
|
|
||||||
|
VM Essentials Backups can be enabled under Administration > Settings > Backups.
|
||||||
|
|
||||||
|
Scheduled Backups
|
||||||
|
: When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
|
||||||
|
|
||||||
|
Create Backups
|
||||||
|
: When enabled, VM Essentials will automatically configure backup jobs for Instances at provision time.
|
||||||
|
|
||||||
|
Backup Appliance
|
||||||
|
: When enabled, a Backup will be created to backup the VM Essentials appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
|
||||||
|
|
||||||
|
Default Backup Bucket
|
||||||
|
: From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
|
||||||
|
|
||||||
|
Default Backup Schedule
|
||||||
|
: From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
|
||||||
|
|
||||||
|
Backup Retention Count
|
||||||
|
: The default maximum number of successful backups to retain.
|
||||||
|
|
||||||
|
Default Synthetic Full Backup Enabled
|
||||||
|
: When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
|
||||||
|
|
||||||
|
Default Synthetic Full Backups Schedule
|
||||||
|
: From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
|
||||||
|
"title": "Scoping Services",
|
||||||
|
"ordinal": 172,
|
||||||
|
"parent_title": "Integrations",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Scoping Services",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
|
||||||
|
"clustering_title": "Scoping Services"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
|
||||||
|
"clustering_title": "Scoping Services"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,20 @@
|
|||||||
|
# Scoping Services
|
||||||
|
|
||||||
|
NETWORKING
|
||||||
|
: Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
|
||||||
|
|
||||||
|
IPAM
|
||||||
|
: IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
|
||||||
|
|
||||||
|
SECURITY
|
||||||
|
: Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
|
||||||
|
|
||||||
|
DNS
|
||||||
|
: DNS integrations will populate domains in the Infrastructure > Network > Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
|
||||||
|
|
||||||
|
Service Registry
|
||||||
|
: Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
|
||||||
|
"title": "Group and Tenant Access",
|
||||||
|
"ordinal": 143,
|
||||||
|
"parent_title": "Configuring Networks",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Group and Tenant Access",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
|
||||||
|
"clustering_title": "Group and Tenant Access"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
|
||||||
|
"clustering_title": "Group and Tenant Access"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,3 @@
|
|||||||
|
# Group and Tenant Access
|
||||||
|
|
||||||
|
Networks can be configured to provide specific Group access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
|
||||||
|
"title": "Cloud-Init Agent install mode",
|
||||||
|
"ordinal": 39,
|
||||||
|
"parent_title": "Agent Install",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Cloud-Init Agent install mode",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
|
||||||
|
"clustering_title": "Cloud-Init Agent install mode"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
|
||||||
|
"clustering_title": "Cloud-Init Agent install mode"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,4 @@
|
|||||||
|
# Cloud-Init Agent install mode
|
||||||
|
|
||||||
|
- Cloud-Init is configured in Administration > Settings > Provisioning section
|
||||||
|
- Provisioned image has Cloud-Init (Linux) or Cloudbase-Init (Windows) installed
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
|
||||||
|
"title": "Activity",
|
||||||
|
"ordinal": 20,
|
||||||
|
"parent_title": "Operations",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Activity",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
|
||||||
|
"clustering_title": "Activity"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
|
||||||
|
"clustering_title": "Activity"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
# Activity
|
||||||
|
|
||||||
|
The Activity section displays a recent activity report for Auditing. VM Essentials defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, etc… This view can be searched and filtered by type, user, and date range.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html)**
|
||||||
|
- **[Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html)**
|
||||||
|
- **[History](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html)**
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
|
||||||
|
"title": "Add ArubaCX Integration to a Cluster",
|
||||||
|
"ordinal": 354,
|
||||||
|
"parent_title": "ArubaCX Network Integration",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Add ArubaCX Integration to a Cluster",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
|
||||||
|
"clustering_title": "Add ArubaCX Integration to a Cluster"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
|
||||||
|
"clustering_title": "Add ArubaCX Integration to a Cluster"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,10 @@
|
|||||||
|
# Add ArubaCX Integration to a Cluster
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. In Infrastructure > Clusters select the target Cluster
|
||||||
|
2. Select the Edit icon for the Cluster
|
||||||
|
3. In the “Integrations” dropdown, select an available ArubaCX Integration
|
||||||
|
4. Save Changes
|
||||||
|
|
||||||
|
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
|
||||||
|
"title": "Group Access",
|
||||||
|
"ordinal": 160,
|
||||||
|
"parent_title": "Editing Domain Permissions",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-06426E05-BE70-4917-89E3-153236303513.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Group Access",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
|
||||||
|
"clustering_title": "Group Access"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
|
||||||
|
"clustering_title": "Group Access"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,3 @@
|
|||||||
|
# Group Access
|
||||||
|
|
||||||
|
The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
|
||||||
|
"title": "Currency Settings",
|
||||||
|
"ordinal": 271,
|
||||||
|
"parent_title": "Appliance",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Currency Settings",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
|
||||||
|
"clustering_title": "Currency Settings"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
|
||||||
|
"clustering_title": "Currency Settings"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,3 @@
|
|||||||
|
# Currency Settings
|
||||||
|
|
||||||
|
In VM Essentials, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, VM Essentials allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
|
||||||
|
"title": "NFSv3 File Shares",
|
||||||
|
"ordinal": 189,
|
||||||
|
"parent_title": "Storage",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "NFSv3 File Shares",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
|
||||||
|
"clustering_title": "NFSv3 File Shares"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
|
||||||
|
"clustering_title": "NFSv3 File Shares"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,80 @@
|
|||||||
|
# NFSv3 File Shares
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
|
||||||
|
|
||||||
|
NOTE
|
||||||
|
|
||||||
|
Upon save VM Essentials will create a persistent mount owned by `morpheus-app.morpheus-app` on the VM Essentials Appliance for the NFSv3 File Share. The VM Essentials appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before VM Essentials is able to successfully mount the share.
|
||||||
|
|
||||||
|
To Add a NFSv3 File Share:
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Select the Infrastructure link in the navigation bar.
|
||||||
|
2. Select the Storage link in the sub navigation bar.
|
||||||
|
3. In the FILE SHARES tab, Click the + ADD button.
|
||||||
|
4. Select NFSv3 from the dropdown list
|
||||||
|
5. From the NEW FILE SHARE Wizard input the following:
|
||||||
|
|
||||||
|
NAME
|
||||||
|
: Name of the File Share in VM Essentials.
|
||||||
|
|
||||||
|
HOST
|
||||||
|
: Enter the File Share path on the local VM Essentials Appliance.
|
||||||
|
|
||||||
|
EXPORT FOLDER
|
||||||
|
: Enter the NFSv3 Folder
|
||||||
|
|
||||||
|
Default Backup Target
|
||||||
|
: Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
|
||||||
|
|
||||||
|
Archive Snapshots
|
||||||
|
: Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
|
||||||
|
|
||||||
|
Default Deployment Archive Target
|
||||||
|
: Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
|
||||||
|
|
||||||
|
Default Virtual Image Store
|
||||||
|
: Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
|
||||||
|
|
||||||
|
RETENTION POLICY
|
||||||
|
: None
|
||||||
|
: Files in the File Share will not be automatically deleted or backed up.
|
||||||
|
|
||||||
|
Backup Old Files
|
||||||
|
: This option will backup files after a set amount if time and remove them from the File Share.
|
||||||
|
: DAYS OLD
|
||||||
|
: Files older than the set number of days will be automatically backed up to the selected Backup File Share.
|
||||||
|
|
||||||
|
BACKUP File Share
|
||||||
|
: Search for and select the File Share the files will be backed up to.
|
||||||
|
|
||||||
|
DELETE OLD FILES
|
||||||
|
: This option will delete files from this File Share after a set amount of days.
|
||||||
|
: DAYS OLD
|
||||||
|
: Files older than the set number of days will be automatically deleted from the File Share.
|
||||||
|
6. Select SAVE CHANGES
|
||||||
|
|
||||||
|
## Results
|
||||||
|
|
||||||
|
The File Share will be created and displayed in the File Shares tab.
|
||||||
|
|
||||||
|
- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
|
||||||
|
- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
|
||||||
|
|
||||||
|
WARNING
|
||||||
|
|
||||||
|
Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
|
||||||
|
- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
|
||||||
|
|
||||||
|
WARNING
|
||||||
|
|
||||||
|
When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html)**
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
|
||||||
|
"title": "Add HPE Alletra MP Storage",
|
||||||
|
"ordinal": 366,
|
||||||
|
"parent_title": "HPE Alletra MP Storage",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Add HPE Alletra MP Storage",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
|
||||||
|
"clustering_title": "Add HPE Alletra MP Storage"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
|
||||||
|
"clustering_title": "Add HPE Alletra MP Storage"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,33 @@
|
|||||||
|
# Add HPE Alletra MP Storage
|
||||||
|
|
||||||
|
## About this task
|
||||||
|
|
||||||
|
The first step is to create a storage server in VM Essentials. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
|
||||||
|
|
||||||
|
## Procedure
|
||||||
|
|
||||||
|
1. Navigate to Infrastructure > Storage
|
||||||
|
2. In the “Servers” tab, Click the + ADD button
|
||||||
|
3. From the ADD STORAGE SERVER wizard, input the following:
|
||||||
|
|
||||||
|
NAME:
|
||||||
|
: Name of the storage server in VM Essentials
|
||||||
|
|
||||||
|
TYPE:
|
||||||
|
: Select “HPE Alletra MP”
|
||||||
|
|
||||||
|
URL:
|
||||||
|
: URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
|
||||||
|
|
||||||
|
USERNAME:
|
||||||
|
: Add your administrative user account
|
||||||
|
|
||||||
|
PASSWORD:
|
||||||
|
: Add your administrative user account password
|
||||||
|
4. Select SAVE CHANGES
|
||||||
|
|
||||||
|
## Results
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The Storage Server will be added and displayed in the Datastore tab.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
|
||||||
|
"title": "Plans",
|
||||||
|
"ordinal": 238,
|
||||||
|
"parent_title": "Administration",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Plans",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
|
||||||
|
"clustering_title": "Plans"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
|
||||||
|
"clustering_title": "Plans"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# Plans
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html)**
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
|
||||||
|
"title": "Cloud Detail View",
|
||||||
|
"ordinal": 93,
|
||||||
|
"parent_title": "Clouds",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Cloud Detail View",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
|
||||||
|
"clustering_title": "Cloud Detail View"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
|
||||||
|
"clustering_title": "Cloud Detail View"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,22 @@
|
|||||||
|
# Cloud Detail View
|
||||||
|
|
||||||
|
The Cloud Detail view shows metrics on health, sync status, resource utilization statistics, and resource counts for hosts, virtual machines, or any other constructs under the umbrella of the selected Cloud.
|
||||||
|
|
||||||
|
From the Cloud list page, select the name of a Cloud to display that Cloud’s detail page. You’ll notice the following actions are available:
|
||||||
|
|
||||||
|
EDIT
|
||||||
|
: Edit the setup configuration of the Cloud.
|
||||||
|
|
||||||
|
REFRESH
|
||||||
|
: Force a sync with the Cloud.
|
||||||
|
|
||||||
|
DELETE
|
||||||
|
: Delete the Cloud from VM Essentials.
|
||||||
|
|
||||||
|
IMPORTANT
|
||||||
|
|
||||||
|
All Instances, managed Hosts, and VMs associated with the Cloud must be removed prior to deleting a Cloud.
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Cloud Detail Tabs](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html)**
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
|
||||||
|
"title": "Environments",
|
||||||
|
"ordinal": 286,
|
||||||
|
"parent_title": "Settings",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Environments",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
|
||||||
|
"clustering_title": "Environments"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
|
||||||
|
"clustering_title": "Environments"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,5 @@
|
|||||||
|
# Environments
|
||||||
|
|
||||||
|
**Subtopics**
|
||||||
|
|
||||||
|
- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html)**
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
|
||||||
|
"title": "Overview",
|
||||||
|
"ordinal": 356,
|
||||||
|
"parent_title": "HPE Aruba CX DSS",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Overview",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
|
||||||
|
"clustering_title": "Overview"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
|
||||||
|
"clustering_title": "Overview"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
@@ -0,0 +1,11 @@
|
|||||||
|
# Overview
|
||||||
|
|
||||||
|
The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus VM Essentials Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
|
||||||
|
|
||||||
|
Implemented as a VM Essentials `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for VM Essentials environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM cluster.
|
||||||
|
|
||||||
|
On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. VM Essentials integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM hosts in the HVM cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
|
||||||
|
|
||||||
|
The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM cluster.
|
||||||
|
|
||||||
|
Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
|
||||||
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_0",
|
||||||
|
"page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
|
||||||
|
"title": "Editing Domain Permissions",
|
||||||
|
"ordinal": 159,
|
||||||
|
"parent_title": "Domains",
|
||||||
|
"doc_id": "sd00007520en_us",
|
||||||
|
"version": "8.1.0",
|
||||||
|
"product": "User Manual",
|
||||||
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html",
|
||||||
|
"topic_cluster": {
|
||||||
|
"clustering_title": "Editing Domain Permissions",
|
||||||
|
"clustered_topics": [
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_1",
|
||||||
|
"page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
|
||||||
|
"clustering_title": "Editing Domain Permissions"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"bundle_id": "hvm_user_manual_8_1_2",
|
||||||
|
"page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
|
||||||
|
"clustering_title": "Editing Domain Permissions"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}
|
||||||
|
}
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user