Blog Series: Metro – Break Stuff 5 – Failing a PowerStore
In the last episodes we failed an entire datacenter with and without a witness. This time we will be failing a PowerStore
Erik Zandboer runs Konversations around all things Kubernetes in a Cloud-Native world.
In the last episodes we failed an entire datacenter with and without a witness. This time we will be failing a PowerStore
In the previous episode we shut down an entire datacenter. AS we did not have a witness service present, the recovery wasn’t
In the previous episode of breaking stuff we powered off all hosts in one of the datacenters… Not really eventful as we
After we killed the datacenter interlink in the last episode, today we will be pulling the power from all hosts in one
Now that have are done describing the lab in the last episode, we are ready to go out and break stuff! Today
In this episode we will be leaving the History of Metro (which I covered in part1, part2 and part3). Let’s look at
Continuing the brief history of metro from part 2 of the series with some things that really help in building out a
In the previous “a brief history of metro” blog post (part 1) I discussed replication and metro and how they are “the
You may ask yourself: Why blog about a VMware environment? In parallel to “learn to crawl before you run” I feel that a lot of people working with kubernetes have a requirement (or at least THINK they have a requirement) for active/active metro storage solutions under their kubernetes setup. Building out a metro environment seems really easy, but as I run through this series you’ll discover that metro is anything-but-simple; there are many things to consider… Things that VMware figured out in their stretched cluster setup where kubernetes will struggle. I hope that people will start to see what metro is all about when I revisit the world of Virtual Machines.
In order to fully understand metro configurations, let’s first look at the history of things. The earliest ways of recovering from datacenter