Last week during a visit to VMware headquarters in Palo Alto, I had the opportunity to catch up with our engineering team who are responsible for developing storage solutions for Docker and Kubernetes running on vSphere. I have written about our Docker volume driver for vSphere and Kubernetes on vSphere already, but it’s been a while since I caught up with the team, and obviously more and more enhancements are being added all the time. I thought it might be useful to share the improvements with you here. There also seems to be some concerns raised about the availability of…
In a previous post related to multiple failures in a vSAN stretched cluster, we showed that if a failure caused the data components to be out of sync, the most recent copy of the data needs to recover before the object becomes accessible again. This is true even if there are a majority of objects available (e.g. old data copy and witness). This is to ensure that we do not recover the “STALE” copy of the data which might have out of date information. To briefly revisit the previous post, the accessibility of the object when there are multiple failures…
Last month we announced the release of a new vROps Management Pack specifically for vSAN. Previously the vSAN Management Pack was bundled with the MPSD – Management Pack for Storage Devices. I wrote about this when it entered beta, way back in 2015. Well, for those customers who are only interested in monitoring vSAN, and didn’t want all the other parts of the MPSD, the new vSAN Management Pack is now a stand-alone offering, so no MPSD required. This new vSAN Management Pack focuses on 3 main areas of vSAN: (1) Health and Availability, (2) Performance Analysis and (3) Capacity…
This is something very interesting which gained support with the release of vSAN 6.5. It will be of interest to those customers who boot their ESXi hosts from USB/SD devices, and also have vSAN configured. One long-standing restriction with this configuration was the inability to boot from USB/SD when the amount of memory in the host is over 512GB. This is because we could not guarantee that the memory dump would fit in the pre-sized core dump partition. Well, now we have the ability to resize the core dump partition, even when it resides on a USB/SD device. The guidance…
Many readers will be aware that John Nicholson and Pete Fletcha of the VMware Storage and Availability Tech Marketing team run a weekly podcast show called Virtually Speaking. This week I am back as a guest on their show, alongside Cody Hosterman of Pure Storage. We discuss a lot of the new core storage features in vSphere 6.5, which were detailed in a co-produced white paper that we recently created. You can read about how to get the white paper here. You can listen to the podcast through the player below. I hope you enjoy it.
Regular readers will know about vSphere Integrated Containers (VIC for short), as I have written a number of articles around my experiences with this new VMware product. Although announced with vSphere 6.5, VIC did not GA at the same time. However, VIC v0.8 is now generally available for vSphere 6.5.
Thanks to my friends over at VMUG Italia, my recorded presentation on Storage Challenges with Cloud Native Apps is now available. This was delivered at the VMUG UserCon event held in Milan, Italy, and which took place on November 15th. In this session I go through various container related projects that are underway at VMware (docker volume driver, vSphere Integrated Containers, Admiral, Harbor and Photon Platform), as well as how we are providing persistent storage for containers deployed on these products. Hope you enjoy it.