Archive for the ‘New Products’ Category

h1

Short-Take: vSphere vCloud Suite – Cheat Sheet

August 27, 2012

VMworld 2012 Announcements

VMware announces a new product package based on vCloud Director and vSphere Enterprise Plus called vCloud Suite. Existing users of vSphere Enterprise Plus (with valid SnS as of 8/27/2012) – including Academic and Federal users – may qualify for a “free” upgrade (actually $1/CPU) to “Standard” edition of vCloud Suite. Likewise, users with valid SnS and vSphere Enterprise (not Plus) qualify for a reduced cost upgrade to vCloud Suite Standard at $682/CPU.

Qualifying users have until December 15, 2012 to complete the transaction. Upgrades to other editions of vCloud Suite from Enterprise and Enterprise Plus are available as well – at additional cost per CPU.

vCloud Suite Cheat Sheet

Summary of new vCloud Suite offering and tiers (including links):

vCloud Suite
Standard Advanced Enterprise
Virtualization VMware vSphere Enterprise Plus Edition * * *
Cloud Infrastructure vCloud Director and vCloud Connector * * *
Standard vCloud Networking and Security * * *
Advanced vCloud Networking and Security * *
vCenter Site Recovery Manager Enterprise *
Operations Management vCenter Operations Management Suite vCOps Advanced vCOps Enterprise
VMware vCenter Chargeback Manager™ *
VMware vCenter Configuration Manager™ *
VMware vCenter Infrastructure Navigator™ *
vFabric Application Director *
Licensing Per CPU, Enterprise Plus basis $4,995.00 $7,495.00 $11,495.00
Support Basic: Per CPU, Per Year $1,049.00 $1,574.00 $2,414.00
Production: Per CPU, Per Year $1,249.00 $1,874.00 $2,874.00

Per-VM Pricing All But Gone

The introduction of vCloud Suite side-steps the vCloud Director per-VM licensing model and allows private cloud to scale based on the more predictable per-CPU infrastructure metric. Public cloud service providers will still be interested in per-VM foot prints and billing structures, but at least private cloud can be unshackled from the confines of per-VM vCD and vRAM issues; which segways nicely into the next tidbit…

In Other News…

VMware effectively kills vRAM by including “unlimited” vRAM entitlements in all editions of vSphere.

SMB’s may be pleased to note that VMware also now includes the vSphere Storate Appliance with all acceleration kits except vSphere Essentials at no additional cost (versus vSphere 5.0 kits). This is especially good for ROBO operations using Essentials Plus. The standalone cost for vSphere Storage Appliance is now $3,495.

h1

Short Take: VMware View Client for Android, ICS Update

May 17, 2012

An updated VMware View Client for Android devices hit a the street today sporting a couple of enhancements for Google’s Android OS running the relatively new Ice Cream Sandwich (ICS) version; other improvements are for View 5.1 deployments only.

Here’s a list of the new features in the update available now on Google Play:

- Support for ICS
- Mouse support with hover, right click and scroll wheel (ICS)
- Updated look and feel and improvements for smaller screens
- New Settings dialog includes security mode settings
- Up to 2x better video playback performance
- Optimized for View 5.1
- RADIUS two factor authentication with View 5.1
- Save password option (administrator approval required) with View 5.1
- French, German, Spanish keyboard support with View 5.1

The update is a 5.32MB download, and is available free of charge.

h1

In-the-Lab: NexentaStor and VMware Tools, You Need to Tweak It…

February 24, 2012

While working on an article on complex VSA’s (i.e. a virtual storage appliance with PCIe pass-through SAS controllers) an old issue came back up again: NexentaStor virtual machines still have a problem installing VMware Tools since it branched from Open Solaris and began using Illumos. While this isn’t totally Nexenta’s fault – there is no “Nexenta” OS type in VMware to choose from – it would be nice if a dummy package was present to allow a smooth installation of VMware Tools; this is even the case with the latest NexentaStor release: 3.1.2.

I could not find where I had documented the fix in SOLORI’s blog, so here it is… Note, the NexentaStor VM is configured as an Oracle Solaris 11 (64-bit) virtual machine for the purpose of vCenter/ESXi. This establishes the VM’s relationship to a specific VMware Tools load. Installation of VMware Tools in NexentaStor is covered in detail in an earlier blog entry.

VMware Tools bombs-out at SUNWuiu8 package failure. Illumos-based NexentaStor has no such package.

Instead, we need to modify the vmware-config-tools.pl script directly to compensate for the loss of the SUNWuiu8 package that is explicitly required in the installation script.

Commenting out the SUNWuiu8 related section allows the tools to install with no harm to the system or functionality.

Note the full “if” stanza for where the VMware Tools installer checks for ‘tools-for-solaris’ must be commented out. Since the SUNWuiu8 package does not exist – and more importantly is not needed for Illumos/Nexenta – removing a reference to it is a good thing. Now the installation can proceed as normal.

After the changes, installation completes as normal.

That’s all there is to getting the “Oracle Solaris” version of VMware Tools to work in newer NexentaStor virtual machines – now back to really fast VSA’s with JBOD-attached storage…

SOLORI’s Note: There is currently a long-standing bug that affects NexentaStor 3.1.x running as a virtual machine. Currently there is no known workaround to keep NexentaStor from running up a 50% cpu utilization from ESXi’s perspective. Inside the NexentaStor VM we see very little CPU utilization, but from the performance tab, we see 50% utilization on every configured vCPU allocated to the VM. Nexenta is reportedly looking into the cause of the problem.

I looked through this and there is nothing that stands out other that a huge number of interrupts while idle. I am not sure where those interrupts are coming from. I see something occasionally called volume-check and nmdtrace which could be causing the interrupts.

- Nexenta Support

A bug report was reportedly filed a couple of days ago to investigate the issue further.

h1

Quick-Take: VMworld 2011, Thoughts on the Airplane

August 28, 2011

On the way to VMworld this morning this morning I started-out by listening to @Scott_lowe, @mike_laverick and @duncanyp about stretched clusters and some esoteric storage considerations. Then i was off reading @sakacc blogging about his take on stretch clusters and the black hole of node failure when I stumbled on a retweet @bgracely via @andreliebovici about the spectre of change in our industry. Suddenly these things seemed very well related within the context of my destination: VMworld 2011.

Back about a month ago when vSphere 5 was announced the buzz about the “upgrade” was consumed by discussions about licensing and vRAM. Naturally, this was not the focus VMware was hoping for, especially considering how much of a step forward vSphere 5 is over VS4. Rather, VMware – by all deserved rights – wanted to hear “excited” conversations about how VS5 was closing the gap on vCloud architecture problems and pain-points.

Personally, I managed to keep the vRAM licensing issue out of SOLORI’s blog for two reasons: 1) the initial vRAM targets were so off that VMware had to make a change, and 2) significant avenues for the discussion were available elsewhere. That does not mean I wasn’t outspoken about my thoughts on vRAM – made obvious by contributions to some community discussions on the topic – or VMware’s reasoning for moving to vRAM. Suffice to say VMware did “the right thing” – as I had confidence they would – and the current vRAM targets capture 100% of my clients without additional licenses.

I hinted that VS5 answers a lot of the hanging questions from VS4 in terms of facilitating how cloud confederations are architected, but the question is: in the distraction, did VS5′s “goodness” get lost in the scuffle? If so, can they get back the mind share they may have lost to Chicken Little reactionaries?

First, if VMware’s lost ground to anyone, it’s VMware. The vast majority of cool-headed admins I talked to were either not affected by vRAM or were willing to take a wait-and-see outlook on vSphere 5 with continued use of vSphere 4.1. Some did evaluate Hyper-V’s “readiness” but most didn’t blink. By comparison, vSphere 4.1 still had more to offer private cloud than anything else.

Secondly, vSphere 5 “goodness” did get lost in the scuffle, and that’s okay! It may be somewhat counter intuitive but I believe VMware will actually come out well ahead of their “would be” position in the market, and it is precisely because of these things, not just in spite of them. Here’s my reasoning:

1) In the way the vSphere 5 launch announcement and vRAM licensing debacle unfolded, lot of the “hot air” about vRAM was vented along the way. Subsequently, VMware gained some service cred by actually listening to their client base and making a significant change to their platform pricing model. VMware got more bang-for-their-buck out of that move as the effect on stock price may never be known here, given the timing of the S&P ratings splash, but I would have expected to see a slight hit. Fortunately, 20-30% sector slides trump vRAM, and only Microsoft is talking about vRAM now (that is until they adopt something similar.)

On that topic, anytime you can get your competitor talking about your product instead of theirs, it usually turns out to be a good thing. Even in this case, where the topic has nothing to do with the needs of most businesses, negative marketing against vRAM will ultimately do more to establish VMware as an innovator than an “already too expensive alternative to XYZ.”

2) SOLORI’s law of conservation of marketing momentum: goodness preserved, not destroyed. VMworld 2011 turns out to be perfectly timed to generate excitement in all of the “goodness” that vSphere 5 has to offer. More importantly, it can now do so with increased vigor and without a lot of energy siphoned-off discussing vRAM, utilization models and what have you: been there done that, on to the meat and away with the garnish.

3) Again it’s odd timing, but the market slide has more folks looking at cloud than ever before. Confidence in cloud offerings has been a deterrent for private cloud users, partly because of the “no clear choices” scenario and partly because concerns about data migration in and around the public cloud. Instability and weak growth in the world economy have people reevaluating CAPEX-heavy initiatives as well as priorities. The bar for cloud offerings has never been lower.

In vSphere 5, VMware hints at the ability for more cloud providers to be transparent to the subscriber: if they adopt vSphere. Ultimately, this will facilitate vendor agnosticism much like the early days of the Internet. Back then, operators discovered that common protocols allowed for dial-up vendors to share resources in a reciprocal and transparent manner. This allowed the resources of provider A to be utilized by a subscriber of provider B: the end user was completely unaware of the difference. For those that don’t have strict requirements on where their data “lives” and/or are more interested in adherence to availability and SLA requirements, this can actually induce a broader market instead of a narrower one.

If you’ve looked past vRAM, you may have noticed for yourself that vSphere has more to deliver cloud offerings than ever before. VMware will try to convince you that whether cloud bursting, migrating to cloud or expanding hybrid cloud options, having a common underlying architecture promotes better flexibility and reduces overall cost and complexity. They want you to conclude that vSphere 5 is the basis for that architecture. Many will come away from Las Vegas – having seen it – believing it too.

So, as I – and an estimated 20K+ other virtualization junkies – head off to Las Vegas for a week of geek overload, parties and social networking, my thoughts turn to @duncanyp‘s 140+ improvements, enhancements and advances waiting back home in my vSphere 5 lab. Last week he challenged his “followers” to be the first to post examples of all of them; with the myriad of hands-on labs and expert sessions just over the horizon, I hope to do it one better and actually experience them first hand.

These things all add up to a win-win for VMware and a strong showing for VMworld. It’s going to be an exciting and – tip of the hat to @bgracely - industry changing week! Now off to the fray…

References:

See Mike Laverick’s chinwag podcasts

See Chad’s Sakacc’s VirtualGeek blog on stretched cluster issues to overcome

(excuse typos today, wordpress iPad…)

h1

Short-Take: Nexenta 3.1 Adds VAAI Support, Auto-Sync Resume

August 3, 2011

Nexneta Systems Inc released version 3.1 of its open storage software yesterday with a couple of VMware vSphere-specific feature enhancements. These enhancements are specifically targets at VMware’s vStorage API for Array Integration (VAAI) which promises to accelerate certain “costly” storage operations by pushing their implementation to the storage array instead of the ESX host.

From NexentaStor 3.1 Release Notes, the primitives implemented in 3.1 that contribute to VAAI support include:

  • SCSI Write Same: Supported in vSphere 4.1 and later
    Example. Accelerates zero block writes when creating new virtual disks.
  • SCSI ATS (Atomic Test & Set): Supported in vSphere 4.1 and later.
    Example. Enables specific LUN “region” to be locked instead of entire LUN when cloning a VM.
  • SCSI Block Copy: Supported in vSphere 4.1 and later.
    Example. Avoids reading and writing of block data “through” the ESX host during a block copy operation by allowing VMware to instruct the SAN to do so.
  • SCSI Unmap: Supported in vSphere 5 and later. Enables freed blocks to be returned to the zpool for new allocation when no longer used for VM storage.

Additional “optimizations” and improvements from Nexenta in 3.1 include:

  • In-flight deduplication
  • ARC performance enhancements
  • multiple connections per session for iSCSI
  • DMU fast path for iSCSI (i.e. no extra copy)
  • Auto-sync “resume” with progress bar in GUI/NMV and ability to change source/destination paths OTF
  • Parallel tasks in NMV (i.e. no more busy process “hangs”)
  • Improved CIFS performance
  • Support for multiple DC/DC fail-over for CIFS
  • Better cross-forrest trusts with CIFS
  • Configuration monitoring/reporting via “ConfGuard” plug-in
  • Multiple VIP per service for HA Cluster, fail-over of local users and elimination of separate heartbeat device
  • JBOD management for select devices from within the NMV

Given the addition of VAAI features, the upgrade offers some compelling reasons to make the move to NexentaStor 3.1 and at the same time removes obstacles from choosing NexentaStor as a VMware iSCSI platform for SMB/SME (versus low-end EMC VNXE, which at last look was still waiting on VAAI support.) However, for existing vSphere 4.1+ environments, a word of caution: you will want to “test, test, test” before upgrading to (or enabling) VAAI (fortunately, there’s a NexentaStor VSA available).

Auto-Sync Resume

In the past, NexentaStor’s auto-sync plug-in has been the only integrated means of block replication from one storage pool (or array) to another. In the past, the plug-in allowed for periodic replication events to be scheduled which drew from a marker snapshot until the replication was complete. Upon extended error (where the replication fails), the failure of the replication causes a roll-back to the marker point, eliminating any data that has transferred between the pools. For WAN replication, this can be costly as no check-points are created along the way.

More problematically, there has been no way to recreate a replication service in the event it has been either deleted or missing (i.e. zpool moved to a new host.) This creates a requirement for the replication to start over from scratch – a problem for very large datasets. With Auto-Sync 3.1, later problem is resolved, and provided NexentaStor can find at least one pair of identical snapshots for the file system.

Where I find this new “feature” particularly helpful is in seed replications to external storage devices (i.e. USB2.0 arrays, JBODs, etc.). This allows for a replication to external, removable storage to (1) be completed locally, (2) shipped to a central repository, and (3) a remote replication service created to continue the replication updates over the WAN.

Additionally, consider the case where the above local-to-WAN replication seeding takes place over the course of several months and the hardware at the central repository fails, requiring the replication pool to be moved to another NexentaStor instance. In the past, the limitation on auto-sync would have required a brand new replication set, regardless of the consistency of the replicated data on the relocated pool. Now, a new (replacement) service can be created pointing to the new destination, and auto-sync promises to find the data – intact – and resume the replication updates starting with the last identical marker snapshot.

NexentaStor Native Transport

The default transport for replication in NexentaStor 3.1 is now NexentaStor’s TCP-based Remote Replication protocol (RR). While SSH is still an option for non-NexentaStor destinations, netcat is no longer supported for auto-sync replications. While no indication of performance benefits are available, two tunable parameters are available for RR auto-sync services (per service): TCP connection count (-n) and TCP package size (-P). Defaults for each of these are 4 and 1024, respectively, meaning 4 connections and 1024KB PDU size for the replication session.

Conclusions

For VMware vSphere deployments in SMB, SME and ROBO environments, NexentaStor 3.1 looks to be a good fit, offering high-performance CIFS, NFS, iSCSI and Fiber Channel options in a unified storage environment complete with VAAI support to accelerate vStorage applications. For VMware View installations using NexentaStor, the VAAI/ATS feature should resolve some iSCSI locking behavior issues that have made NFS more attractive but remove SCSI-based VAAI features. That said, with the storage provisioning changes in View 4.5 and upcoming View 5, the ability to pick from FC, iSCSI or NFS (especially at 10G) from within the same storage platform has definite advantages (if not complexity implications.) Suffice to say, NexentaStor’s update is adding more open storage tools to the VMware virtualization architect’s bag of tricks.

NexentaStor 3.1 is available for download now.

Update, 8/12/2011:

Nexenta has found some problems with 3.1 post Q/A. They’ve released this statement on the matter:

Nexenta places the highest importance on maintaining access to and integrity of customer data. The purpose of this Technical Bulletin is to make you aware of an issue with the process of upgrading to 3.1. Nexenta has discovered an issue with the software delivery mechanism we use. This issue can result in errors during the upgrade process and some functionality not being installed properly. Please postpone upgrading to v3.1 until our next Technical Bulletin update. We are actively working to get this corrected and get it back to 100 % service as fast as possible. Until the issue is resolved we have removed 3.1 from the website and suspended upgrades. Thanks for your patience.

- Nexenta Support, Aug. 6, 2011

According to sources from within Nexenta, the problems appear to be more related to APT repository/distribution issues “rather than the 3.1 codebase.” All ISO and repository distribution for 3.1 has been pulled until further notice and links to information about 3.1 on the corporate Nexenta site are no longer working…

Update, 8/17/2011:

Today, while working on a follow-up post, the lab systems (virtual storage appliances) were updated to NexentaStor 3.1.1 (both Enterprise and Community editions). Since a question was raised about the applicability of the VAAI enhancements to Community Edition (NexentaStor CE), I’ve got a teaser for you: see the following image of two identical LUNs mounted to an ESXi host from NexentaStor Enterprise Edition (NSEE) and NexentaStor Community Edition (NSCE). If you look closely, you’ll notice they BOTH show “supported” status.

vSphere VMFS5 Datastores provided by NexentaStor Community (VSA04) and Enterprise (VSA03) editions.

Update, 8/19/2011:

Nexenta officially re-released NexentaStor 3.1 today in the form of version 3.1.1 – it is available for download now.

h1

Short-Take: VMware View PCoIP Client for Android

July 15, 2011

Today VMware released a “Tech Preview” version of VMware’s View Client for Android: a PCoIP-only client suitable for LAN and WAN (via PCoIP Secure Gateway). We’ve had a quick first look this evening when the application appeared on Android Market – a free download – and it looks great. On my NotionInk Adam tablet (NVidia 1GHz dual-core) running Honeycomb 3.0.1 the display updates where just as snappy as my iPad2 running View Client for iPad. The only problem I experienced in the hour or so of working with the client is the lack of three-finger support in the Adam/Honeycomb port to spawn the pop-up keyboard.

The View PCoIP Client for Android supports the same saved desktop icon paradigm as it's iPad predecessor for quick access.

The View PCoIP Client for Android allows for desktop connections to stay active even when the app is not in the foreground - a one-up on the iPad predecessor.

Android View PCoIP Client - Task switching to other Android application

Task switching in View PCoIP Client for Android works just like any other Android application.

Android View PCoIP Client - Retrieving a View desktop from background

View PCoIP Client for Android is easily restored from the background without reconnection delays.

And yes, that last screen shot shows 1-bar on AT&T’s 3G network and it’s totally useable just like on the iPad. If you’re waiting for a rocking View client before plunking down money on that 10.1″ ASUS EEpad Transformer (now with Honeycomb 3.1) and it’s keyboard/mousepad “docking” station (complete with additional run-time doubling battery) then wait no more: Android has arrived. Remember though, this is just a “Tech Preview” and the apple needs a bit more polishing before you go running to your CIO…

SOLORI’s Note: Although the View Client for Android was “optimized” for 1280×800 format, it still had no problem with the more limited 1024×600 Pixel Qi display on my NotionInk Adam. In fact, changes in rotation on the Android seemed faster than on iPad2 and multitasking on the Honeycomb system did no seemed to be affected to a backgrounded desktop.

As another test to compatibility, I tested small-screen PCoIP goodness on my Samsung Fascinate and it rocks! Beware, there is just enough display to be useful with the pop-up keyboard on-screen, however and the scroll-back on the screen with keyboard in foreground made for interesting URL entry while trying to get to Hulu, but audio was clear and frame rates at about 3-5 fps (visual est.) but very clear. Task switching on the single-core Android Froyo device worked flawlessly too.

How did Hulu fare on Honeycomb? Unfortunately it was not up to scratch in full screen, but I found it passable in the embedded mode (Mozilla 3.6). This kind of performance issue will likely be very platform dependent on Android version, CPU, display and vendor tweaks to the Google Android kernel – especially hacked kernels like the NI Adam (tested). Unlike the Apple-controlled IOS, Android leaves a lot of performance enhancements to platform providers and most just pass-on the reference kernel without significant improvement in performance. For a “preview” release, Team Fox at VMware has delivered the goods.

VMware’s official blog post has a quick walk-through video. A User Guide and Release Notes are also available from VMware.

h1

Short-Take: VMware View, What’s Up with PCoIP?

March 21, 2011

Isn’t it time you looked at what VMware View and PCoIP have to offer? Now that there is a server off-load card supporting View PCoIP virtual machines, the overhead of display processing opens-up opportunities for denser View servers (or does it?) Here’s what VMware says about PCoIP in the “VMware View Architecture Planning Guide, View 4.6″

VMware View with PCoIP
PCoIP is a new high-performance remote display protocol provided by VMware. This protocol is available for View desktops that are sourced from virtual machines, Teradici clients, and physical machines that have Teradici-enabled host cards.

PCoIP can compensate for an increase in latency or a reduction in bandwidth, to ensure that end users can remain productive regardless of network conditions. PCoIP is optimized for delivery of images, audio, and video content for a wide range of users on the LAN or across the WAN. PCoIP provides the following features:

  • You can use up to 4 monitors and adjust the resolution for each monitor separately, up to 2560 x 1600 resolution per display.
  • You can copy and paste text between the local system and the View desktop, but you cannot copy and paste system objects such as folders and files between systems.
  • PCoIP supports 32-bit color.
  • PCoIP supports 128-bit encryption.
  • PCoIP supports Advanced Encryption Standard (AES) encryption, which is turned on by default.
  • For users outside the corporate firewall, you can use this protocol with your company’s virtual private network or with View security servers.
  • MMR is not supported on Windows 7 clients or virtual desktops.
    • Although MMR is not supported on Windows 7 virtual desktops, if the Windows 7 desktop has 1GB of
      RAM and 2 virtual CPUs, you can use PCoIP to play 480p- and 720p-formatted videos at native resolutions.
      For 1080p, you might need to make the window smaller than full screen size.

If you use PCoIP, the display protocol from VMware, you can adjust the display resolution and rotation
separately for each monitor. PCoIP allows a true multiple-monitor session rather than a span mode session.

  • The maximum number of monitors that you can use to display a View desktop is 10 if you use the RDP display protocol and 4 if you use PCoIP.

RAM Sizing for Specific Monitor Configurations When Using PCoIP
If you use PCoIP, the display protocol from VMware, the amount of extra RAM that the ESX host requires depends in part on the number of monitors configured for end users and on the display resolution. Table 4-1 lists the amount of overhead RAM required for various configurations. The amounts of memory listed in the columns are in addition to the amount of memory required for other PCoIP functionality.

RAM sizing for Multi-Monitor PCoIP sessions

When you consider these requirements, note that virtual machine configuration of allocated RAM does not change. That is, you do not need to allocate 1GB of RAM for applications and another 31MB for dual 1080p monitors. Instead, consider the overhead RAM when calculating the total physical RAM required for each ESX server. Add the guest operating system RAM to the overhead RAM and multiply by the number of virtual machines.

  • Software developers or other power uses with high-performance needs might have much higher CPU requirements than knowledge workers and task workers. Dual virtual CPUs are recommended for compute-intensive tasks or for Windows 7 desktops that need to play 720p video using the PCoIP display protocol.

Maximum Connections for View Connection Server
Table 4-7 provides information about the tested limits regarding the number of simultaneous connections that a VMware View deployment can accommodate.

This example assumes that you are using VMware View with vSphere 4.1 and vCenter Server 4.1. It also assumes that View Connection Server is running on a 64-bit Windows Server 2008 R2 Enterprise operating system.

Maximum Connections for View Connection Server

PCoIP Secure Gateway connections are required if you use security servers for PCoIP connections from outside the corporate network. Tunnelled connections are required if you use security servers for RDP connections from outside the corporate network and for USB and multimedia redirection (MMR) acceleration with a PCoIP Secure Gateway connection.

Network Bandwidth Considerations
For display traffic, many elements can affect network bandwidth, such as protocol used, monitor resolution and configuration, and the amount of multimedia content in the workload. Concurrent launches of streamed applications can also cause usage spikes.

Read the rest of this entry ?

h1

Short-Take: vSphere Client for iPad, Preview

March 18, 2011

I highlighted the installation and use of VMware’s vCenter Moble Access (vCMA) appliance in a post in late February. For the most part, vCMA has not changed much since our initial download back in April of 2009. If you downloaded the OVF early this February and looked at the updated instructions from the “fling” site, you may have noticed the following “curious” statements:

  • Once it powers on, you will need to configure your iPad by going into Settings, the vSphere client (usually bottom left corner of screen, in the Apps section), then you enter the IP address of your mobile appliance.
  • Finally, you can access your environment from the vSphere iPad app by entering your vCenter server info or ESX server info, with appropriate username and password.

vSphere Client for iPad

Having a heads-up from the vExpert team briefing by Srinivas Krishnamurti, Sr. Director for Mobile Solutions and Marketing at VMware, plus earlier press coverage from VMworld 2010 (see below), I knew what this “information leak” was hailing. Fortunately, the offending section (text above) was quickly redacted and VMware managed to avoid spoiling the surprise pending today’s [press release].

However, that was not the only source of “information leakage” prior to today’s announcement: you just had to know where to look. For instance, while looking deeper into the virtual appliance for our vCMA how-to, I found bread-crumbs pointing to more “curious” iPad wanderings. The following “Easter egg” was discovered in the “action-config.xml” file (which we held back under the spirit of the information embargo):

<!-- VCMA iPad Actions -->
 <action name="vcmaAbout" type="com.vmware.vcma.action.VcmaAboutAction"></action>
 <action name="vcmaLogin" type="com.vmware.vcma.action.VcmaLoginAction"></action>
 <action name="vcmaLogout" type="com.vmware.vcma.action.VcmaLogoutAction"></action>
 <action name="vcmaHome" type="com.vmware.vcma.action.VcmaHomeAction"></action>
 <action name="vcmaHostInfo" type="com.vmware.vcma.action.VcmaHostInfoAction"></action>
 <action name="vcmaHostOp" type="com.vmware.vcma.action.VcmaHostOperationAction"></action>
 <action name="vcmaVmInfo" type="com.vmware.vcma.action.VcmaVmInfoAction"></action>
 <action name="vcmaVmQuestion" type="com.vmware.vcma.action.VcmaVmQuestionAction"></action>
 <action name="vcmaVmAnswer" type="com.vmware.vcma.action.VcmaVmAnswerAction"></action>
 <action name="vcmaVmOp" type="com.vmware.vcma.action.VcmaVmOperationAction"></action>
 <action name="vcmaSnapshot" type="com.vmware.vcma.action.VcmaSnapshotAction"></action>
 <action name="vcmaPerf" type="com.vmware.vcma.action.VcmaPerfAction"></action>
 <action name="vcmaSearch" type="com.vmware.vcma.action.VcmaSearchAction"></action>
 <action name="vcmaPing" type="com.vmware.vcma.action.VcmaPingAction"></action>
 <action name="vcmaTracert" type="com.vmware.vcma.action.VcmaTraceRouteAction"></action>
 <action name="vcmaVmsList" type="com.vmware.vcma.action.VcmaVmListAction"></action>
 <action name="vcmaMonitorTask" type="com.vmware.vcma.action.VcmaMonitorTaskAction"></action>

This grouping of action/command definitions identify 17 of 23 vCMA action classes. These classes meant four things to me: (1) the actions are tuned specifically for a non-HTML-only client; (2) the limitations of vCMA’s web interface do not bind the iPad client; (3) there is significant potential for “capabilities drift” between the iPad client the “generic” mobile access client (i.e. HTML) as time goes by (read: richer feature set, user options); and (4) other “tablet” or “mobile” clients can’t be too far behind.

Since it is not feasible to have iPad software previews for vExperts (i.e. via iTunes) for pre-release products, this “pre-view” is based on exposure to product briefing and other pre-launch sources (direct and indirect). We’ll be following-up within the week with actual hands-on experience… That said, here’s what’s going on with VMware and iPad:

vSphere Client for iPad

Today, VMware CIO Steve Herrod announced the launch of version 1.0 of the vSphere Client for iPad (vCiP). The aptly named utility runs on Apple’s current generations of iPad and provides access to many of the basic administrative functions available to vCenter and the standard vSphere Client. This release must be seen as a quick, 1-2-3 punch of mobile and management-centric releases for VMware in the span of two weeks: vCenter Ops, View Client for iPad and now vSphere Client for iPad.

This iPad application is not truly a “native” or “fat” client for vSphere in the “conventional Windows sense.” Instead, VMware’s new app deploys as a web service reliant application (typical of its iPad ilk), and it is accordingly “small, light and elegant.” As you might guess from the [leading] introduction, the “heavy lifting” is actually performed by VMware’s vCenter Mobile Access (vCMA) appliance through the set of new classes (conveniently listed above).

VMware diagram showing (optional) placement of firewall, vCMA, vCenter and vSphere clusters. The use of a VPN connection to your firewall is strongly recommended as vCMA deploys with its web service without SSL enabled.

This illustration depicts the “best practice” recommended deployment for the iPad client by way of a trusted VPN connection. Again, this information was provided to us from Srinivas and his team “pre-launch” and hence was also prior to the recently released enhancements in vCMA (see below). In either case, the connection from iPad to vCenter is always translated through vCMA.

Like the standard Windows “fat” client (now conveniently available as a ThinApp’d zero-install package), the iPad client login requires the following credentials:

  1. The IP address or DNS host name for your vCenter;
  2. A valid user name with rights to access/manage the target vCenter;
  3. The password for the vSphere user.

Unlike the Windows variant, the following must be configured into the iPad’s “Settings” for the vSphere app prior to initial connection:

  1. The IP address or DNS host name for your vCMA appliance (displayed as “Web Server” in “Settings”).

vCMA’s web service is not SSL encrypted, and these credentials could be passed “in the clear.” (see updated post, SSL added to vCMA this Tuesday.) Given this client is targeted for mobile use, the risk of exposure to insecure networks (Internet, public WiFi, etc) without SSL would have created “special” opportunities for man-in-the-middle attacks. However, the use of a mobile VPN connection for the iPad client is strongly recommended, but no longer strictly necessary.

Read the rest of this entry ?

h1

Quick-Take: Buying an iPad2 on Friday

March 10, 2011

New iPad2, launcing in White and Black "on day one"

If you’re chomping at the bit to buy an iPad2 on launch day, the question remains: which one to buy? There seems to be many options and ways to go, but ultimately this will end-up being a personal decision. However, there is an economic and functional rational that you should consider before coughing up nearly $1K on an arguably cool device.

Given the choices of models and network options, this should definitely NOT be an impulse buy, and I hope you look at it in a reasoned – if not somewhat giddy – way. Here are my thoughts for personal acquisition (not for businesses – you guys need to run POC for at least 3-6 months!):

Basically, there are three models: WiFi, WiFi+3G/ATT & WiFi+3G/Verizon, with three flash variants of each – 16GB, 32GB & 64GB – and two color variants of those – black & white. That’s a total of 18 different SKU’s for iPad2. So here’s how the process breaks down to me:

  1. Since WiFi/Bluetooth is the same on all models, choose first between 3G (includes aGPS) or WiFi-only (no aGPS);
    1. Choose carrier between ATT & Verizon (either are month-to-month):
      1. ATT offers two options for iPad2:
        1. $15/month for 250MB/month; with automatic charge of $15/250MB overage;
        2. $25/month for 2GB/month; with automatic charge of $10/1GB overage;
      2. Verizon offers four options for iPad2 WiFi-only + MiFi:
        1. $20/month for 1GB/month; with automatic charge of $20/GB overage;
        2. $35/month for 3GB/month; with automatic charge of $10/GB overage;
        3. $50/month for 5GB/month; with automatic charge of $10/GB overage;
        4. $80/month for 10GB/month; with automatic charge of $10/GB overage;
        5. Note: MiFi device is free only with a 2-year contract.
      3. Verizon offers four plans for iPad2 WiFi+3G:
        1. $20/month for 1GB/month; with automatic charge of $20/GB overage;
        2. $35/month for 3GB/month; with automatic charge of $10/GB overage;
        3. $50/month for 5GB/month; with automatic charge of $10/GB overage;
        4. $80/month for 10GB/month; with automatic charge of $10/GB overage;
    2. Choose memory size; 3G Models will cost according to their memory size regardless of carrier:
      1. $630 for 16GB, black or white;
      2. $730 for 32GB, black or white;
      3. $839 for 64GB, black or white;
    3. Choose color;
      1. Black;
      2. White;
  2. For WiFi-only models, you’ll give-up accurate location (no aGPS) but save money (see MiFi above for mobile access):
    1. Choose memory size; 3G Models will cost according to their memory size regardless of carrier:
      1. $630 for 16GB, black or white;
      2. $730 for 32GB, black or white;
      3. $839 for 64GB, black or white;
    2. Choose color;
      1. Black;
      2. White;
  3. Choose how you want to purchase:
    1. In-store (5PM local time):
    2. On-line (1AM PST):
  4. Enjoy iPad2 nirvana!

SOLORI’s Take: Steve Jobs really wants to see you on-camera and in line. Apple made a point to require retailers to coordinate sale starts at 5PM local time to be able to maximize “free” advertising benefits based on local, mobile news feeds from “high demand queues” at retailers. There’s no discount for purchasing after standing in a retail store line, so why queue-up without compensation just to be part of the iPad2 marketing push? Buy from an on-line retailer (or wait) and avoid the lines.

As for the model and plan, economically the 16GB iPad2 makes the most sense. If you need 3G but have no interest in using your iPad as a navigation unit while you drive, get MiFi and get the benefit of being able to use it with up to 5 other devices (laptop, iPad1, Android tablet, etc.) If you’re replacing your 32GB+ iPad and laptop (good luck) in this purchase, you may go all out, but don’t be surprised when buyer’s remorse sets-in a month or so hence. Then it comes down to 3G variant: ATT has more global reach (see link above), but beware of “data roaming” charges, while Verizon has a bit better $/GB rates (see above).

If you choose to que-up and volunteer for Steve Jobs unpaid marketing army, good luck and stay safe. According to BestBuy’s playbook, you’ll get a “ticket” for the model you want in line. There will only be tickets enough for the actual models they have and they’ll likely only know what that list is one to two hours before 5PM local time. When all tickets are gone, they’ll issue standby tickets for the next day, etc. At BestBuy at least, you’ll need to leave a $100 deposit with your standby ticket and it will be issued in the form of a $100 gift card usable towards your iPad purchase.

[Update: SOLORI's iPad2 ordered for the lab at 2:53AM CST from ATT on-line - black, 16GB WiFi+3G, 2GB/mo. data plan. Verizon, Walmart, Target all show iPad2 as unavailable on-line and in stores at 5PM.]

[Update: On-line supplies of iPad2 started at 2-3 business day promised delivery and had gone to 2-3 week delivery by 9:30AM PST.]

[Update: 15-Mar-2011 - USPS delivered iPad2 - 2 business days achieved.]

h1

Short-Take: Windows 7 for iPad, Free

March 9, 2011
Windows7 running on iPad

Windows7 running on iPad

Remember that announcement about View 4.6 and the PCoIP Software Gateway (PSG) a week or so back? If the existence of PSG got your imagination drifting towards running Windows7 over PCoIP on your iPad or Android tablet, then some of you are going to be very excited and some of you will have to wait a little bit longer.

Today VMware is taking mobile desktop to a new level by announcing the general availability of the View Client for iPad V1.0 – Android tablet users will have to wait! This is a iPad-native, PCoIP-only client for View 4.6 environments (i.e. PCoIP w/PSG support) with  gesture-enabled navigation and virtual mouse pad. If you liked accessing your View desktop in Wyse’s PocketCloud for iPhone & iPad (RDP mode only), you’re going to love the View Client for iPad because it unlocks the rich, PCoIP goodness that you’ve been missing.

Last week a group of vExperts were briefed on the iPad app by its development team leader Tedd Fox who came to VMware in August, 2010 after nearly 8 years of work at Citrix (co-inventor/designer of Citrix Reciever for iPad & iPhone). To say Tedd knows iPad/mobile and remote app/desktop is an understatement, and VMware has committed to an aggressive “feature update” schedule for the iPad app on the order of every 1-2 months (typical of mobile application norms.)

Needless to say, we had a few questions. Here’s just a few of the responses from our Q/A and demonstration session:

vExpert: Will there be a iPhone link for touchpad control?

Tedd: No. Due to some patent-pending issues, we decided not to tread on that ground.

vExpert: Has it been enhanced for the iPad2?

Tedd: No. It’s [iOS] 4.3 “ready” but nobody’s got an iPad2 so no one knows if there application’s going to work. We’ve tested on dual-core architecture before, just not Apple’s dual-core architecture.

vExpert: Dual-core tested? So there’s an Android app coming?

Tedd: Android app is coming! We’re looking at mid-year for the Android. I just spent a few weeks in China getting that in alpha-alpha mode; so we actually have a UI and everything – we’re just building-up the bits… it’s going to be tablet only. It works on a 7″ right now, but we’re not sure if that’s a useful form.

vExpert: Is that because it’s too small [i.e. 7" screen]?

Tedd: It’s because of the mouse pad and everything… it just doesn’t feel right – the resolution and everything.

vExpert: Not even with panning and side scrolling [small screen]?

Tedd: Not really. Panning a windows desktop is “okay” for like 10 minutes, after which you develop something like Tourette syndrome with curse words and all. We actually ran tests on that to figure that out, but it could change [given the right demand/use case.]

vExpert: Will it support bi-directional audio?

Tedd: No, uh, uni-directional is definitely on the roadmap so doctors can dictate and stuff like that. Otherwise, we’re going to see how the protocol matches up for [more complex] audio applications.

vExpert: Can we get more information on the Android app?

Tedd: I don’t want to get into the Android client because everything is still “in flux” and we’re still designing it…

vExpert: Will [View Client for iPad] work with bluetooth mouse and keyboard?

Tedd: Yes… You have to go into the iPad settings and pair them… then with you do the three-finger tap on the screen – like to activate the on-screen keyboard – that’s how you activate the bluetooth keyboard [only, no mouse support per Apple policy], and the [on-screen] toolbar drops down to the bottom of the screen… It’s very nice to use.

vExpert: Will it support multitasking, multiple sessions and session swapping?

Tedd: No. We’re working with Teradici on full-multitasking for one of the feature revs this year.

vExpert: It seemed that logging-in and getting to your desktop seemed pretty quick. What would you say?

Tedd: This [demo] is on 3G – by the way – so it’s fairly quick. The only [downside] is if you’re using RSA tokens: you’ve got to read the token and put it in… If the broker policy allows users to save their passwords, then you’d only need the token code.

vExpert: Is there a way to transfer data to/from the iPad from the [View client desktop]?

Tedd: Working on that – that’ll be in the next rev or two. There’s a grey area there with the shared foldering system in iOS – some people are like “yeah, awesome” but if you talk to DoD they’re like “heck no” so we’re working on an elegant solution.

vExpert: What about dropbox or something like that?

Tedd: If we have an internal solution then yes. I don’t want to be [bound by a third party] on our app – I want to keep it as “pure VMware” as possible. If the market screams for it in enough number, then of course I’m going to listen… If it’s allowed in your desktop’s environment [dropbox will work.]

vExpert: How’s the performance of the View client while other programs are in the background on the iPad?

Tedd: You don’t even notice it. If you know me you know I’ve constantly got white earbuds on. One of my test cases was working on a desktop while running on Pandora in the background.

vExpert: Price is free?

Tedd: Yeah, as long as I’m with VMware it will always be free.

Over the course of the demonstration, we saw Tedd put the application through its paces. It’s fast – even on the original iPad. The gesture interface looks well thought-out, has been thoroughly tested – Tedd says “rock solid” – and repeated three-finger abuses [rapid toggling the keyboard] won’t crash the View iPad app. Can’t wait to get it into SOLORI’s lab…

Gesture Help for iPad View Client

View Client for iPad Keyboard (three-fingers to pop-up)

View for iPad soft mouse pad and cursor keys

 

Client support for tap-hold loupe: zoom near mouse pointer.

Related Links:

[Update: View 4.x -> View 4.6 (iPad Client designed for View 4.6 and PSG). Added community blog link, virtual keyboard and loupe screenshots. Remote add -> Remote app. Added link to Andre's VDI calculator. Clarification on bluetooth mouse support. Related links section with PCoIP off-load.]

Follow

Get every new post delivered to your Inbox.