UPDATE VMware’s cloudy “capacity constraint” incident has stretched into a third week.
As we reported a lifetime ago on March 25, VMware advised it may not be possible to provision new software-defined data centres in one availability zone of the Sydney region of the VMware Cloud on AWS service.
At the time of writing, on April 9, the problem persists. The region still has an amber light, according to VMware’s status page. That dashboard has, for the last few days, offered only the following information about the issue: “The VMware Engineering team continues to work on adding new hosts and a fix on this issue.”
The issue isn’t disruptive. Current clients’ workloads run unimpaired. And constraints in a single Australian availability zone won’t inconvenience the majority of VMware customers.
Yet it’s now more than two weeks since VMware first started adding hosts, and Australia takes a four-day Easter break. Which means that unless some VMware engineers are willing to skip their seasonal chocolates, this one could stretch into a fourth week.
We've asked VMware to explain the delays and await a response.
In other VMware news, the company has released a new edition of NSX-T, the cut of its network virtualisation suite aimed at carrier and multi-cloud operations and which runs without requiring its vSphere compute virtualisation products.
NSX-T 3.0 adds a new “NSX Federation” that allows definition of network policies and automatically implementing them even as workloads move between on-prem and public cloud infrastructure. The new cut is also VMware’s preferred way to handle Kubernetes’ networking requirements if you adopt the new vSphere with K8s. ®
UPDATE: 01:15 GMT, April 11. VMware's advised customers that the incident is over with a terse: "This incident has been resolved. This is the final update."