Google Cloud's VMware service loses resilience due to a dud update
As VMware itself warns of critical flaw in its load balancer
Google Cloud has admitted it made a configuration change that means some customers of its VMware Engine (GCVE) can’t use stretched cluster.
A G-Cloud incident report time-stamped 13:24 PDT on July 14 (21:24 UTC) reports some customers “are experiencing zonal outages impacting network connectivity across multiple regions” and that the trouble started at 10:00 PDT.
Google first attributed the problem to “an underlying network connectivity issue affecting the infrastructure that links the zones within a stretch cluster,” and warned “This disruption is causing synchronization issues between the affected zones.”
Storage and compute services weren’t impacted, and VMs kept running. Users just couldn’t reach their virtual servers.
That’s bad because the whole point of stretched clusters is to enhance resilience by creating a virtual pool of resources that spans two physical sites, while keeping the two rigs in synch to...
Copyright of this story solely belongs to theregister.com. To see the full text click HERE
