We’re excited to announce two new VMmark results today from Dell Technologies:

• First VCF 9.1 Benchmarks: These are the first results using VMware Cloud Foundation (VCF) 9.1. VCF 9.1 maximizes hardware efficiency using a Next-Gen Topology-Aware CPU Scheduler that optimizes memory and cache locality for intensive enterprise workloads. A separate VCF 9.1 evaluation demonstrated a 12% reduction in CPU utilization using its new Memory Tiering enhancements.
• First VMmark 4.1 Results: These results are also the first to use VMmark 4.1, the latest release of our free enterprise virtualization benchmarking tool. While VMmark 4.0 measures private cloud performance and scalability, VMmark 4.1 adds power measurement with a Performance Per Kilowatt (PPKW) score. For example, Dell’s new Server Power-Performance result is 1.5255 PPKW @ 4.6 tiles. This can be helpful for understanding and comparing how much power different environments need to complete the same amount of work.

Using the exact same servers, processors, and storage array, the new VCF 9.1 results outperformed VCF 5.2 with an 11% higher performance score and a 10% higher tile count. This means that for this environment, simply upgrading to VCF 9.1 allowed more VMs to be run, completing even more work. The hardware configuration and benchmark score comparisons are detailed below:

VMmark 4

VMware VMmark 4 is a free cluster-level benchmarking tool used by hardware vendors and others to measure the performance and scalability of enterprise virtualization environments that has become the standard tool for this purpose. If you’d like to learn more about VMmark 4, refer to the resources below:

• VMmark 4.1: Enhanced Power Efficiency Benchmarking for Private Cloud Infrastructure
• VMmark 4 Results
• VMmark FAQ (Scores, Tiles, Use Cases)
• VMmark Download
• Try VMmark 4.1 in less than 60 seconds via VMware Hands-on Labs:
  VMmark 4.1: Performance Benchmarking Real-World Application Workloads in VCF 9.1 (Module 3)

VMmark^® is a product of Broadcom, Inc.

The post First VMmark 4.1 Power-Performance and VMware Cloud Foundation 9.1 Results appeared first on VMware Cloud Foundation (VCF) Blog.

The post First VMmark 4.1 Power-Performance and VMware Cloud Foundation 9.1 Results appeared first on VMware Blogs.

第一回：2026年、メインフレーム・モダナイゼーションの現在地 メインフレーム（汎用コンピュータ）は、日本の社会インフラや主要企業の基幹業務システムにおいて、長年にわたり高い堅牢性と信頼性を提供してきました。IBMのz/OS、富士通のXSP/OSIV、NECのACOSなど、各社が独自に発展させたプラットフォームは、現在も重要インフラを支えています。しかし2026年現在、主要メーカーによるメインフレーム事業の撤退・サポート終了方針の提示、および保守を担うベテラン技術者の定年退職によるスキル継承の限界から、事業継続上の実害を伴う課題が顕在化しています。 こうした状況下において企業に求められるのは、単なるシステムの延命ではなく、自社のデータに対する統制（データ主権）を維持し、将来的なデータ活用を見据えたシステムアーキテクチャの再設計です。 本稿では、メインフレームのモダナイゼーションにおける選択肢として、オンプレミス環境や各種クラウド基盤の特性およびリスクを比較・整理することで、失敗しない移行への第一歩を考えます。   1. 確実性を高めるアプローチとインフラの選択肢 メインフレーム脱却において重要な検討事項は、移行後におけるシステム性能、可用性、セキュリティなどの非機能要件の維持です。 プログラム言語の変換のみでは、基幹システムとしての要求水準を満たすことはできません。この課題に対して、VMwareのTanzuアーキテクチャチームが公開している技術指針（An Architecture Path to Mainframe Modernization）では、一括刷新（ビッグバン移行）に伴う処理結果の不一致や障害リスクを回避するため、段階的な移行手法が推奨されています。具体的には、アプリケーション層において、現行システムを稼働させながら、重要な機能やデータを単位ごとに新環境へ段階的に移行する手法（Stranglerパターン）を適用します。そして、それを受け止めるインフラ層として、自社統制が可能なVMware環境上のLinux基盤を採用することにより、既存のビジネスロジックを活用しつつ、メインフレームと同等の応答性や可用性を維持することが可能となります。 一方で、パブリッククラウド各社が公開している情報をもとに直接パブリッククラウドのネイティブ環境へ移行するルートを検討する企業も少なくありません。パブリッククラウドは最新のAI機能や外部サービスと手軽に連携できるメリットがありますが、基幹システムをそのまま持ち込む際には把握しておくべき現実的な注意点があります。   共有環境（マルチテナント）における非機能要件の課題 他社と物理リソースを共有する構成では、ミリ秒単位の低遅延処理や、他システムの負荷影響を排除したリソース隔離の再現が困難です。 専用（占有）環境におけるコストおよび為替リスク 上記の課題を回避するために占有環境を採用した場合、初期費用および運用費用が高騰しやすくなります。また、サービス特有のドル建て課金体系により、為替変動（ドル高・円安）や国際情勢の影響を受けて中長期的なインフラコストが不透明化するリスクがあります。 データ主権に関わるリスク 米国クラウド法（CLOUD Act）に基づく国外法執行機関からのデータアクセス要求の可能性や、暗号鍵の管理権限を事業者に依存することによるデータ閲覧リスクなど、データ統制上の課題が生じます。   現在では、オンプレミスの堅牢性とクラウドの柔軟性を両立させるアプローチとして、国内事業者によるソブリンクラウドや、ハイパースケーラー上で展開される専有VMware基盤（VMC on AWS, AVS, OCVS等）も有力な選択肢となっています。コスト・性能・法制度リスクを多角的に評価した上で、適材適所の配置を行うことが不可欠です。   2. 2026年における移行戦略と仕分け 規約や為替リスクを回避し、自社主導でデータを管理・運用するための移行パターンとして、代表的な3つのアプローチを整理します。 移行パターン 具体的なアプローチ 2026年現在の評価とリスク 1. リプレイス （全面手組み刷新） システムを解体し、パッケージ導入またはゼロから再構築します。 数千万行規模のビジネスロジックの再設計を伴うため、膨大なコストと期間を要します。現行システムとの処理結果の相違等により、長期化・頓挫リスクが高くなります。 2. リホスト （クラウド直接移行） 現行プログラムをパブリッククラウドの仮想マシンへそのまま移行します。 移行期間の短縮は見込めるものの、共有環境における処理遅延、占有環境採用時のコスト高騰・為替リスク、および国外法制度に伴うデータ統制上のリスクが存在します。 3. リファクター （自動リライト＋次世代インフラ） 変換ツールを用いてモダン言語（Java等）へ機能等価で一括変換し、自社統制が可能なインフラへ移行します。 アプリケーションの書き換えリスクを最小化しつつ非機能要件を確保できます。パブリッククラウド直行のリスクを回避し、データ主権を維持する現実的な選択肢となります。   現在、移行を成功させている企業では、パターン3の採用が多くみられます。 実績のある自動変換ツールを用いてアプリケーション層の資産をJava等へ安全に移行し、受け皿となるインフラ層には、高い物理性能とセキュリティを維持できるソフトウェア定義プラットフォームを、オンプレミスや、ハイパースケーラー上で展開される専有VMware基盤上に構築します。アプリケーションのモダナイゼーションとインフラ基盤のモダナイゼーションを適切に役割分担することが、確実性の高い解決策となります。   … 続き

The post VCF9で完遂するメインフレーム・モダナイゼーション appeared first on VMware Japan Blog.

The post VCF9で完遂するメインフレーム・モダナイゼーション appeared first on VMware Blogs.

In this episode of VCF Breakroom Chats, Anika Suri sits down with Abhishek Rao from Tigera, the company behind Project Calico, to discuss a critical aspect of running Kubernetes in production: networking and security.

Want to learn more about this partnership?

1. Check out the Kubernetes Ecosystem Partners page  for more resources.
2. Read this blog post.

About the VCF Breakroom Chat Series

​In this series, we share vlogs with industry-recognized experts from Broadcom and Broadcom partners and customers. These vlogs are concise, like meeting in a breakroom and getting great information from a quick conversation. This series is for you if you are an IT practitioner: IT admin, cloud or platform architect, platform engineer, developer, DevOps, senior IT manager, IT executive, or AI/ML professional. 

If you are new to the series, please check out our previous episodes.

The post VCF Breakroom Chats Episode 94: Supercharging VKS Networking with Tigera appeared first on VMware Cloud Foundation (VCF) Blog.

The post VCF Breakroom Chats Episode 94: Supercharging VKS Networking with Tigera appeared first on VMware Blogs.

An AI-ready private cloud is not simply a private cloud with GPUs added to it. What determines whether a private cloud platform can actually serve AI workloads effectively is everything built around them: how the fabric carries traffic, how the tenancy model lets teams consume capacity, and how policy and telemetry stay coherent across the virtual and physical boundary. Networking is a key component in the future of the datacenter, and it introduces new and interesting challenges.

This is where the joint work VMware and Cisco are doing across VMware Cloud Foundation (VCF) and Cisco Nexus One Fabric matters. This is work customers have been asking for, and we’re excited to deliver on this. So let’s take a look at what we’ve been doing and especially why.

AI workloads change the traffic profile in both directions

Traditional enterprise virtualization produced a reasonably stable pattern. Most traffic stayed east-west inside the cluster. North-south was the smaller, better-understood fraction, which is why concentrating it through a centralised gateway was a sound design.

AI workloads are changing the general assumptions of network traffic – they have their own patterns and they tend to go both East-West and North-South but in a more intensely saturated fashion.

• East-west becomes bandwidth-dominant and latency-sensitive during distributed training. Gradient synchronization across nodes is a collective operation, and a collective finishes when its slowest participant finishes. A single congested link does not degrade the job proportionally; it sets the pace for every GPU in the ring. This is why AI fabrics are engineered for lossless or near-lossless behaviour with RoCEv2, priority flow control, and explicit congestion notification, and why buffer behaviour on the leaf matters far more than it does for a general-purpose workload.
• North-south becomes bursty and unpredictable. Training data is pulled from object storage that frequently sits outside the cluster. Model artifacts move between development, staging, and production environments that are not colocated. Inference endpoints serve consumers across the enterprise and sometimes outside it. Retrieval-augmented pipelines make external calls on the request path, which puts north-south latency directly into user-facing response time.

You cannot size a fixed north-south chokepoint for that profile, because the profile changes every time a team ships a new model.

Distributed forwarding, and why it follows from the above

VCF 9.1 introduces the distributed Transit Gateway. North-south forwarding moves onto the ESX hosts themselves. Each host forwards for its own VMs, encapsulates in VXLAN, and hands traffic to its local leaf. The Route Controller maintains BGP EVPN peering with the fabric on behalf of the hosts, so the control plane remains centralised and operationally manageable while the data plane is not.

Some practical and noteworthy consequences:

Egress capacity scales with host count. Adding GPU nodes to a training cluster adds north-south capacity at the same time, rather than pushing an existing shared gateway closer to saturation.

The path is one hop to the fabric. A packet leaving a VM is encapsulated on its own host and lands on the leaf that host is cabled to. Latency stops depending on where a gateway appliance was placed relative to the workload.

ECMP across leaf uplinks applies to the traffic immediately. Hash distribution happens across the fabric’s full uplink set rather than across whatever the gateway’s own connectivity happens to be.

Host capacity previously dedicated to edge appliances returns to workloads. In an environment where GPU-attached hosts are the expensive resource, not spending general-purpose capacity on a forwarding tier is worth accounting for.

One encapsulation, one control plane

The integration point between VCF and a Cisco Nexus One fabric is BGP EVPN, spoken natively by both sides. Inside the workload domain, VCF Networking uses GENEVE between hosts. At the boundary, the Transit Gateway encapsulates in VXLAN and the Route Controller exchanges routes with the leaf switches over BGP EVPN. There is no gateway translating between the two models.

A single EVPN control plane means a MAC or IP that moves is a control plane event visible on both sides, which is the difference between correlating a workload move against fabric state and inferring it. It means troubleshooting a path involves one route table concept rather than two, examined from either end. And it means the fabric’s own telemetry has something to correlate against.

On the Cisco side, the Nexus One approach keeps this consistent across ACI, NX-OS, and SONiC choices and brings together on-premises and cloud-managed operating models through Nexus Dashboard and Nexus Hyperfabric respectively, sharing a VXLAN EVPN data plane, a common policy construct in Endpoint Security Groups, and common visibility, under a unified architecture. The fabric operating model your network team prefers and the VCF integration are separable decisions. The protocol interface is the same either way.

Telemetry and observability across platforms

For AI workloads the interesting failures are not link-down events. They are the ones where a training job takes 40% longer this week than last week and nothing is obviously broken. Diagnosing that requires seeing microburst behavior, buffer occupancy, and ECN marking rates on the fabric, and correlating those against workload placement and VM-level counters on the platform.

What makes that correlation possible is the route exchange itself. The Route Controller advertises endpoint MAC and IP addresses and subnet prefixes into the fabric as EVPN routes, and the leaf installs them in its own table. In the data plane, the source VTEP is the originating ESX host. Previously the Tier-0 summarised everything behind a few edge node interfaces, so the fabric saw traffic but not who was sending it.

ASIC-assisted telemetry on the Nexus One side provides the fabric half at a granularity that polling cannot reach. Because both sides share EVPN state, workload identity is common between them. Buffer occupancy on a port resolves to a named host, and a vMotion arrives as a control plane update rather than being inferred after traffic shifts.

Consumption: building the public cloud model on premises

Infrastructure that requires a ticket for every subnet will be routed around. It’s happened before and it will absolutely happen again. 

The VPC model addresses this by fixing the boundary in advance. The provider, typically the network team, configures physical fabric access and pre-allocates network resources to tenants with quotas and limits. A tenant admin selects from the connectivity options the provider published and creates VPCs within that quota. A VPC admin creates subnets and attaches workloads.

Each layer operates independently inside limits set by the layer above. The network team is not approving subnets one at a time, and the AI team is not waiting on them. Isolation between tenants is enforced structurally, which matters when several teams share GPU infrastructure and their data cannot mix.

The compute side of the same picture

VCF delivers this against three consumption models on one control plane: VKS for Kubernetes-managed containers, KubeVM for declaratively managed VMs, and Containers as a Service for containers in vSphere Pods without Kubernetes scaffolding. A typical AI application uses more than one, with inference serving in containers and a vector or relational database in a VM, sharing namespace, RBAC, and quota.

Underneath, GPU vMotion with DRS and GPU reservations make accelerators schedulable resources rather than statically pinned hardware, and high-speed adapters and DPUs keep distributed training and multi-node inference off the CPU for data movement.

VMware’s support for Cilium as an alternative CNI add-on for VKS 3.6 and later adds another important dimension. It gives VKS customers a supported path to an eBPF-based data plane, and Kubernetes and Cilium network policy. Separately, Cisco’s supported Nexus One–Isovalent integration shows how Cilium-based workloads can participate natively in an EVPN-VXLAN fabric. 

These are complementary developments. The strategic value is that each layer can do its job while aligning around open interfaces: VCF provides the private cloud and VPC consumption model; VKS provides Kubernetes lifecycle and platform operations; Cilium provides cloud-native networking, security, and observability; and Nexus One provides the network fabric and consistent network operating model that connects those domains to the rest of the enterprise.

Designing for the AI-ready datacenter

Measure current north-south utilisation before sizing anything; most teams have never had a reason to and the shape is usually not what they expect. Treat buffer and congestion behaviour on the leaf as a first-class design input. Decide the provider and tenant boundary before the first VPC exists. And plan capacity as a growth curve tied to host count, which is the property distributed forwarding gives you.

The result is a platform where adding AI workloads is a capacity decision, not an architecture project.

Conclusions and where this goes

None of this requires starting over – it’s exactly the opposite. It’s taking advantage of what you already have. The Nexus One fabric already speaks EVPN, and so does VCF. What changed is that the two halves now exchange state directly rather than meeting at an appliance that summarized away most of what each side needed from the other. The hardware is the hardware you bought, and the people who read BGP tables and the people who size workload domains are the ones who will operate it. 

The reason this matters is because the usual answer for AI infrastructure is a separate stack: its own fabric, its own operational model, its own team. That gets the first cluster running and becomes a problem at the second. Keeping these workloads on the same platform and the same fabric means capacity added for one purpose stays available for others, and the next class of workload is a capacity decision.

The post AI-Ready Private Cloud with Cisco and VMware appeared first on VMware Cloud Foundation (VCF) Blog.

The post AI-Ready Private Cloud with Cisco and VMware appeared first on VMware Blogs.

Enterprises running private cloud face a common question: what does the investment actually deliver? To answer it, we commissioned Forrester Consulting to conduct an independent New Technology Total Economic Impact (TEI) study on VMware Cloud Foundation 9 (VCF 9). Forrester interviewed decision-makers at organizations running VCF 9 and surveyed additional customers to develop a composite organization and financial model that quantifies the potential financial and operational impact of the solution.

The results are compelling and they are now available for you to explore in depth, both in the full study and in our recent on-demand webinar featuring guest speakers from the Forrester team.

About the Study and the Customers Behind It

Forrester Consulting conducted a 2026 commissioned New Technology Total Economic Impact (TEI) study based on eight one-on-one customer interviews and a survey of 55 customers. The study was modeled over a three-year period. The study reflects the experiences of large, complex enterprises running VCF 9 in production — organizations with significant infrastructure footprints, diverse workloads, and the operational challenges that come with scale. Their experiences informed the composite organization, assumptions, and financial analysis presented in the study.

Key Findings at a Glance

Forrester’s three-year projected financial analysis shows that VCF 9 delivers significant, measurable value across cost, efficiency, productivity, and risk.

Where the Value Comes From

The study quantifies benefits across six categories. In the study’s high-impact scenario, the projected benefits break down as a share of total quantified benefits as follows:

The big takeaway: in the study’s high-impact scenario, over 70% of quantified benefits came from two areas: lowering infrastructure costs through better utilization and workload consolidation, and reducing the operational effort needed to run infrastructure. Downtime reduction and faster delivery each contributed roughly 10-12%, while tool consolidation and security/compliance round out the remaining value.

The Customer Journey: Why Organizations Chose VCF 9

Before adopting VCF 9, interviewed organizations described complex, fragmented infrastructure environments built up over time through a mix of legacy systems and point solutions. Common challenges included slow provisioning, heavy manual coordination, tool sprawl, higher downtime risk, and mounting security and compliance overhead.

VCF 9 gave these organizations a way to unify and automate — bringing the agility, self-service, and consumption experience of public cloud together with the resilience and cost control of on-premises infrastructure. The TEI study quantifies what that transformation is worth in dollars, hours, and risk avoided.

Watch the Webinar: The Forrester TEI Study, on Demand

To go deeper into the methodology, the composite model, and the metrics that matter most to your business case, watch our on-demand webinar with the Forrester team.

[On-Demand video – Webinar video link here]

What you’ll learn

• The TEI methodology and how Forrester built the composite financial model
• The headline findings on infrastructure cost reduction, operational efficiency, developer productivity, and risk mitigation
• The metrics that matter most when building an internal business case or benchmarking your current environment
• Analyst perspective on what these results mean for enterprises evaluating or running VCF

Speakers

• Roger Nauth – Senior Consultant, Total Economic Impact Consulting Practice, Forrester
• Naveen Chhabra – Principal Analyst, Forrester Research
• Swapnil Gupta – Senior Product Marketing Manager, VCF Division, Broadcom

Whether you’re evaluating VCF, building an internal justification, or benchmarking your current environment, this session delivers the data and analyst perspective you need.

Read the Full Study

The complete Forrester Consulting TEI study walks through the methodology, the composite organization profile, the full benefits and costs analysis, and the risk-adjusted financial model behind these numbers.

Access the full Forrester New Technology TEI study for VMware Cloud Foundation 9 →

The Bottom Line

The Forrester TEI study makes the business case for VCF 9 concrete. The large, complex enterprise in the study stands to gain up to 137% projected ROI, along with meaningful improvements in delivery speed, developer productivity, and risk reduction.

These aren’t vendor claims. They come from an independent study based on real customer interviews and a disciplined financial model. Explore the study, watch the webinar, and use the findings to inform your own VCF 9 journey.

The post See How Organizations Achieved 137% ROI with VMware Cloud Foundation 9 appeared first on VMware Cloud Foundation (VCF) Blog.

The post See How Organizations Achieved 137% ROI with VMware Cloud Foundation 9 appeared first on VMware Blogs.

Starting with VMware Cloud Foundation (VCF) 9.0, VMware officially publishes OpenAPI specifications for VCF APIs. This is a major milestone for developers, enabling you to consume VCF APIs using your programming language of choice.

VMware provides first-class developer tooling such as VCF PowerCLI for PowerShell users and the VCF SDK offering Java and Python bindings. These out-of-the-box options may not cover all the developers wanting to consume VCF in their preferred programming language. In such scenarios, you can generate custom, strongly-typed API client libraries directly from the published OpenAPI specification.

This guide walks through the end-to-end process of generating a custom .NET C# API client using OpenAPI Generator. Beyond basic CLI usage, we will address real-world edge cases such as handling massive spec sizes and scoping API surfaces.

OpenAPI Specifications

The OpenAPI specification defines an open-source, machine readable, language agnostic API contract. It serves as a single source of truth, documenting API operations, components, and schema details in a machine-readable format. Because the specification is generated once by the API producer, developers can feed that same contract into various generator tools (OpenAPI Generator, Kiota, TypeSpec, or AutoRest) to produce native client bindings in their preferred programming language.

Installing OpenAPI Generator

OpenAPI Generator is a widely adopted, Java-based CLI tool capable of producing client SDKs across dozens of target languages. Because it runs on Java, ensure you have JRE/JDK 11 or higher installed on your system (unless you run it via Docker).

Installation Methods

1. Node.js / NPM (Recommended for CI/CD & Full-Stack):

2. OS Package Managers

3. Docker

4. Standalone Executable JAR

Generating a .NET Client for vSphere APIs

To demonstrate client generation for a real vSphere environment, we will target two distinct vSphere endpoints:

1. vSphere Automation REST API (/api): A modern, resource-oriented REST API for core inventory objects such as virtual machines, datastores, folders, and resource pools.
2. Virtual Infrastructure JSON API (/sdk/vim25): A JSON-RPC equivalent of the classic SOAP API endpoint, offering complete API coverage across core vSphere and vSAN capabilities.

Here is the OpenAPI generator command that will generate the .Net CSharp client SDK for both these API interfaces.

Let us understand the command and its provided argument in detail.

Increase JVM Memory Limits for vSphere OpenAPI Specifications

When parsing enterprise-scale specs, the generator’s underlying YAML parser (SnakeYAML) will crash if the document exceeds its default safety limit (~3 MB of code points).

To prevent memory limit exceptions, pass the maxYamlCodePoints system property directly to the JVM before invocation:

Specify the Generator and Targeted Framework

The OpenAPI C# generator supports multiple underlying HTTP clients (such as RestSharp and HttpClient). Here, we target RestSharp, pinning the build target to .NET 8.0 with nullable reference types enabled:

Trim the API Scope for SDK Generation

Full product specifications for vSphere describe hundreds of operations. Compiling a massive, monolithic client when your application only needs a fraction of those endpoints inflates build times and produces unnecessarily large binaries.

Use the –global-property apis flag to filter generation down to only the specific API groups you require:

Project Structure & Application Integration

Generating SDKs separately for both the REST API (/api) and the VI/JSON API (/sdk/vim25) produces two clean, independent C# projects. Keeping these bindings in separate packages prevents namespace and class collisions on overlapping entities (e.g., a “VM” or “Folder” has distinct structural definitions in each spec).

1. Referencing Projects in .csproj

In your consuming solution, reference both generated output directories as standard project dependencies:

2. Calling APIs from generated Client SDK

Since you have generated SDKs offerring API bindings you can interact with the APIs in your application code with strongly-typed C# classes and methods. Here is the sample code usage from the generated SDK.

Conclusion

Publishing complete OpenAPI specifications marks a pivotal shift in how enterprise private clouds are managed. Rather than treating VMware Cloud Foundation as a series of isolated control panels or limiting integration to pre-selected SDK languages, VCF becomes a fully programmable infrastructure platform.

By publishing OpenAPI contracts, VCF establishes an API-first paradigm where the specification itself is the single source of truth. Whether your developer teams build in C#, Go, Rust, TypeScript, or Swift, language choice is no longer a blocker. If a language compiler or HTTP stack exists, client code can be generated in seconds.

The end result is an agile, friction-free developer experience. Whether you’re managing multi-tenant clouds, automating internal platforms, or building custom orchestration tools, OpenAPI specifications ensure VMware Cloud Foundation can be extended, integrated, and consumed seamlessly from any programming language interface.

Resources

• OpenAPI Specifications
• Github Repository – Sample csharp project 
• Unlocking the Full Potential of Programmable Infrastructure with VMware Cloud Foundation 9.1 – New Features and Capabilities 

The post Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs appeared first on VMware Cloud Foundation (VCF) Blog.

The post Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs appeared first on VMware Blogs.

By combining VMware Tanzu Greenplum with VMware vSAN, organizations can bring their AI compute directly to their data storage layer for improved cost and latency.

The post A Unified Data Architecture For Sovereign Agentic AI With VMware Tanzu And VMware vSAN appeared first on Tanzu.

The post A Unified Data Architecture For Sovereign Agentic AI With VMware Tanzu And VMware vSAN appeared first on VMware Blogs.

Public clouds have upped the ante when it comes to what we expect from private cloud solutions. Our smartphones and fast access to public cloud resources have conditioned us to expect instant access to what we need when we need it.  Anything less feels antiquated and cumbersome, leaving your business users frustrated and disenchanted. To meet these heightened expectations, you need to get your VMware Cloud Foundation (VCF) up, running, and integrated into your ecosystem quickly to deliver a public cloud experience on-premises.

You may be thinking that your IT team possesses the necessary skills to get this done. In our experience, even if you have a tech savvy team most of them are already over-subscribed and don’t have the deep technical knowledge and experience to successfully accomplish cloud initiatives on their own. Often those who take the “build it yourself” route end up not succeeding, fall short of their objectives, or give up entirely because they realize it’s beyond their team’s skillset or other priorities take over.

The repercussions are unrealized value and a negative image with stakeholders due to unfulfilled expectations. IT leaders who are afforded a second chance or recognize there’s a better way to begin with often turn to VCF Professional Services.

So, avoid the missteps others have made and de-risk your cloud initiatives – go with the experts who live and breathe VCF all day, every day.  Our consultants aren’t just well-versed in your industry; they’ve got the hands-on experience to design, deliver, configure, and integrate VCF into your existing ecosystem for fast, reliable results.

Formula for success

Our VMware Pro Cloud Services can help you deliver a public cloud experience on-premises to meet business stakeholder expectations. We developed VMware Pro Cloud Services to provide consistent, predictable, and reliable solutions in the fastest time possible. They are based on VMware reference architectures combined with the best practices that we developed based on cloud engagements with a wide variety of customers spanning all industries. The result is a set of pre-packaged services aligned to common use cases.

Pre-packaged service offerings support common customer use cases

Our VMware Pro Cloud Services architect, deploy, configure, integrate, and operationalize VMware Cloud Foundation to deliver a secure private cloud that supports your IT and business objectives.

Infrastructure Modernization

Transforming your environment from day one requires a VMware Cloud Foundation (VCF) private cloud tailored directly to your operational goals—something an over-subscribed internal team rarely has the bandwidth to build alone. We don’t just deploy technology; we secure it right out of the gate by embedding the VMware vDefend Security Services Platform (SSP) and Avi Load Balancer WAF across all your workload domains. Whether you need zero-trust microsegmentation, automated virtual patching, or specialized builds that meet strict U.S. federal and sovereign cloud standards, we make sure your data stays fully locked down and compliant. 

When business demands surge, your infrastructure has to flex, but attempting to stretch your on-premises setup into the public cloud without expert guidance can lead to costly missteps. We enable seamless application mobility to handle dynamic demands like seasonal spikes.

Need to move applications to a new VCF 9.1 environment? We use low-risk iterative migration strategies for large-scale application moves.  We also upgrade existing VCF environments and converge legacy VMware vSphere® setups into VCF, streamlining management so your team can focus on innovation rather than maintenance. Our services to support these initiatives include:

• Build a Private Cloud
• Build a U.S. Federal Cloud
• Build a Sovereign Cloud
• Extend Your Data Center to the Cloud
• Modernize Your Virtualized Storage
• Migrate Workloads
• Upgrade

Application Modernization

Your developers expect instant access to modern tools, and when they don’t get it, business velocity grinds to a halt. Accelerating software delivery requires giving them immediate self-service capabilities without handing over the keys to operational safety. Our services bridge that exact gap, turning your VCF environment into an agile platform built for modern workloads. We build dynamic self-service catalogs that deliver fully configured cloud-native tools directly to your developers—moving your team far beyond simple virtual machine provisioning.

Building and migrating containerized architectures on your own often results in unexpected downtime and broken pipelines. We eliminate that friction by designing, deploying, and configuring VMware vSphere® Kubernetes Service (VKS) and migrating your existing clusters without missing a beat.

As enterprise AI demands grow, you don’t need to risk public cloud exposure or burn internal bandwidth trying to architect an AI framework from scratch. We pinpoint your infrastructure gaps, design an AI-ready framework, and seamlessly integrate private AI into your VCF private cloud so your machine learning workloads stay secure within your own boundary. Our services to support application modernization initiatives include:

• Enable Self-Service for App Teams
• Build Private AI
• Build and Migrate Kubernetes

Security Modernization

Cyber threats move far too fast for reactive defense strategies, and trying to piecemeal a security model together after a deployment leaves dangerous gaps. A truly modern security posture requires embedded protection at every single layer—from the hypervisor straight to the application layer. Our engineers design and deploy tailored cyber resilience and disaster recovery solutions built directly into your VCF platform so you aren’t left exposed.  By operationalizing VMware vDefend and Avi WAF, we establish a robust, multi-layered Zero-Trust architecture for you. We configure hypervisor-level distributed virtual patching to shield vulnerable operating systems, VMs, and Kubernetes workloads before threats ever touch your core. To keep breaches from spreading, we set up microsegmentation to block lateral movement and fine-tune AI-driven anomaly detection to give your operational team actionable intelligence instead of noise. Finally, we replace legacy load balancers with Avi Load Balancer to bring dynamic container ingress, cross-site resilience, and predictable performance to your applications. Our services for security modernization initiatives include:

• Implement Ransomware Protection and Recovery
• Implement Disaster Recovery
• Implement App and Private Cloud Security
• Implement and Migrate Load Balancing

In addition, our services define the roles and processes you need to effectively operate and manage your new environment.

Integrating VCF with your existing ecosystem is key

No VCF platform stands in isolation. It’s part of a larger ecosystem. That’s why our VMware Pro Cloud Services includes assistance for integrating with your existing processes and third-party solutions.

Get assistance with advanced operations

Once VCF is built and integrated into your environment, our Extended Expert Team Services are a great way to help advance your private cloud maturity with additional hands-on assistance. We can help you address challenges you may be experiencing, bridge gaps where additional expertise and best practices would be valuable and empower your team through knowledge transfers from VCF subject matter experts.

Frequently Asked Questions

Q: Are VMware Pro Cloud Services fixed-scope or customizable?

A: They provide a structured, fixed-scope delivery model to ensure fast execution, but offer some flexibility for custom scaling. Core platform builds include security hardening, an initial service catalog, network visibility, and integration with key infrastructure services like DNS, IPAM, and IAM.

Q: Frontier AI security threats are top of mind, do the VMware Pro Cloud Services include security features to help mitigate these risks?

A: Yes. Our services for building a private cloud handle end-to-end design and deployment with infrastructure security hardening. We fortify your private cloud with the VMware vDefense Security Services Platform and VMware Avi Load Balancer Web Application Firewall to protect applications and infrastructure from advanced cyber and ransomware threats. For existing VCF environments, we have individual VMware Pro Cloud Services to implement the same level of protection.

Q: Which services path should we take to get to VCF 9.1?

A: Your path to VCF 9.1 depends on your current state. To converge existing VMware vSphere environments or upgrade prior VCF builds, choose VMware Pro Cloud Upgrade Service.

For a new VCF 9.1 environment choose between VMware Pro Cloud Services: Build a Private Cloud or Build a Federal Cloud. No matter which service you choose, we can help you adopt operational processes for timely patching to keep your environment current and secure.

Q: How much faster is it to go with VCF Professional Services vs. doing the work in-house?

A:  Leveraging dedicated VCF specialists drastically reduces time-to-value and deployment risk. While internal teams know your general operations, our engineers deploy VCF daily across complex and highly regulated environments. Partnering with us prevents internal bandwidth bottlenecks and avoids costly trial-and-error missteps.

Q: What happens at the end of the engagement?

A: Every VMware Pro Cloud Services engagement includes a knowledge transfer for your team, best practices recommendations and any documentation that is developed as part of the service.

Q: Can we retain long-term expertise?

A: Yes. You can extend our assistance with our Extended Expert Team Services. These services pair nicely with our fixed-scope VMware Pro Cloud Services to provide long-term hands-on guidance, operational gap coverage, and ongoing SME mentorship.

To learn more about how VCF Professional Services can help your organization contact your Broadcom Account Director.

Editorial Note: the content of this blog has been updated following its original publication on October 2, 2025.

The post Get to VMware Cloud Foundation Faster with VMware Pro Cloud Services appeared first on VMware Cloud Foundation (VCF) Blog.

The post Get to VMware Cloud Foundation Faster with VMware Pro Cloud Services appeared first on VMware Blogs.

VMware Explore 2026 in Las Vegas

Day 4 Recap | September 3, 2026

Focused Learning. Immediate Impact.

This past week was jam-packed with awesome sessions, Hands-on Labs, and expert speakers who showcased our latest product releases around the future of VMware Private AI with VMware Cloud Foundation (VCF) 9.1. Attendees got to learn from industry pros, jump into lively discussions, and see how Broadcom’s solutions can tackle real-world business challenges.

Last Chance for Certifications

Tomorrow is your final opportunity to get certified this week. Even with a packed schedule, it’s worth carving out time for an exam, since it’s a direct way to validate your expertise and bring measurable career growth back to your team. That’s recognition, skills, accreditation, and tools to keep learning all rolled into one. Don’t miss it. The testing center will remain open until 12:45 PM tomorrow. 

Catch All the News of the Day in the Explore 2026 Media Kit

Looking Back at Explore 2026 in Las Vegas:

4,700+ attendees came to Las Vegas this year to immerse themselves into over 400 sessions designed to give deep insights and actionable strategies across four content tracks: Cloud Infrastructure, App Modernization, Security, and Innovation. But the sessions weren’t all…

Whether you were cultivating community in The Hub, discussing the latest innovations at one of the demo stations in the VMware by Broadcom Booth, or leveling up your resume with new certifications, we hope you found your perfect place to grow and connect this week.

VMware Explore 2026 in Las Vegas was a huge hit, and we couldn’t have done it without our amazing customers, partners, and peers. Thank you, to everyone who was a part of making it come to life. 

VMware Explore 2026 in Las Vegas 

That’s a wrap! 

A huge thank you to everyone who made this event possible. Your participation was key to its success. Get ready to meet us next year as we focus up our next wave of innovations.

Another year is in the books from Las Vegas and #VMwareExplore continues to deliver. Catch the news, replay, gallery, and get ready for Explore on Tour, coming to cities across the globe.
Share on X

Watch the Replay

Couldn’t make the plenary session? Catch the replay in the VMware Explore Video Library and get up to speed on all the latest news and announcements. Breakout session recordings will be available 24 hours after the session happens.

Missed one of this week’s daily recaps? You can get those here:

Day 1 Recap | Day 2 Recap | Day 3 Recap

We hope you will join us again next year in Las Vegas.

New Spring Dates. Brand-New Venue. Same Top-Tier Learning.

Save the Date and Pre-Register Today!

Join Us at VMware Explore

Las Vegas | Resorts World

May 3 – 6, 2027

Add to Calendar Now

Want to register your interest early? Pre-register today to lock in the lowest rate for Explore 2027. Complete the pre-registration form before September 30, 2026 to save an additional $100 off your Full Event Pass when registration officially goes live on January 12, 2027.

Looking Ahead: VMware Explore on Tour

Coming to cities across the globe, VMware Explore on Tour offers a highly curated selection of sessions and Hands-on Labs from Explore in Las Vegas. You’ll also gain access to key partners, regional leaders, subject matter experts, and local community members.

September 29 – 30 | Mumbai | LEARN MORE

October 1 – 2 | Singapore | LEARN MORE

October 13 – 14  | Frankfurt | LEARN MORE

October 20 – 21 | Tokyo | LEARN MORE

November 18 – 19 | London | LEARN MORE

December 8 | Washington, D.C. | Public Sector | SAVE THE DATE

March 3 – 4, 2027 | Sydney | SAVE THE DATE

Stay Connected

Get informed right here on the VMware Explore official blog for news, updates, and more. Join the Explore Insider newsletter and be part of our year-round community. Continue the conversation on LinkedIn using #VMwareExplore and after that, get connected with all of our social channels.

The post VMware Explore 2026 in Las Vegas | Day 4 Recap appeared first on VMware Explore Blog.

The post VMware Explore 2026 in Las Vegas | Day 4 Recap appeared first on VMware Blogs.

In today’s fast-paced digital economy, where AI-driven innovation demands unprecedented agility, IT leaders are tasked with more than just provisioning infrastructure; they are expected to deliver a frictionless, self-service platform that accelerates software delivery. For platform engineers, cloud architects, and IT executives, the goal is to bridge the gap between robust infrastructure and modern application deployment. VMware Cloud Foundation (VCF) Automation has consistently served as the critical enabler for a self-service private cloud. Today, we’re thrilled to announce the release of VCF 9.1.1, a pivotal update that brings advanced declarative application delivery to the forefront by introducing a native GitOps service to VCF Automation Org users, now available in Tech Preview.

By deeply integrating Argo CD into our platform, VCF 9.1.1 transforms how platform teams manage continuous delivery pipelines, eliminating operational friction and enabling a true modern cloud operating model.

The Challenge: Overcoming Scaling Bottlenecks in Application Delivery

For many organizations, the shift toward modern cloud-native architectures has exposed gaps in how deployment pipelines are managed. Prior to this feature, establishing GitOps continuous delivery pipelines lacked a standardized approach for onboarding, operating, and updating services without introducing administrative complexity.

Last July, we took an initial step to bridge this gap by releasing the Argo CD Operator for VCF. The Argo CD supervisor service deployed via vCenter (available since VCF 9.0.1) leverages the Argo CD Operator to seamlessly deploy and manage the lifecycle of Argo CD instances. The Argo CD supervisor service is fully supported for production use, and enterprise customers are leveraging it in their production environments today.

However, while this laid the necessary groundwork for bringing GitOps to the platform, scaling it to organizational end-users across a fleet still required platform engineering teams to perform manual, repetitive work to install, configure, and maintain the underlying Argo CD instances for their developer tenants.

This decentralized approach to tooling often resulted in a disjointed operational model at the organizational level. This created scaling bottlenecks, making it difficult for platform administrators to achieve a comprehensive view and efficiently manage the lifecycle of these services across the entire VCF fleet. As enterprises attempted to scale, platform engineering teams struggled with fragmented identity management and manual infrastructure mapping, lacking a unified control plane to seamlessly attach continuous deployment tools to varying vSphere Namespaces and VMware vSphere Kubernetes Service (VKS) clusters at scale.

Consequently, there was a missed opportunity to fully capitalize on cloud-native agility, leaving room to improve time-to-market, standardize security postures, and free highly skilled platform engineers from manual configuration tasks.

What’s New in VCF 9.1.1: A First-Class GitOps Experience (Tech Preview)

To solve these complex orchestration challenges, we are bringing GitOps directly into the core of VCF Automation private cloud services. Building upon the VCF services introduced in VCF 9.1, and the Argo CD service in vCenter, the VCF 9.1.1 release introduces the installation of the Argo CD-based VCF GitOps service as Tech Preview through the Service Management option in the VCF Automation Provider Management portal.

(Note: The core Argo CD supervisor service via vCenter remains fully supported for production; only this new VCF Automation Org user self-service integration is in Tech Preview.)

While in Tech Preview, this addition fundamentally shifts how organizations consume and manage continuous delivery frameworks:

• Self-Service Lifecycle Management: The VCF Automation organization portal enables organization users to self-service deployment of Argo CD instances into their vSphere Namespaces, rather than relying on decentralized manual processes.
• Seamless Integration and Authentication: The service delivers a highly integrated experience by automatically configuring VCF Automation OIDC authentication, which allows users to log in to the deployed Argo CD instance using VCF Automation credentials.
• Cross-Region Provider Management: The new VCF Service enables provider admins to deploy and manage Argo CD Operators across regions.
• Automated Target Attachment: The new GitOps service UI allows users to easily attach existing vSphere Namespaces and VKS clusters automatically configuring URLs in Argo CD’s managed cluster settings, eliminating manual infrastructure mapping and enabling a rapid start for managing workloads.
• Declarative Delivery at Scale: This integration enables a quick start with the Argo CD instance, enabling declarative GitOps continuous delivery to your workloads running on vSphere Namespaces and VKS clusters.
• Tailored Architectural Flexibility: It offers enterprise-grade architectural flexibility through granular, region-based scoping. Organizations deploy one Argo CD instance per hosting namespace. From there, teams can scope that specific instance to synchronize declarative resources across multiple vSphere Namespaces and VKS clusters residing within the same region. This allows project users to collaboratively manage continuous delivery targets across their environments without compromising organizational boundaries or security postures.

Driving Business Outcomes: The Value Proposition of Centralized GitOps

For IT executives, technology investments must deliver clear business outcomes and operational ROI. The introduction of this native integration is designed to align technical capabilities directly with overarching business goals.

The new VCF GitOps service drives significant operational ROI by centralizing GitOps lifecycle management, reducing the time to value required to bring modern application delivery services under unified operational control. By stripping away the manual overhead of fragmented tooling, platform engineering teams can redirect their focus toward innovation rather than maintenance.

Platform teams achieve faster and more secure deployment capabilities through the automated integration of VCF Automation OIDC and built-in, out-of-the-box targeting for vSphere Namespaces and VKS clusters. Ultimately, this native GitOps integration empowers organizations to scale declarative application delivery seamlessly, ensuring better compliance, streamlined access control, and a consistent cloud operating model across their entire private cloud environment.

By standardizing on a single, integrated GitOps control plane, organizations not only accelerate their digital transformation initiatives but also inherently strengthen their security and compliance frameworks across all underlying clusters and namespaces.

Take the Next Step

Ready to see how VCF 9.1.1 can revolutionize your continuous delivery pipelines and private cloud operations?

Read the release notes here. Discover how you can start configuring, deploying, and scaling your declarative applications with unprecedented ease today.

Learn More

• Blog: The Future of Cloud Infrastructure: Deep Dive into VMware Cloud Foundation Automation at Explore 2026
• Blog: Broadcom Named a Leader in the 2026 IDC MarketScape for Worldwide Private and Hybrid Cloud Management and Automation
• Blog: Accelerate, Streamline, and Control Your Self-Service Private Cloud with VMware Cloud Foundation 9.1
• eBook: Your Private Cloud is the New Public Cloud
• IDC Whitepaper: Self-Service Private Cloud as the Engine for In-House AI and Application Innovation

The post From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1 appeared first on VMware Cloud Foundation (VCF) Blog.

The post From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1 appeared first on VMware Blogs.