Skip to main content

vSphere 5 components

vSphere 5 components and features;

Vmware ESXi : Well, this is the physical part of vSphere. The virtualization OS installed in  in physical servers and bastracts the physical resources of the server and distributes them across VMs.

VMware vCenter : It is the vsphere centralised management software. It is essential for configuring and managing the full potential of vSphere say HA, DRS etc

vSphere client: A client software that lets users connect remotely to Vmware ESXi and vCenter

vSphere web client: A web interface that allows users to connect remotely to vCenter client or ESXi

vSphere SDKs: Provides standard interfaces for VMware and third party solution to access VMware vSphere

VMFS : A high performance cluster file systems for ESXi virtual machnes

vSphere virtual SMP: Enables single virtual machine to use multiple physical processors simultaneously

vMotion: Enables migration of virtual machines from one datastore to another without service interruption*

vSphere HA: If the host ESXi fails, the affected virtual machines are restarted on other available servers with spare compacity

vSphere DRS: Distributed resource scheduler balances the computing capacity across vSphere clusters. DPM (Dynamic power 

Storage DRS: Allocates and balances storage capacity and I/O dynamically across colections of datastore. This includes management capabilities that minimise the risk of running out of space and risk of I/O bottlenecks that slow down the performance of virtual machines

vSphere FT: Provides continuous availability by protecting a virtual machine with a copy. When this feature is enabled for a virtual machine, a secondary copy of the original, or primary, virtual machine is created. All actions completed on the primary virtual machine are also applied to the secondary virtual machine. If the primary virtual machine becomes unavailable, the secondary machine becomes immediately active

vSphere Distributed switch: A virtual switch that can span multiple ESXi hosts, enabling significant reduction of on-going network maintenance activities and increasing network capacity. This increased efficiency enables virtual machines to maintain consistent network configuration as they migrate across multiple hosts.

Host profile: A feature that simplifies host configuration management through user-defined configuration policies. The host profile policies capture the blueprint of a known, validated host configuration and use this configuration to configure networking, storage, security, and other settings across multiple hosts. The host profile policies also monitor compliance to standard host configuration settings across the datacenter. Host profiles reduce the manual steps that are involved in configuring a host and can help maintain consistency and correctness across the datacenter.

Host profiles are also a component of vSphere Auto Deploy. The concept of an autodeployed host means that vCenter Server owns the entire host configuration and it is captured within a host profile.
 Certain policies require user input to provide host-specific values. To support Auto Deploy for host profiles, an answer file is created that contains the definitions for those policies.

*vMotion is not supported across datacenters


Popular posts from this blog

Cloud Security - Risk factors

Cloud security is a major consideration for enterprise wide cloud adoption, especially public cloud. This is part 1 of a serious of blog posts , where I am planning to pen down the different dimensions of Cloud security, starting with the risk factors of cloud adoption. The various attributes of security risks  involved in the process can be summed up as follows: ENISA* recommends the following  risk areas to be taken into account, while embarking on a cloud adoption journey

Windows server 2012: where is my start button??

If you have been using Windows Server OS for a while, the one thing that will strike you most when you login to a Windows server 2012 is that there is no start button!!.. What??..How am I going to manage it?? Microsoft feels that you really dont need a start button, since you can do almost everything from your server  manager or even remotely from your desktop. After all the initial configurations are done, you could also do away with the GUI and go back to server core option.(In server 2012, there is an option to add and remove GUI). So does that mean, you need to learn to live without a start button. Actually no, the start button is very much there .Lets start looking for it. Option 1: There is "charms" bar on the side of your deskop, where you will find a "start" option. You can use the "Windows +C" shortcut to pop out the charms bar Option 2: There is a hidden "start area"in  the bottom left corner of your desktop

Install nested KVM in VMware ESXi 5.1

In this blog, I will explain the steps required to run a nested KVM hypervisor on  Vmware ESXi. The installation of KVM is done on Ubuntu 13.10(64 bit). Note: It is assumed that you have already installed your Ubuntu 13.10 VM in ESXi, and hence we will not look into the Ubuntu installation part. 1) Upgrade VM Hardware version to 9. In my ESXi server, the default VM hardware version was 8. So I had to shutdown my VM and upgrade the Hardware version to 9 to get the KVM hypervisor working. You can right click the VM and select the Upgrade hardware option to do this. 2)In the ESXi host In /etc/vmware edit the 'config' file and add the following setting vhv.enable = "TRUE" 3)Edit the VM settings and go to VM settings > Options  > CPU/MMU Virtualization . Select the Intel EPT option 4) Go to Options->CPUID mask> Advanced-> Level 1, add the following CPU mask level ECX  ---- ---- ---- ---- ---- ---- --H- ---- 5) Open the vmx