![]() ![]() Simplification of Virtualization Managementīy integrating these management functions into the VMkernel, the ESXi architecture became much simpler than ESX. As anyone who has ever architected anything can tell you, the simpler the better.įor example, instead of installing a 3rd party agent for hardware monitoring, VMware introduced the Common Information Model or CIM. ![]() This allowed hardware data to be easily seen in vCenter server, and common hardware management platforms to access it via vCenter.įor a great overview of the CIM, be sure to check out this blog on VMware’s site. It is from 2011, and wonderfully explains this huge shift in ESX vs ESXi architecture. Not only did this simplify management, but added to the stability and security of ESXi as a whole. We’ve talked a lot about the VMkernel, which is the brains of ESXi. I want to give you a simple overview so you can really begin to understand its capabilities. Like I said, the VMkernel is the brains of the operation. ![]() It handles things like resource scheduling, and resource management. The networking and storage stacks are also in the VMkernel, and the ESXi’s hosts device drivers are also handled by the VMkernel. What are VMkernel Ports?īack in the ESX days, we connected to our hosts with a special service console port. This was configured during the installation process of ESX, so we could connect to our hosts to continue to configure them and manage them. Starting with ESXi, we configured a VMkernel port for management. ![]()
0 Comments
Leave a Reply. |