In this post we will focus on 3 key product enhancements around vSAN.
Simpler Lifecycle Management
Increase reliability and reduce number of tools
In vSphere 6.x hosts are individually managed with VMware Update Manager (VUM), but vSAN is a cluster based solution which is not ideal and can create inconsistencies.
vSphere 7 is introducing an entirely new solution at the cluster level to unify software and firmware management.
- This new approach is focused around this desired-state model for all lifecycle operations
- Monitors compliance “drift” in real time
- Provides then the ability to remediate back to the desired state
- Built to manage server stack in cluster
- Modular framework supports vendor firmware plugins which allows their own firmware and respective drivers to be integrated with an image that is applied to hosts.
Native File Services
Now we talking! vSAN 7 introduces a fully integrated file service that is built right into the Hypervisor and managed through vCenter Server.
- Provision vSAN cluster capacity for file shares Supports NFS v4.1 & v3
- Supports quotas for file shares
- Suited for Cloud Native & traditional workloads on vSAN
- I don’t think this capability is looking to replace large scale filers, but more looking to solve the specific use cases within that particular cluster.
- Works with common vSAN/vSphere features
There are many use cases for both traditional VMs as well for cloud native applications. Let’s look at the latter.
Extension and integration K8s running on vSphere and vSAN
- Native files services will offer file-based persistent storage
- vSAN also provides persistent block storage through SPBM for vSAN and vVols which is associated to a Storage class in Kubernetes
- Persistent volume encryption and snapshot support
- Volume resizing support
- Support for some different tooling options