Skip to content

Commit 62e439a

Browse files
authored
Merge pull request #7767 from ovh/YC-Fixes-20250417
Fixes and duplication for several guides (VMware / Data Platform / AI)
2 parents 1dd8a94 + d1a0e26 commit 62e439a

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

75 files changed

+910
-322
lines changed
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Updating hosts using vSphere Lifecycle Management (vLCM)
3+
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4+
updated: 2025-04-17
5+
---
6+
7+
## Objective
8+
9+
This guide explains how to update your ESXi hosts using vSphere Lifecycle Management (vLCM), directly from the vSphere interface. vLCM helps you detect required updates and keep your hosts up to date quickly and securely by applying a complete image.
10+
11+
Unlike VMware Update Manager, vLCM provides a full lifecycle approach by including software updates, drivers, firmware, and hardware components. This gives you a centralised view of your hosts’ status and helps you make informed decisions to maintain performance and security.
12+
13+
## Requirements
14+
15+
- Your vCenter must be running **vSphere 8** to access the vLCM feature.
16+
- Make sure the **DRS (Distributed Resource Scheduler)** feature is enabled in automatic mode.
17+
- Check that your `.iso` or `.vmdk` files are not stored locally on the hosts.
18+
19+
## Instructions
20+
21+
### Step 1: Log in to vSphere
22+
23+
Log in to your vSphere interface, then select the **host cluster** you want to update.
24+
25+
### Step 2: Select a new image
26+
27+
Go to `Updates > Hosts > Image`{.action} to view the current image.
28+
29+
![Viewing the current image in vLCM](images/vlcm_00.png){.thumbnail}
30+
31+
Click `Edit`{.action} to modify the image.
32+
33+
![Edit button to modify the image](images/vlcm_01.png){.thumbnail}
34+
35+
From the dropdown list, select the desired ESXi version. The first option usually corresponds to the latest version published by Broadcom.
36+
37+
Click `Save`{.action} to confirm and save the selected image.
38+
39+
![Selecting a new ESXi version](images/vlcm_02.png){.thumbnail}
40+
41+
> ![primary]
42+
> OVHcloud recommends always using the suggested version. Avoid downgrading to a previous version.
43+
44+
Your image is now loaded.
45+
46+
### Step 3: Launch the update
47+
48+
Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
49+
50+
![Launching with Remediate All](images/vlcm_03.png){.thumbnail}
51+
52+
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
53+
54+
Before launching the update, make sure that:
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
59+
60+
Click `Start Remediation`{.action} to begin the process.
61+
62+
![Start Remediation](images/vlcm_04.png){.thumbnail}
63+
64+
The update process is now running. It may take several minutes per host.
65+
66+
![Final validation](images/vlcm_05.png){.thumbnail}
67+
68+
## Go further
69+
70+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
71+
72+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
73+
74+
Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-asia.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

@@ -70,4 +71,4 @@ If you need training or technical assistance to implement our solutions, please
7071

7172
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
7273

73-
Join our [community of users](/links/community).
74+
Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-au.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

@@ -70,4 +71,4 @@ If you need training or technical assistance to implement our solutions, please
7071

7172
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
7273

73-
Join our [community of users](/links/community).
74+
Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-ca.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

@@ -70,4 +71,4 @@ If you need training or technical assistance to implement our solutions, please
7071

7172
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
7273

73-
Join our [community of users](/links/community).
74+
Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-gb.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-ie.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

@@ -70,4 +71,4 @@ If you need training or technical assistance to implement our solutions, please
7071

7172
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
7273

73-
Join our [community of users](/links/community).
74+
Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-sg.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

@@ -70,4 +71,4 @@ If you need training or technical assistance to implement our solutions, please
7071

7172
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
7273

73-
Join our [community of users](/links/community).
74+
Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_update_esxi_vlcm/guide.en-us.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Updating hosts using vSphere Lifecycle Management (vLCM)
33
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4-
updated: 2025-04-16
4+
updated: 2025-04-17
55
---
66

77
## Objective
@@ -52,9 +52,10 @@ Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
5252
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
5353

5454
Before launching the update, make sure that:
55-
- The **DRS** feature is enabled in automatic mode;
56-
- No anti-affinity rules are preventing virtual machine relocation;
57-
- No `.iso` or `.vmdk` files are stored locally on the hosts.
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
5859

5960
Click `Start Remediation`{.action} to begin the process.
6061

@@ -70,4 +71,4 @@ If you need training or technical assistance to implement our solutions, please
7071

7172
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
7273

73-
Join our [community of users](/links/community).
74+
Join our [community of users](/links/community).
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Updating hosts using vSphere Lifecycle Management (vLCM)
3+
excerpt: Learn how to update your ESXi hosts via vSphere Lifecycle Management quickly and securely.
4+
updated: 2025-04-17
5+
---
6+
7+
## Objective
8+
9+
This guide explains how to update your ESXi hosts using vSphere Lifecycle Management (vLCM), directly from the vSphere interface. vLCM helps you detect required updates and keep your hosts up to date quickly and securely by applying a complete image.
10+
11+
Unlike VMware Update Manager, vLCM provides a full lifecycle approach by including software updates, drivers, firmware, and hardware components. This gives you a centralised view of your hosts’ status and helps you make informed decisions to maintain performance and security.
12+
13+
## Requirements
14+
15+
- Your vCenter must be running **vSphere 8** to access the vLCM feature.
16+
- Make sure the **DRS (Distributed Resource Scheduler)** feature is enabled in automatic mode.
17+
- Check that your `.iso` or `.vmdk` files are not stored locally on the hosts.
18+
19+
## Instructions
20+
21+
### Step 1: Log in to vSphere
22+
23+
Log in to your vSphere interface, then select the **host cluster** you want to update.
24+
25+
### Step 2: Select a new image
26+
27+
Go to `Updates > Hosts > Image`{.action} to view the current image.
28+
29+
![Viewing the current image in vLCM](images/vlcm_00.png){.thumbnail}
30+
31+
Click `Edit`{.action} to modify the image.
32+
33+
![Edit button to modify the image](images/vlcm_01.png){.thumbnail}
34+
35+
From the dropdown list, select the desired ESXi version. The first option usually corresponds to the latest version published by Broadcom.
36+
37+
Click `Save`{.action} to confirm and save the selected image.
38+
39+
![Selecting a new ESXi version](images/vlcm_02.png){.thumbnail}
40+
41+
> ![primary]
42+
> OVHcloud recommends always using the suggested version. Avoid downgrading to a previous version.
43+
44+
Your image is now loaded.
45+
46+
### Step 3: Launch the update
47+
48+
Click `Remediate All`{.action} to apply the image to all hosts in the cluster.
49+
50+
![Launching with Remediate All](images/vlcm_03.png){.thumbnail}
51+
52+
This action triggers the maintenance mode for the affected hosts. Virtual machines will be automatically moved using **vMotion**.
53+
54+
Before launching the update, make sure that:
55+
56+
- The **DRS** feature is enabled in automatic mode.
57+
- No anti-affinity rules are preventing virtual machine relocation.
58+
- No `.iso` or `.vmdk` files are stored locally on the hosts.
59+
60+
Click `Start Remediation`{.action} to begin the process.
61+
62+
![Start Remediation](images/vlcm_04.png){.thumbnail}
63+
64+
The update process is now running. It may take several minutes per host.
65+
66+
![Final validation](images/vlcm_05.png){.thumbnail}
67+
68+
## Go further
69+
70+
If you need training or technical assistance to implement our solutions, please contact your Technical Account Manager or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
71+
72+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
73+
74+
Join our [community of users](/links/community).

0 commit comments

Comments
 (0)