Today we all heard/will hear (depending on timing of release 🙂 ) the official announcement of the VMware vSphere 7 product. One focus of todays announcement, that caught my eye, was the focus of being the center of the modern cloud/hybrid cloud. Following the the universal pillars of streamlined deployments, agile operations, to include improvements to lifecycle management, as well as an innovation acceleration through predictability.
First off let me state that its really nice to see that VMware has been holding themselves to their word, of staying in step with current global initiatives and movements on things like kubernetes and the ability to seamlessly manage them. I recall the difficulty I was having working vSphere integrated containers some years ago. Many of these features have come from direct feedback from customers and clients as well.
Here is a quick breakdown and take and take on what has been stated.
First up we see vSphere 7 with Kubernetes. Let me start by defining a few keywords, right from the Lincu foundation course I took on kubernetes. Containers are application-centric methods to deliver high-performing, scalable applications on any infrastructure of your choice. Containers are best suited to deliver microservices by providing portable, isolated virtual environments for applications to run without interference from other running applications.
As for microservices, they are lightweight applications written in various modern programming languages, with specific dependencies, libraries and environmental requirements. To ensure that an application has everything it needs to run successfully it is packaged together with its dependencies.
So now, kubernetes is “simply” a container orchestrator that is based on Google’s own orchestrator, Borg, that is used for an abundance of things internally to run their systems, like gmail, etc.
So what does all that mean for a VI admin/engineer? Well from my thoughts, VMware set out to seamlessly merge the systems and vi infrastructure and management with the emergence of the developers need and overall architecture of the container.
We also have some big improvements to life cycle management in vSphere 7. Upgrades have been made to make configuration management easier on the VI admin/engineer. vCenter configuration can be imported and exported via REST api, ability to move and drop config to other vcenters, version control and revert abilities on said configs.
The internal API explorer has had some improvements as well, to allow for faster ability to find the correct calls.
As far as lifecycle management here is the rest of what id picked up on. More to come on them over the next few weeks.
- vCenter Server Multi-Homing
- Have up to 4 nics per vcenter (as this is the current supported limit)
- Scalability Updates
- Standalone vcenter
- 2500 hosts per vcenter
- 30k powered on virtual machines
- Linked Mode vcenter
- 15k hosts total
- 150k powered on virtual machines
- Increase in vcenter to vcenter latency limit up to 150ms (up from 100ms)
- vCenter Server CLI Tools improvements
- Simple tooling commands for SSO domain consolidation
- unregister function
- domain repoint function
- Updates to the Content Library
- Quickly find template versions
- check-in templates
- check-out templates for edit
- revert versions of vm image
- New Versioning Tab for historical view of all edits
- versioning information is only available when a vm template is stored in the content library
Updates to Updates is, im sure for some, a welcome place of boosted features. Over the year there have been varying feelings towards updates and as any VI admin/eng can tell you, the more work done upfront pre-upgrade, the better.
Simplified certificate management is a welcome addition. internally we just went through upgrades, cert management and enablement of enhanced linked mode. Every bit of seamless counts.
This full number release of vSphere is looking to be loaded with hundreds of forward features. Cant wait for GA to put some time through it in the lab!