Skip to main content

Posts

Showing posts with the label Virtualization

Whats new in vSphere 6.0

Here is a list of feature comparison of 5.5 and 6.0

Cloud Computing ( Public vs Private cloud)

Today we had a (friendly ;-) ) conversation with my colleagues which moved to an argument about the cloud computing. We were discussing (arguing) about the types of cloud services and its pro's / con's which lead me to write this blog post.  The Cloud Computing is now a trend and a hot discussion in every IT group.  The reason behind is that the cloud infrastructure can offer advantages over traditional datacenters in the areas of performance, scalability, and even security. There is a vast differences between private, public and hybrid clouds for enterprise. The type of cloud service is defined based on the types of data they store.  Sometimes these differences narrow, but each type of cloud has different levels of security and varying degrees of management. One may be more flexible or scalable, while another might be more affordable.  Here we’ll talk about private, public and hybrid cloud computing and some of their primary differences. What is a public cloud?  A pu

vVOLS (Virtual Volumes)

# Jagadeesh Devaraj #vVols I believe its a hot and trending topic now in internet. By now you guys might heard a lot about the vVols at VMworld 2014 or through various forums and the reason it is important to manage the end-to-end Infrastructure. The vVols takes cares of end-to-end Infra from compute of storage at the virtual machine (VM) and its VMDK ( vDisk) level. Virtualization meant VMs and vDisks are the unit of management at the compute layer. VMware® Virtual Volumes is meant to bridge the gap by extending the paradigm to storage specifically on VMware vSphere® deployments. What is vVols :  VVOLs is a provisioning feature for vSphere 6 that changes how virtual machines (VMs) are stored and managed. ( Information source : VMware.com) VVOLs is an out-of-band communication protocol between vSphere and storage. It allows VMware to associate VMs and vDisks with storage entities, and allows vSphere to offload some storage management functions, like provisioning of VM's

Cloud computing architecture

What is the use of defining cloud architecture? Cloud architecture is a software application that uses on demand services and access pool of resources from the cloud. Cloud architecture act as a platform on which the applications are built. It provides the complete computing infrastructure and provides the resources only when it is required. It is used to elastically scale up or down the resources according to the job that is being performed. How does cloud architecture overcome the difficulties faced by traditional architecture? Cloud architecture provide large pool of dynamic resources that can be accessed any time whenever there is a requirement, which is not being given by the traditional architecture. In traditional architecture it is not possible to dynamically associate a machine with the rising demand of infrastructure and the services. Cloud architecture provides scalable properties to meet the high demand of infrastructure and provide on-demand access to the user.

Introduction to Cloud Computing

What is Hypervisor in Cloud Computing and its types? The hypervisor is a virtual machine monitor (VMM) that manages resources for virtual machines. The name hypervisor is suggested as it is a supervisory tool for the virtual machines. There are mainly two types of hypervisors : • Type-1: the guest Vm runs directly over the host hardware, e.g Xen, Hyper-V, VmWare ESXi • Type-2: the guest Vm runs over hardware through a host OS, e.g Kvm, Oracle virtualbox Are Type-1 Hypervisors better in performance than Type-2 Hypervisors and Why? Yes the Type-1 Hypervisors are better in performance as compared to Type-2 hypervisors because Type-1 hypervisors does not run through a host OS, they utilize all resources directly from Host hardware. In cloud implementation Type-1 hypervisors are used rather than Type-2 because Cloud servers need to run multiple OS images and it should be noted that if OS images are run on host a OS as in case of Type-2, the resources will get wasted. What are

Hardware Virtualization-The Nuts and Bolts

Author:     Johan  De  Gelas Page 1 Introduction First dual-core in 2005, then quad-core in 2007: the multi-core snowball is rolling. The desktop market is still trying to find out how to wield all this power; meanwhile, the server market is eagerly awaiting the octal-cores in 2009. The difference is that the server market has a real killer application, hungry for all that CPU power: virtualization. While a lot has been written about the opportunities that virtualization brings (consolidation, hosting legacy applications, resource balancing, faster provisioning...), most publications about virtualization are rather vague about the "nuts and bolts". We talked to several hypervisor architects at VMWorld 2008. In this article, we'll delve a bit deeper as we look to understand the impact of virtualization on performance. Performance? Isn't that a non-issue? Modern virtualization solutions surely do not lose more than a few percent in performance, right? We'l

Virtual Server 2005: How To Configure the Virtual DHCP Server

Instead of configuring a virtual machine as a DHCP server, you can use the virtual DHCP server for your virtual network. To configure the virtual DHCP server: 1. Open the  Virtual Server Administration Website . 2. Under  Virtual Networks , select Configure  and then click the virtual network. 3. In  Virtual Network Properties , click  DHCP server . 4. Check the  Enabled  checkbox, then configure the necessary DHCP server options. 5. Click OK.

Remove a LUN from ESX host

ESXi 5.0 To avoid the rather complex set of instructions that you needed to follow in 4.1, VMware introduced new  detach  and  unmount operations to the vSphere UI & the CLI. As per  KB 2004605 , to avoid an APD condition in 5.0, all you need to do now is to  detach  the device from the ESX. This will automatically unmount the VMFS volume first. If there are objects still using the datastore, you will be informed. You no longer have to mess about creating and deleting rules in the PSA to do this safely. The steps now are: Unregister all objects from the datastore including VMs and Templates Ensure that no 3rd party tools are accessing the datastore Ensure that no vSphere features, such as Storage I/O Control or Storage DRS, are using the device Detach the device from the ESX host; this will also initiate an unmount operation Physically unpresent the LUN from the ESX host using the appropriate array tools Rescan the SAN