vSphere 8-ийн дэмжлэг дуусах нь VMware орчноо заавал солих гэсэн үг биш

Published:

Энэхүү мэдээ, нийтлэлийг хиймэл оюун боловсруулав.

2027 оны аравдугаар сарын 11-нд ерөнхий дэмжлэг дуусах ч гуравдагч талын үйлчилгээ байгууллагуудад шинэчлэл, шилжилтийн хугацааг тусад нь төлөвлөх боломж олгоно.

VMware-ийн vSphere 8 хувилбарын ерөнхий дэмжлэг 2027 оны аравдугаар сарын 11-нд дуусна. Томоохон байгууллагуудад орчноо үнэлэх, хамаарлуудыг шалгах, шинэчлэх эсвэл өөр виртуалчлалын платформ руу шилжих ажил хэдэн сараас ч удаан үргэлжилж болзошгүй.

Үйлдвэрлэлийн орчны шинэчлэл нь зөвхөн программ хангамж солихоор хязгаарлагдахгүй: аппликейшн, интеграц, нөөцлөлт, сэргээх үйл явц болон дэд бүтцийн хамаарлыг хамарна. Ялангуяа гиперконвергент дэд бүтэц ашигладаг байгууллагад шинэчлэл хийхэд техник хангамж солих шаардлага гарч, зардал нэмэгдэж болзошгүй.

Зарим байгууллага VMware Cloud Foundation-ийн захиалга авсан ч ажлын ачааллаа vSphere 9 рүү шилжүүлэлгүй vSphere 8 дээр ажиллуулсаар байна. Ингэснээр Broadcom-ийн захиалгын загварт шилжсэн боловч техникийн шинэчлэл хийгдээгүй бөгөөд захиалга нь шинэ платформ нэвтрүүлэх ажлыг эсвэл бизнесийн үндэслэлийг орлохгүй.

2027 оны аравдугаар сараас хойш vSphere 8 ашиглах байгууллагууд гуравдагч талын дэмжлэг авч, урт хугацааны платформын шийдвэрээ гаргах хүртэл шилжилтээ үе шаттай хийх боломжтой. Гэхдээ үйлдвэрлэгчийн шинэчлэл, хамгаалалтын нөхөөсгүй үед эмзэг байдлыг орчны тохиргоотой уялдуулан үнэлж, тохиргоог бэхжүүлэх, сүлжээг сегментчлэх, хандалтыг хянах зэрэг хамгаалалтыг хэрэгжүүлэх шаардлагатай. Дэмжлэгийн хугацаа дуусахад бэлтгэх нь зайлшгүй ч энэ нь дэд бүтцийг хэзээ, хэрхэн өөрчлөхийг дангаараа шийдэх ёсгүй.

Дэлгэрэнгүйг эх сурвалжаас харах

↓Эх сурвалжийг нээх ↓

Having supported VMware customers through both vendor and independent support roles for over a decade, I’ve seen many organizations plan and execute major upgrades. The software change itself is only one part of the work. In a mature VMware estate, an upgrade reaches into applications, integrations, infrastructure dependencies, operational processes, and the teams responsible for keeping critical services available.

Even a well-understood upgrade can become a substantial operational undertaking. Before a production environment changes, infrastructure teams need to understand how the wider estate will be affected, what needs to move in what order, where incompatibilities may appear, and how much risk the business is prepared to absorb. In large environments, that work can take months. A migration to another virtualization platform can take considerably longer.

That long lead time is exactly why the vSphere 8 support deadline matters now. General support ends on 11th October 2027, and for a large enterprise the remaining window may be shorter than the time needed to assess the estate, build a business case, test dependencies, and complete a major upgrade or migration safely.

The deadline creates two pressures at once: organizations need a plan for how vSphere 8 will be supported beyond October 2027, while also deciding whether the longer-term strategy is to upgrade, migrate or continue running parts of the existing estate for longer. For some customers, particularly those running hyperconverged infrastructure, an upgrade may also require a hardware refresh, adding significantly to the cost.

In practice, the commercial route to continued vendor support can bring those decisions together. Customers may move onto the newer subscription or upgrade path because that is what allows them to remain supported, even when they are not yet ready to make the corresponding technical change across the estate.

We are already seeing this play out. Some organizations have purchased VMware Cloud Foundation subscriptions but continue to run workloads on vSphere 8 rather than upgrading to vSphere 9. From a commercial perspective, they have moved onto Broadcom’s subscription model.

Technically, however, the estate remains where it was. That apparent contradiction says something important about the decision customers are facing. Purchasing a subscription does not remove the operational work involved in deploying a newer platform, nor does it automatically establish the business case for doing so. In a mature VMware estate, those considerations can take much longer to work through.

As 2027 approaches, VMware customers need a credible plan for supporting vSphere 8, alongside a longer-term view of where those workloads should ultimately run. The two decisions influence one another, but forcing them onto the same timetable can push organizations towards change before the business case. Technical readiness or migration plan is sufficiently developed.

Why the architecture decision deserves its own timetable

There is a tendency to think of an upgrade as a progression from one version of a product to the next. In enterprise infrastructure, the consequences are rarely so contained.

A mature VMware estate carries years of operational knowledge around it. Applications have been tested against the platform; backup and recovery processes have developed around it, and infrastructure teams understand how changes in one part of the environment affect another. None of that means the estate should be preserved indefinitely. But it does mean that replacing it carries a cost that extends beyond the new software or platform itself.

I saw this repeatedly during my time at VMware. Upgrades were one of the biggest drivers of support cases because changing the virtualization layer could expose compatibility problems or dependencies elsewhere in the stack.

A move may still be entirely justified. The current environment may be becoming harder to secure or maintain. Another platform may offer better value for money, or the organization may have infrastructure requirements that the existing estate can no longer meet.

For some CIOs, that assessment also includes vendor constraints and lock-in, and whether open source alternatives or complementary technologies could better support their longer-term virtualization strategy.

What matters is that those reasons come from the needs of the business and the condition of the environment. An approaching support deadline tells an organization that its current support arrangements need attention. It does not provide the business case for a wider infrastructure transformation.

Supporting vSphere 8 beyond the vendor deadline

For customers that expect to still be running vSphere 8 after October 2027, the choice is not simply between upgrading and continuing without support. Independent third-party support offers another option: supporting the existing environment while giving the organization time to assess and implement a longer-term platform decision.

That can be valuable in several different circumstances. A customer that has already decided to leave VMware may need years to migrate a large estate without creating unnecessary operational risk. Another may still be assessing newer VMware options against competing platforms. Some organizations may find that different groups of workloads need to move at different points rather than as part of one wholesale migration.

Third-party support does not make the VMware lifecycle irrelevant, and moving beyond vendor support requires a different approach to managing risk. Without the vendor patch stream, organizations need to understand vulnerabilities in the context of their own environment: how VMware is configured, where it is exposed, and what controls already sit around it.

That means taking a defense-in-depth approach, using measures such as configuration hardening, segmentation, access controls, and compensating controls where appropriate. The aim is not to suggest that patches no longer matter but to avoid treating them as the only way to manage security risk once an environment moves beyond the vendor support lifecycle.

What third-party support fundamentally changes is the amount of control the customer has over the timetable.

Using the support deadline to make a better decision

The October 2027 deadline should already be prompting VMware customers to examine their estates in detail. They need to understand how long existing workloads are likely to remain on vSphere 8, what maintaining those environments will require and where there is a genuine case for change.

For some organizations, that assessment will support an upgrade or migration before general support ends. Others will conclude that the right destination is clear but cannot responsibly be reached within the remaining support window. There will also be environments where the current platform continues to meet the needs of the business and changing it is not yet a priority.

Each of those positions still requires a support strategy, but the longer-term architecture decision may need to follow a different timetable.

An alternative support model allows those timelines to be managed separately. The end of vendor support still needs to be planned for, but it does not have to determine when a wider infrastructure change takes place. That decision can instead be based on the technical requirements of the estate, the operational risk involved in changing it and the economics of the available options.

The support deadline requires a plan. It does not have to dictate the future of the VMware estate.

We’ve featured the best cloud computing provider

This article was produced as part of TechRadar Pro Perspectives, our channel to feature the best and brightest minds in the technology industry today.

The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc. If you are interested in contributing find out more here: https://www.techradar.com/pro/perspectives-how-to-submit

Та юу гэж бодож байна?

Сэтгэгдлээ оруулна уу!
Please enter your name here

MFC.mn сайтад сэтгэгдэл оруулахад анхаарах зүйлс

Холбоотой

spot_img

Шинэ

spot_img