Archive for September, 2010

VMworld recap and “The Social Network” premier screening 10-1-10

September 30th, 2010

Quick (and awesome) invite for Minneapolis VMware User Group (VMUG) and virtualization community members from St. Croix Solutions – this event is being put on TOMORROW Friday October 1st:

I’d like to invite any and all members of the VMware User Group to join us on Friday for a breakfast presentation and a movie at the new Showplace Icon movie theater in St Louis Park. St Croix engineer, Bill Oyler, will recap his top 5 take-aways from VMworld and take some follow-up Q&A along with Jim Yanik from VMware. We’ll follow up the presentation with a complimentary premier screening of “The Social Network” movie. Concessions will be provided.

Schedule for Friday, October 1st:
—————————————————————
8:00-8:30 Registration & Breakfast
8:30-10:00 “Best of VMworld” presentation, Q&A
10:00-12:00 “The Social Network” Premier Screening

More details online here:
http://www.facebook.com/#!/event.php?eid=102243959840607

VMUG members can RSVP here:
http://www.stcroixsolutions.com/vmworld

Thanks,
Corey Donovan
Marketing Director
St Croix Solutions
cdonovan@stcroixsolutions.com
952-653-1731

Open in New Window

September 22nd, 2010

The VMware vSphere Client has a right-click menu option for most objects called Open in New Window

For instance, when right-clicking on a cluster object, the Open in New Window menu item appears:

SnagIt Capture

SnagIt Capture

SnagIt Capture

After choosing Open in New Window, a new vSphere Client window indeed appears.  Like many common tasks in the vSphere Client, this procedure has a shortcut key combination (CTRL + ALT + N).  Does this imply this is a commonly used feature? 

It’s not a commonly used feature by me.  To be honest, I didn’t know this feature existed until this week.  I was intrigued and played around with it for about 15 minutes.  First I tried to understand where this feature was presented.  I found it on most objects.  When I saw this, I looked for a way to exploit it.  The result was a rather anticlimactic failure.

This still left me wondering what the use case was for this feature.  There is one which comes to mind but I’m going to keep that to myself for now.  I’d like to hear from you.  Do you use this feature?  What are the use cases?  If you don’t use the feature, can you imagine a use case?  Open the vSphere Client and give it a try.  Be sure to try different infrastructure views.  There’s really no defined set of correct answers here, I’m looking for practical or creative ideas around the feature.

Respond in the comment section below.  The first responder with a relevant or interesting use case will be the winner of a VMware vSphere video training package from Train Signal.

Meet the Engineer: VMware vMotion

September 14th, 2010

I caught this VMware video announcement on Twitter but didn’t see a formal blog post or landing page to provide the proper introduction which it deserves, so I’ll go ahead here and do the cheeseful.  I have no shame in this.

vMotion is a historically significant technology in VMware’s portfolio of datacenter products and has become a staple of virtualized datacenter operations.  It paves a foundation which many other key VMware technologies leverage.  Dilpreet Bindra is the Senior Engineering Manager, VM Mobility Team at VMware (which encompases both vMotion and Storage vMotion).  

Dilpreet is the star of this video and he explains some of the barriers his group has conquered in vSphere 4.1 – these are awesome improvements!  Watch the video. You’re being treated to a sizable slice of VMware history.

The Future of VMware Lab Manager

September 12th, 2010

With the release of VMware vCloud Director 1.0 at VMworld 2010 San Franciso, what’s in store for VMware Lab Manager?  The future isn’t entirely clear for me.  I visualize two potential scenarios:

  1. Lab Manager development and product releases continue in parallel with VMware vCloud Director.  Although the two overlap in functionality in certain areas, they will co-exist on into the future in perfect harmony.
  2. VMware vCloud Director gains the features, popularity, pricing, and momentum needed to obsolete and sunset Lab Manager.

I’ve got no formal bit of information from VMware regarding the destiny of Lab Manager. In lieu of that, I’ve been keeping my ear to the rail trying to pick up clues from VMware body language.  Here are some of the items I’ve got in my notebook thus far:

Development Efforts:  First and foremost, what seems obvious to me is that VMware has all but stopped development of Lab Manager well beyond the past year.  Major functionality hasnt been introduced since the 3.x version.  Let’s take a look:

4.0 was released in July 2009 which provided compatibility with the recent launch of vSphere, that’s really it. I don’t count VMware’s half baked attempt at integrating with vDS which they market as DPM for Lab Manager (one problem, the service VMs prevent successful host maintenance mode and, in turn, prevent DPM from working; this bug has existed for over a year with no attempts at fixing).  To further add, the use of the Host Spanning network feature leverages the vDS and implies the requirement Enterprise Plus licensing for the hosts.  This drives up the sticker price of an already costly development solution by some accounts.

4.0.1 was released in December 2009, again to provide compatibility with vSphere 4.0 Update 1. VMware markets this release as introducing compatibility with Windows 7 and 2008 R2 (which in and of itself is not a lie), but anyone who knows the products realizes the key enabler was vSphere 4.0.1 and not Lab Manager 4.0.1 itself.

4.0.2 is released in July 2010 to provide compatibility with vSphere 4.1.  No new features to speak of other than what vSphere 4.1 brings to the table.

SnagIt Capture

Are you noticing the pattern?  Development efforts are being put forth merely to keep up compatibility with the vSphere releases.  Lab Manager documentation hasn’t been updated since the 4.0 release.  The 4.0.1 and 4.0.2 versions both point back to the 4.0 documentation.  Lab Manager documentation hasn’t been updated in over a year even considering two Lab Manager code releases since then.  Further evidence there has been no recent feature development in the Lab Manager product itself.

This evidence seems to make it clear that VMware is positioning Lab Manager for retirement.  The logical replacement is vCloud Director.  I haven’t heard of large scale developer layoffs in Palo Alto so a conclusion could be drawn here that most developer effort was pulled from Lab Manager and put on on vCloud Director 1.0 to get it out the door in Q3 2010.

Bug Fixes & Feature Requests:  This really ties into Development Efforts, but due to its weight, I thought it deserved a category of its own.  Lab Manager has acquired a significant following over the years by delivering on its promise of making software development more efficient and cost effective through automation.  Much like datacenter virtualization itself, a number of customers have become dependent on the technology.  As much as VMware has satisified these customers by maintaining Lab Manager compatibility with vSphere, at the same time customers are getting the short end of the stick.  Customers continue to pay their SnS fees but the value add of SnS is diminishing as VMware development efforts slowed down to a crawl.  At one time, SnS would net you new features, bug fixes, in addition to new versions of the software which provide compatibility with the host platforms.  Instead, the long list of customer feature requests (and great ideas I might add) sits dead in a VMware Communities forum thread like this.  The number of bugs fixed in the last two releases of Lab Manager I can almost count on two hands.  And what about squashing these bugs: this, this, and this?  Almost nothing has changed since Steven Kishi (I believe) exited the role of Director of Product Manager for VMware Lab Manager.

Again, this evidence seems to make it clear that VMware is sending Lab Manager off into the sunset.  Hello vCloud Director.

Marketing Efforts:  From my perspective, VMware hasn’t spent much time focusing on Lab Manager marketing.  By a show of customer or partner hands, who has seen a Lab Manager presentation from VMware in the last 6-12 months?  This ties strongly into the Development Efforts point made above.  Why market a product which seems to be well beyond its half life?  Consistent with the last thought above, marketing has noticably shifted almost entirely from Lab Manager to vCloud Director.

Chalk up another point for the theory which states Lab Manager will be consumed by vCloud Director.

Lack of Clear Communication:  About the only voice in my head (of which there are many) which reasons Lab Manager might be sticking around (other than a VMware announcement of a Lab Manager video tutorial series which has now gone stale) is the fact that VMware has not made it formally and publically clear that Lab Manager is being retired or replaced by vCloud Director.  Although I’m making a positive point here for the going concern of Lab Manager, I think there is ultimately an expiration date of Lab Manager in the not so distant future.  If you understand the basics of vCloud Director or if you have installed and configured it, you’ll notice similarities between it and Lab Manager.  But there is not 100% coverage of Lab Manager functionality and integration.  Until VMware can provide that seamless migration, they obviously aren’t going to pull the plug on Lab Manager.  Quite honestly, I think this is the most accurate depiction of where we’re sitting today.  VMware has a number of areas to address before vCloud Director can successfully replace Lab Manager.  Some are technical such as getting that 100% gap coverage between the two products from a features standpoint.  Some are going to be political/marketing based.  Which customers are ready to replace a tried and true solution with a version 1.0 product?  Some may be cost based.  Will VMware take a 1:1 trade in on Lab Manager for vCloud Director or will there be an uplift fee?  Will Enterprise Plus licensing be a requirement for future versions of vCloud Director?  vCloud Direct0r 1.0 requires Enterprise Plus licensing according to the VMware product’s ‘buy’ page.  Some will be a hybrid.  For instance, existing Lab Manager customers rely on a MS SQL (Express) database.  vCloud Director 1.0 is back ended with Oracle, a costly platform Lab Manager customers won’t necessarily have already in terms of infrastructure and staff.

SnagIt Capture

In summary, this point is an indicator that both Lab Manager and vCloud Director will exist in parallel, however, the signs can’t be ignored that Lab Manager is coasting on fumes.  Its ongoing presence and customer base will require support and future compatibility upgrades from VMware.  Maintaining support on two technologies for VMware is more expensive than to maintain just one.  A larger risk for VMware and customers may be that development efforts for vSphere have to slow down to allow Lab Manager to keep pace.  Even worse, new technology doesn’t see the light of day in vSphere because it cannot be made backward compatible with Lab Manager.  Unless we see a burst in development or marketing for Lab Manager, we may be just a short while away from a formal announcement from VMware stating the retirement of Lab Manager along with the migration plan for Lab Manager customers to become vCloud Director customers.

What are your thoughts?  I’d like to hear some others weigh in.  Please be sure to not disclose any information which would violate an NDA agreement.

Update 2/14/11: VMware has published a VMware vCenter Lab Manager Product Lifecycle FAQ for it’s current customers which fills in some blanks.  Particularly:

What is the future of the vCenter Lab Manager product line?

As customers continue to expand the use of virtualization both inside the datacenter and outside the firewall, we are focusing on delivering infrastructure solutions that can support these expanded scalability and security requirements. As a result, we have decided to discontinue additional major releases of vCenter Lab Manager. Lab Manager 4 will continue to be supported in line with our General Support Policy through May 1, 2013.

When is the current end-of-support date for vCenter Lab Manager 4?

For customers who are current on SnS, General Support has been extended to May 1, 2013.

Are vCenter Lab Manager customers eligible for offers to any new products?

To provide Lab Manager customers with the opportunity to leverage the scale and security of vCloud Director, customers who are active on SnS may exchange their existing licenses of Lab Manager to licenses of vCloud Director at no additional cost. This exchange program is entirely optional and may be exercised anytime during Lab Manager’s General Support period. This provides customers the freedom and flexibility to decide whether and when to implement a secure enterprise hybrid cloud.

The Primary License Administrator can file a Customer Service Request to request an exchange of licenses. For more information on the terms and conditions of the exchange, contact your VMware account manager.

Update 6/25/13: VMware notified its customers via email that support for Lab Manager 4.x has been extended:

June 2013

Dear VMware Valued Customers,VMware is pleased to announce a 1-year extension to the support for VMware vCenter Lab Manager 4.x. As reference, the original end of support date for this product was May 1, 2013. The new official end of support date will be May 21, 2014. This new end of support date aligns with VMware vSphere 4.x (noted in the support lifecycle matrix below as VMware ESX/ESXi 4.x and vCenter Server 4.x) end of support. This new date also allows the vCenter Lab Manager customer base more time to both use the 4.x product and evaluate options for moving beyond vCenter Lab Manager in the near future.

Additional Support Materials:

vCenter Server JVM Memory

September 6th, 2010

For those of you who have installed VMware vCenter Server 4.1, have you noticed anything new during the installation process?  A new screen was introduced at the end of the installation wizard for specifying the anticipated size of the virtual infrastructure which the respective vCenter Server would be managing.  There are three choices here: Small, Medium, & Large.  Sorry, no Supersize available yet.  If you require this option, I’m sure VMware wants to talk to you.

SnagIt Capture

The selection you make from the installation wizard not only defines the Maximum Memory Pool value for the Java Virtual Machine, but also the Initial Memory Pool value.  Following is a chart which takes a look at vCenter Server 4.0 & 4.1 JVM Memory Configuration comparisions:

vCenter/JVM Initial Memory Pool Max Memory Pool Thread Stack Size
4.0 128MB 1024MB 1024KB
4.1 Small (<100 hosts, default) 256MB 1024MB 1024KB
4.1 Medium (100-400 hosts) 256MB 2048MB 1024KB
4.1 Large (> 400 hosts) 512MB 4096MB 1024KB

As noted by the table above, in vCenter Server 4.0, the JVM Maximum Memory Pool was configured by default at 1024MB.  The vCenter Server 4.1 installation also defaults to 1024MB (Small <100 hosts) if left unchanged. One other comparison – pay attention to the difference in Initial Memory Pool. By default, vCenter 4.1 uses twice the amount of RAM out of the gate than previous versions.

Although the installation wizard JVM tuning component is new in 4.1, the ability to tune the JVM for vCenter is not.  The Configure Tomcat application has been available in previous versions of vCenter.  Some organizations with growing infrastructures may have been instructed by VMware support to tune the JVM values to overcome a vCenter issue having to do with scaling or some other issue.

SnagIt Capture

SnagIt Capture

Judging from the table, one can assume that the 1024MB value was appropriate for managing less than 100 hosts in vCenter 4.0.  As a point of reference, the Configuration Maximums document states that 300 hosts can be managed by vCenter 4.0.  This would imply that managing 100 hosts or more with vCenter 4.0 requires an adjustment to the out of box setting for the JVM Maximum Memory Pool (change from 1024MB to 2048MB). 

With vCenter 4.1, VMware has improved scaling in terms of the number of hosts a vCenter Server can manage.  The Configuration Maximums document specifies vCenter 4.1 can manage 400 hosts but the table above implies VMware may be preparing to support more than 400 hosts in the near future.  And that’s awesome because vCenter Server sprawl sucks. Period.

So have fun tuning the JVM but before you go, a few parting tips:

  • The Initial Memory Pool value defines the memory footprint (Commit Size) of the Tomcat process when the service is first started.  The Maximum Memory Pool defines the memory footprint which the Tomcat process is allowed to grow to.  Make sure you have sufficient RAM installed in your server to accommodate both of these values.
  • Setting the Initial Memory Pool to a value greater than the Maximum Memory Pool will prevent the Tomcat VJM from starting.  I thought I’d mention that before you spend too much time pulling your hair out.
  • If you would like to learn more about tuning Tomcat, vast resources exist on the internet.  This looks like a good place to start.

Unable To Retrieve Health Data

September 5th, 2010

SnagIt CaptureA number of people, including myself, have noticed that after upgrading to VMware vCenter 4.1, the vCenter Service Status shows red and displays the error message:

Unable to retrieve health data from https:///converter/health.xml

VMware has provided a workaround to this issue in KB 1025010.  The workaround involves installing the ldp.exe application binary from Microsoft, however, since I’m running vCenter Server on Windows Server 2008 R2, the binary is already in place by default and no download and installation was required. I’ve applied the workaround and after a service restart and a brief wait, the Service Status health went completely green, which is desired.

It’s worth nothing for posterity that step 3a is missing a small piece which I have provided in red below:

Double-click DC=virtualcenter,DC=vmware,DC=int, then double-click
-OU=Health,DC=virtualcenter,DC=vmware,DC=int
-OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int
-CN=.vpxd,CN=,OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware
-CN=com.vmware.converter,CN=,OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC

vCalendar 2.0 Released; 1.0 Free Electronic Download

September 2nd, 2010

Welcome back! I can’t believe a year has elapsed since vCalendar was first launched.  vCalendar 1.0 was a lot of fun to say the least. It certainly fulfilled the purpose I had originally intended for myself – to provide a virtualization tip a day on my desktop both at the office and at home.

Truth be told, I began working on the next version of vCalendar right after the first version was released back in August 2009. Like vSphere 4.0 and 4.1, vCalendar 2.0 boasts 150 new features. That’s right – 150 brand new virtualization facts, tips, best practices, configuration maximums, and historical events.  What’s in the new version?  It’s safe to say you’ll probably find some vSphere 4.1 tips, additional advanced concepts, some more key dates in virtualization history, among other new, improved, and valuable items.  I highly suggest you order the new vCalendar 2.0 to find out!

But wait… if there’s 150 new entries, what happened to last year’s entries?  I have to say, it was extremely difficult, but with just 365 days in the year, I had to find 150 of last year’s entries to remove in order to make way for the 150 new entries.  What’s unfortunate is that most of the archived entries are still relevant and therefore valuable. I struggled with the thought of letting the archived entries disappear forever. So here’s what I’ve done about that.  I’m releasing vCalendar 1.0 as a free download in a searchable Adobe PDF formatYou can download vCalendar 1.0 by clicking on this link. I thank you for your support and I hope you get some additional mileage out of it.  The remaining entries from last year which were carried forward were combined into the pool of new entries and all were randomized to provide a fresh new vCalendar.

Continue reading at the official vCalendar web page to learn more including the information on how to obtain vCalendar 2.0.