Skip to content

Posts tagged ‘vmware’


VMworld: Designing Network for Multisite vSphere (VSP3122)

Speakers: Sanjay Aiyagari (VMware), Simon Hamilton-Wilkes (F5)

Journey of IT Transformation: Accelerate and Amplify
– moving from server consolidation to being able to monitor and manage your applications
– and from there to hosting multiple instances of your application in the cloud provisioned independently for varied users

The Journey: Stage 1 – Infrastructure Focus
+ shared resource pools
+ elastic capacity
– no business continuity

The Journey: Stage 2 – Application Focus
+ zero-touch infrastructure
+ increased control and service assurance
– possible downtime
– idle infrastructures
– infrastructure dependencies

The Journey: Stage 3 – Business Focus
+ service definition
+ self-service
+ chargeback
– isolation between instances
– application configuration updates reflect infrastructure

Read moreRead more


VMworld: Engineering The Future (Keynote)

This morning’s keynote is purported to be more technical in flavor than yesterday’s presentation by VMware CEO Paul Maritz, who apparently wasn’t in his prime on Monday (per veteran EMC staff in attendance). Looking forward to what Steve’s going to offer…

Video interviews with VMware engineers: “It should just work and work well.”

Project Octopus: a collaboration platform that bridges somewhere between independent work and SharePoint with a service and simple centrality.


The entire presentation will be done with post-it notes and whiteboards (on screen), instead of PowerPoint.

We want to manage services not individual servers. We want the people to be thought of as a first tier individual who is accessing IT.

Devices. It’s about using all of our devices and having universal access. We have very high expectations. Devices + Universal Access + High Expectations = DUH!

Simplify the existing world: extract from silos, treat things in a common way with a common policy
– Desktop Service: not strapped to a Windows PC
– – VMware View 5
– App Catalog Service: one place
– – Project ThinApp Factory
– – – indexes a location for all MSI’s and exe’s
– – – may even spin up a VM to install the app and package it as a thin app
– – – assign access to apps by groups or users as auto-provisioned or user-activated
– – Horizon App Manager (ships today)
– – – next step is to add Windows apps to Horizon
– Data Service: inconvenience and big security challenge
– – how many of you are using DropBox today?
– – how many of you are /supposed to be/ using DropBox today?
– – Project Octopus:
– – – enterprise controls over external sharing, including expiration and domains
– – – works with both private cloud and public cloud

Manage: secure, user-focused
– Unified Service Broker
– Users, Application, Data Policy
– demonstration by Vittorio (VMware staff) of View thin & mobile

Connect: my app, my data, my colleagues
– Secure Universal Access
– View 5: access via thin client
– Horizon: provision mobile access (Horizon Mobile)
– – work life and home life separated but contained on one device
– – IT has control to wipe the work portion of a phone without affecting the personal side
– Project Octopus: “My Docs” present on Windows and mobile device
– Socialcast: new VMware acquisition for collaboration
– demonstration by Vittorio of iPad access and sharing files
– – Project App Blast: presents MS Excel to iPad
– – – presents apps via native HTML5 primitives
– – video calling from iPad to call center
– – Steve: “how a mobile user will interact with IT in a post-PC era”

Simplify – Manage – Connect

VMotion from the iPad using VCMA

# vSphere 5

# Accessible Innovation (including demonstration by Bruce)

Small Businesses:
– VMware Go: designed for small businesses getting started with virtualization
– – scans network for servers capable of running vSphere
– – Go reaches out to the machine, checks info, asks for password, and converts a Windows server to ESXi
– – can also do patch management and even help desk functionality
– vSphere Storage Appliance
– – enables organizations to deploy VMware without requiring a formal SAN
– – VSA runs as a virtual appliance on each host and presents local storage as shared
– – also writes data to primary and secondary locations for resilience

Larger Environments:
– Auto Deploy: enables ESXi provisioning via PXE

– biggest VM ever: 32 vCPU, 1000 GB RAM, 1 million IOPS
– guarantees: performance, availability, security

# Guarantees:

Intelligent Virtual Infrastructure
– set the policy, deploy the VM, and let IVI satisfy the contract in the private or public cloud

+ Performance Guarantees:
– “noisy neighbor”
– protect VMs from one another
– already been protecting CPU and memory for years
– now protecting Storage in vSphere 5
– – Pooling: take all the arrays in place and create pools and tiers
– – Placement: chooses storage based on policies and even within a tier
– – DRS: tracks behavior of VMs within the pool and migrates VMs within pools
– Storage I/O Control: minimums and shares for VMs
– Network I/O Control: same principles in networking — FINALLY!
– – at the hypervisor layer

– making networking fully virtualization aware
– Problem: Identifier = Location (IP addresses)
– – also shows up in the telephony space as phones moved from landlines to mobile
– – same goal in networking
– VXLAN: encapsulating L2 packets in L3 —HUGE!
– – create logical extensible overlay networks to span geography
– – applicable both inter-datacenter and intra-datacenter for DR, etc
– – vendors: Cisco, Intel, Emulex, Arista, Broadcom, IETF

+ Availability:
– one of the main reasons people have always chose to virtualize
– Datacenter outages:
– – SRM 5
– – – SRM has always abstracted the hardware
– – – SRM 5 introduces vSphere Replication for disparate SANs or less need for replication performance
– – – also introduces Automated Failback
– – – vCloud Partners to use 3rd party data centers as your replication site
– – – use cases: disaster avoidance, datacenter migration

+ Security:
– “nosy neighbor”
– critical in public cloud consideration
– vShield
– Defense In Depth
– – vShield Endpoint (VM)
– – vShield App (between VMs)
– – vShield Edge (virtual edge of network)

Guarantees: Performance – Availability – Security

Automate. Automate. Automate.
– typically an Alert –> Respond model
– an intelligent solution should Respond –> Alert
– Management Solution:
1) Monitor: AppSpeed
2) Correlate: event relations
3) Remediate: DRS, Storage & Network I/O Control, etc
– Sneak Peak (demonstration by Bruce):
– – vCenter Management
– – “Navigator” technology discovers applications running within servers —incredible!
– – no need to change apps within the servers to monitor them
– – discovers how the applications relate to each other
– – vCenter Operations Advanced —very interesting dashboards and metrics

It’s about the services and it’s about the people.


VCE: Virtual Computing Environment

Are you familiar with VCE? If not, add it to your IT acronym dictionary, but it’ll be something you hear more about in the future if virtualization, shared storage, converged networks, and/or server infrastructure are in your purview. VCE stands for “Virtual Computing Environment” and is a consortium of Cisco, EMC, VMware, and Intel (funny…if you take three of those initials, you get V-C-E). The goal and objective, which they seem to be realizing, is to deliver a “datacenter in a box” (or multiple boxes, if your environment is large), and in a lot of ways, I think they have something going…

The highlights for quick consumption:

  • a VCE Vblock is an encapsulated, manufactured product (SAN, servers, network fully assembled at the VCE factory)
  • a Vblock solution is designed to be sized to your environment based on profiling of 200,000+ virtual environments
  • one of the top VCE marketed advantages is a single support contact and services center for all components (no more finger pointing)
  • because a Vblock follows “recipes” for performance needs and profiles, upgrades also come/require fixed increments
  • Cisco UCS blade increments are in “packs” of four (4) blades; EMC disks come in five (5) RAID group “packs”
  • Vblock-0 is good for 300-800 VMs; Vblock-1 is for 800-3000 VMs; Vblock-2 supports 3000-6000 VMs
  • when crossing the VM threshold for a Vblock size, Vblocks can be aggregated

Those are the general facts. So what does all that mean for interested organizations? Is it a good fit for you? Here are some takeaways I drew from the points above as well as the rest of the briefing by our VCE, EMC, and Cisco reps… Read moreRead more


VMware & Link-State Tracking

If you’re running a VMware vSphere cluster on a two-tier (or greater) Cisco network, you might be in a situation like I was. You see, we built in redundancy when we planned our core and access switches, but the design had one significant flaw (see the simplified diagram to the right). Pretend all of those lines are redundant paths. Looks good so far, right? If CoreA goes down, ESX(i) can still send traffic up through AccessB to CoreB. The reverse applies if -B is down, and likewise for either of the Access- switches.

The catch comes for VMs on ESX(i) when one of the Core- switches goes down. ESX(i) balances VMs across the ports in the Virtual Machine port group(s). If a port goes down, it will smartly move the VM(s) to another port that is up. If an “upstream” hop like CoreB goes down, though, ESX(i) doesn’t know about that event, so it keeps its VMs in place, oblivious to the fact that the VMs on AccessB ports are as good as dead to the world. [Enter Link-State Tracking] Read moreRead more


Virtual Center 2.x incorrectly sizes disks during migration

VMs that were formerly RDMs (Raw Device Mappings) and which have had one or more disks grown via LUN migrations in EMC Navisphere (or similar functions in another vendor’s SAN tool) may fail to create the appropriately-sized disks on the target SAN during a storage migration. This is due to the fact that the RDM mapping file on the source SAN never updated to reflect the size of the previously grown LUN (via LUN migration). VMware Virtual Center uses that mapping file to create new VMDK files on the target.  Thus, if the mapping file is not updated to reflect the proper size, Virtual Center will create a smaller file on the target, possible resulting in loss of data or program integrity.

Example: server1 originally had a 30GB C:\ prior to a rebuild. When it was rebuilt, the same LUNs were used. However, due to a larger RAM allocation (i.e. 8GB instead of 4GB), the C:\ drive needed to be expanded. LUN migration in EMC Navisphere was used to accomplish this. However, the mapping file (the pointer .vmdk file) never changed to the new size. When the migration took place, Virtual Center only created a 30GB virtual disk on the target SAN. Windows booted thinking it had a 50GB disk (the expanded size). The result was that applications (i.e. SQL Server) and possibly other components failed to function after migration.

The solution is to delete and re-add the RDMs of any grown VMs before migration to ensure that the right size is used on the target.

Applies to: VMware ESX 3.x, Virtual Center 2.x