Tag Archives: VMWare

VMware – Vendor Strengths and Cautions – Gartner

http://www.gartner.com/technology/reprints.do?id=1-2JFZ1KP&ct=150715&st=sb

VMware

VMware has maintained its functionality lead, introducing vSphere 5.5 in September 2013 (it released vSphere 6.0 after the cutoff for this analysis). VMware continues to have dominant market share, and customers remain very satisfied with product capabilities and vendor support. However, concern over price and vendor lock-in remains. Client inquiries have been significantly increasing about comparisons between VMware and Hyper-V, specifically. While few large enterprises are switching, some smaller enterprises that are not far along in their virtualization deployment are switching (often from VMware to Hyper-V, but sometimes from Hyper-V to VMware), and some larger customers are deploying alternatives to VMware in separate data centers or in branch/store locations.

VMware is still enjoying good growth, but growth is harder due to both increasing market saturation and competitive pricing pressure. An emerging concern is the rapid growth of IaaS cloud providers, especially Amazon Web Services (based on Xen), used mainly for new workloads that are designed for cloud computing. While VMware has a dominant share for existing enterprise workloads, its share of the newer, cloud workloads is much smaller — a major inhibitor to growth. While the overall installed base of VMs tripled between 2011 and 2014, the percentage of VMs in cloud computing providers grew from 3% to 20% in the same time. VMware launched its own cloud service in August 2013 (now called vCloud Air), but it is still a very small player compared with providers like Amazon.

With respect to the growing midmarket business, in which high-end management and automation features are less critical, VMware has retained a strong market share. (Gartner surveys consistently show that about half of midmarket companies, those with 100 to 1,000 employees, tend to use VMware.) However, as Microsoft gains marketing momentum, VMware will need to continue to offer low-price packages to remain competitive in this market. As VMware promotes virtualization for more mission-critical workloads, it continues to face an Oracle VM solution, whereby concern over platform certification will drive a small number of VMware users to Oracle VM. While Windows-based workloads have become heavily virtualized, there is still quite a bit of opportunity for Linux-based workloads. However, OpenStack, Red Hat and containers are growing trends driving Linux virtualization.

A key for VMware’s growth will be to expand outside of traditional applications, attract and enable developers, and succeed as a cloud provider (and/or as an enabler to cloud providers).

Strengths

  • VMware has a broad virtualization strategy from the data center to the cloud.
  • VMware is a virtualization technology leader, with significant investments and innovation.
  • VMware receives high customer satisfaction from a large installed base.

Cautions

  • The cost of VMware offerings tends to be high.
  • VMware has a large number of third-party providers that offer VMware functionality, but the overall market share of VMware functionality in third-party cloud providers is small.
  • VMware has a low penetration for newer, “cloud-native” applications.
Advertisements
Tagged ,

vSphere 5.1 vMotion Deepdive.

A big change in vSphere 5.1 is the vMotion capabilities, where there is no need for shared storage between ESX hosts for Virtual Machines to migrate to and from. In previous versions of vSphere there was a requirement of shared storage.

See this in depth article on vSphere 5.1 vMotion to get a better understanding.  http://frankdenneman.nl/vmotion/vsphere-5-1-vmotion-deepdive/

 

Tagged , ,

vSphere 5.0 Hardening Guide – Official Release

This is the official release of the vSphere 5.0 Security Hardening Guide, v1.0.  The format of this guide has changed from previous versions. The guide is being released as a Excel spreadsheet only.  The guideline metadata from earlier guides has been greatly expanded and standardized.  CLI commands for assessment and remediation of the guidelines is included for the vCLI, ESXi Shell, and PowerCLI.  For additional information, please see the Intro tab of the spreadsheet.

http://communities.vmware.com/servlet/JiveServlet/downloadBody/19605-102-1-26036/HardeningGuide-vSphere50-v1.0.xlsx

HardeningGuide-vSphere50-v1.0

 

 

Tagged , ,

VMware vSphere and Cisco UCS vNIC Configuration

Configuration of vNIC / Loadbalancing / Failover / QOS

Below is a typical configuration of vSphere ESX vNIC assignment correlating to the UCS Fabric Interconnect.

Management Port Group vMotion Port Group Fault Tolerance Port Group Production Virtual Machine Port Group Storage HBA’s
UCS   Fabric A 10GB vNic 0 (Active) vNic 2 (Standby) vNic 4 (Active) vNic 6 (Active) HBA 1 (Active)
UCS   Fabric B 10GB vNic 1 (Standby) vNic 3 (Active) vNic 5 (Standby) vNic 7 (Active) HBA 2 (Active)
UCS   QOS Priority Bronze Silver Gold Best Effort FC
UCS   QOS Weight % 0 % 11 % 11 % 33% 34 %
Min   / Maxbandwidth   using   both fabrics  Min = 1GBMax = 1GB Min = 1GBMax = 10 GBMax is limited to QOS Priority  Min = 1GBMax = 10 GBMax is limited to QOS Priority  Min = 6GBMax  = 10 GBMax is limited to QOS Priority  Min = 8GBMax = 10GBMax is limited to QOS Priority 
VMware   Load Balancing Route based on originating virtual port Id N/A N/A dVS = Route based on physical NIC loadvSS = Route based on originating virtual port Id

 

Active Active(round Robin)
VMware   Failover Policy Active/Standby Active/Standby Active/Standby Active / Active N/A

1)      Note, that route based on IP hash is not supported by UCS when used with either a VMware Standard vSwitch or Distributed vSwitch. You can use route based on IP hash when used with a nexus 1000v.

2)      With the above configuration the production vNics are both active and separated between two fabrics. The uplinks from the fabrics should then be configured as a Multi Chassis Ether-channel to the core switches.

3)      By applying UCS QOS policies, there is guaranteed minimum bandwidth assigned per vNic, and also has the ability to burst higher if is ever needed, but will not affect other vNic’s that have a higher priority.

4)      If a dVS (VMware distributed virtual)  switch is used, then the “route based on physical NIC load “  load balancing algorithm should be used to load balance active/active uplinks to the fabric interconnects.

Tagged , , , ,

Virtualisation and Private clouds.. what is the difference?

The difference between virtualisation and private cloud is that one provides the means to achieve the other – but it is not quite so simple

An article by Alan Stevens on the register explains further:

From virtualisation to private cloud http://reg.cx/1PBM

Tagged , ,

VMware VSphere 5.0

VSphere 5.0 is expected to be released in August 2011. Beta release is already available to partners.

Listed below are the new features that will be included in VMware VSphere 5.0

Client Side

  • New Web based Client. No need to install a local client.

     

Virtual Machine

  • Support for up to 32 vCPU’s per Virtual Machine, previously was 8 vCPU’s.
  • 1 TB RAM per VM, previously was 255GB
  • 64TB Virtual Disk/RDM, previously was 2TB

Cluster Features

  • Storage DRS – Storage Pods
  • Network DRS
  • VASA – Vstorage API Storage Awareness – (monitors IOPS)
  • Application Aware HA (High Availability)

Other Features

  • Host based Replication – SRM 5.0
  • Network I/O Control
  • Storage I/O Control for NFS storage
  • 3D Graphics Support
  • VMFS – READ CACHE ( use RAM as disk)
  • FIPS 140 Compliance

Conclusion

Loads of extra feature enhancement from VSphere 4. Exciting times ahead.

Tagged ,