I had this question this week around what happens to VMs when a cluster is partitioned. Funny thing is that with questions like these it seems like everyone is thinking the same thing at the same time. I had the question on the same day from a customer running traditional storage and had a network failure across racks and from a customer running Virtual SAN who just wanted to know how this situation was handled. The question boils down to this, what happens to the VM in “Partition 1” when the VM is restarted in Partition 2?

The same can be asked for a traditional environment, only difference being that you wouldn’t see those “disk groups” in the bottom but a single datastore. In that case a VM can be restarted when a disk lock is lost… What happens to the VM in partition 1 that has lost access to its disk? Does the isolation response kick in? Well if you have vSphere 6.0 then potentially VMCP can help because if you have a single datastore and you’ve lost access to it (APD) then the APD response can be triggered. But if you don’t have vSphere 6.0 or don’t have VMCP configured, or if you have VSAN, what would happen? Well first of all, it is a partition scenario and not an isolation scenario. On both sides of the partition HA will have a master and hosts will be able to ping each other so there is absolutely no reason to invoke the “isolation response” as far as HA is concerned. The VM will be restarted in partition 2 and you will have it running in Partition 1, you will either need to kill it manually in Partition 1, or you will need to wait until the partition is lifted. When the partition is lifted the kernel will realize it no longer holds the lock (as it is lost it to another host) and it will kill the impacted VMs instantly.
This week I had the pleasure of talking to fellow dutchy
The conversation of course didn’t end there, lets get in to some more details. We discussed the use case first. PeaSoup is a hosting / cloud provider. Today they have two clusters running based on Virtual SAN. They have a management cluster which hosts all components needed for a vCloud Director environment and then they have a resource cluster. The great thing for PeaSoup was that they could start out with a relatively low investment in hardware and scale fast when new customers on-board or when existing customers require new hardware.
Harold pointed out that the only down side of this particular Fujitsu configuration was the fact that it only came with a disk controller that is limited to “RAID O” only, no passthrough. I asked him if they experienced any issues around that and he mentioned that they had 1 disk failure so far and that is resulted in having to reboot the server in order to recreate a RAID-0 set for that new disk. Not too big of a deal for PeaSoup, but of course if possible he would prefer to prevent this reboot from being needed. The disk controller by the way is based on the LSI 2208 chipset and it is one of things PeaSoup was very thorough about, making sure it was supported and that it had a high queue depth. The “HCL” came up multiple times during the conversation and Harold felt that although doing a lot of research up front and creating a scalable and repeatable architecture takes time, it also results in a very reliable environment with predictable performance. For a cloud provider reliability and user experience is literally your bread and butter, they couldn’t afford to “guess”. That was also one of the reasons they selected a VSAN Ready Node configuration as a foundation and tweaked where their environment and anticipated workload would require it.




First App I wanted to install was runkeeper, but for some strange reason it wouldn’t install… It took me a while to figure out that
Talking about notifications, this is of course is a big thing on the Pebble, email / twitter / calendar / whatsapp / sms and much more. I tried to keep it to those 5 though as I didn’t want to find myself constantly dismissing notifications. I use tweetbot and it comes in handy I can specify that I only want notifications for direct messages and mentions from people I follow. This restricts the number of notifications I get. This was one of the big reasons I bought a Pebble by the way. I used to be on my phone checking notifications all the time, and then immidiately responding to email/twitter/facebook etc. Considering the number of messages I receive it resulted on basically holding your phone in your hands for hours a day, driving my family nuts. I can’t respond to anything on my Pebble really, so that prevents me from responding to things which can wait. It is nice that after ~3 minutes notifications are automatically dismissed, would be even better if this was configurable though and I submitted that as a feature request to the Pebble team.
Some other apps which are worth mentioning are Evernote, Transport and TripAdvisor. Evernote is primarily for me to quickly dig up that note and read it. Don’t expect to use it a lot, but can be useful every now and then. TripAdvisor can be useful when looking for a place to eat in the area, couple of clicks and you know what can be found relatively closeby. Transport is probably the most useful of the three, as it will allow you to request an Uber ride from your Pebble. There are plenty of apps you can install / try on the Pebble appstore and I suspect that considering the massive number of Pebble watches sold this will increase steadily.