Home > Blogs > Tribal Knowledge > Monthly Archives: August 2009

Monthly Archives: August 2009

Mobile Phones – The Next Frontier

[photo of Srinivas Krishnamurti]

Posted by Srinivas Krishnamurti
Director of Product Management and Market Development

You may have seen the announcement about the VMware Mobile Virtualization Platform in November 2008 or the MVP demo in Steve Herrod’s Future of Virtualization keynote at VMworld Europe 2009 and wondered what we were doing in this space, given our heritage in virtualizing x86 systems – desktops and servers.  I wanted to share our thoughts and vision for mobile phones to explain why we entered this space and what we intend to do.

Why Mobile Phones?

Image001 Image003
Mobile phones – then and now … (source: Freefoto.com)

Mobile phones are fundamentally and rapidly changing in many ways.  If you think about your mobile phone from 5-7 years ago, it was primarily a communication device that allowed you to save telephone numbers.  Now compare that with the mobile phone you have now (well, this exercise is only for those of us who have a smart phone…)  You can now check your emails, browse the internet, play games, watch TV/videos, listen to music and many other things from your mobile device.  Today’s mobile phones are computational devices, not mere communication devices.  They really are a small computer in your hand; the next generation PC!  In some cases, you can do more things on your mobile phone now – GPS technology has allowed developers to bring forth a vibrant set of LBS-type applications that are very useful and cool.  Mobile payment applications are another category that is catching on as well…

If you think about mobile phones as the next-generation PC, it is only reasonable to expect all the good and bad things about PCs to be relevant on mobile phones, if they aren’t already.  Some of the good things include a huge collection of applications; more powerful devices with more CPU horse power, more memory and better graphics capabilities that allow you to watch videos/TV, play better games, etc.  Some of the bad things include security of the device and headaches in managing devices that are more mobile than laptops.

We formulated a three-prong strategy that allows us to bring innovative solutions in this new market.

  1. More applications:  RIM’s BlackBerry got us all hooked on checking emails from mobile phone and for the longest time, emails were the killer application for mobile phones.  Apple has since shown that if it is easy to develop and get applications, developers will build mobile applications and consumers will download them.  Now consumers are downloading all kinds of applications onto their mobile phones.  As I was thinking about my usage pattern, I realized that there are some applications that I use more on my iPhone than on my Mac – the Facebook app is one example.  I still use the application on my laptop but I find that I can do many of the common things from my iPhone and it is more accessible.  The second thing that I realized is that there is tremendous innovation in the consumer space that eventually gets rolled into the enterprise when us old geezers finally “get it.”

    Image007 Image009

    You may be thinking, ‘yeah, ok, but what does that mean for me?’  Let’s say you are out at your kid’s soccer game and receive a call that a server is down.  Instead of rushing to find the nearest PC, what if you can restart the server from your mobile phone?  We believe enterprises will like that type of flexibility to perform some operations irrespective of where you are.  To that end, we recently launched a technology preview for VMware vCenter Mobile Access.  vCMA will allow you to monitor and manage parts of your internal cloud.  Over time we will figure out what other parts of vCenter and other products need to have a mobile phone interface.

    To download vCMA, visit: http://communities.vmware.com/community/beta/vcmobileaccess.  Also, the vCMA team has a VMworld session on this topic so if you are attending VMworld in SF later this month, please attend this session.

  2. Accessing your desktop:  We are getting a lot of traction for our VDI initiative that allows enterprises to completely redefine how they think about deploying and managing PCs.  Users really care about a set of applications and data and not very much about the particular device they need to use to be productive.  IT folks want to effectively and efficiently manage these applications and data that their “customers” depend on.  By virtualizing the desktop and running that in the cloud, users can now access their desktop from a desktop, laptop or a thin-client device.  Under the VMware View umbrella of products, we are releasing a great set of functionality that allows IT to manage these virtualized desktops.

    Most mobile phones now have WiFi capabilities and with the data networks getting faster and faster with 4G and WiMax deployments starting up, we believe mobile phones will become the next generation thin clients.  Imagine connecting your phone into a monitor and keyboard to access your desktop running in the cloud.  We believe this will take mobility and accessibility to the next level.  We realize that there are a few usability issues and technological shortcomings that need to be addressed and expect that they will be either by us or our partners.  As you think about your desktop strategy, you should incorporate some thoughts about this model.

  3. Virtualized phones: Most everyone who first hears about mobile virtualization scratches their head wondering why you need virtualization on a mobile phone.  If I had a dime for every time people asked me for the elevator pitch on this, I definitely wouldn’t need to work for a few years.  While there are many benefits across the value chain all the way from the semiconductor vendors to handset OEMs to carriers to enterprises to consumers, I want to focus on the enterprise use case in this note.

    There are two major trends in enterprises when it comes to mobile phones.  First, more and more enterprises are purchasing and giving out mobile phones to more and more employees because the productivity benefits associated with this move are well understood.  Second, more and more employees already have a very cool and capable personal phone and wonder why they cannot simply use that device instead of getting a second device from IT.  Due to security concerns, IT has traditionally not allowed employee-owned devices to connect to or manage corporate resources so the unfortunate implication is that a good number of employees carry two phones.  If accessing your email and calendar is the only thing you want to do from a mobile phone, this isn’t much of a problem since Active Sync provides some basic management capabilities but we are seeing an increasing trend where many enterprises applications are being ported to mobile phones.  See point 1 above about vCMA.  You certainly don’t want your IT folks managing your datacenter from their personal mobile phone, do you?  When you start thinking about doing more than just email, you will realize that the security concerns of allowing employee-owned devices are legitimate.  This is where virtualization will play a key role.

    Mobile virtualization is like server virtualization in that it allows you to run multiple isolated virtual environments on a single device.  With server virtualization, you run multiple server or desktop workloads in virtual machines on a singe physical server.  With mobile virtualization, you run multiple virtual phones on a single device i.e. you run your home and work phones on a single phone in two isolated containers with completely separate identities – two telephone numbers, two contact lists, two calendars, two sets of applications, two set of rules/policies, two bills for telephone and data charges, etc.  There is a clear separation of church and state or in this case, home and work on your device.

    The benefit is that employees can now use a device they already own while IT can efficiently manage the “work phone” running on this device.  You can see some early demos of this at:

    The MVP team has a session on this topic at VMworld so please attend this session to find out more details.

I hope this gives you a bit of insight into what we are up to.  Your feedback is most welcome.  Also, I will blog more on each of these initiatives in the future so look out for more information.

One final thought: VMworld 2009 is right around the corner in beautiful San Francisco, CA from August 31 until September 3rd.  The track owners told me that the sessions will be great and having attended a few meetings about keynotes, I can assure you that you will like both Paul’s and Steve’s keynotes.  More than anything else, VMworld is a great opportunity for you to network with your peers and VMware employees, and see what else is happening in the virtualization ecosystem.  If you haven’t registered yet, do it now!  You won’t regret it!  Hope to see you there.  Happy Summer!

[Follow Srinivas on Twitter at skrishna09]

VMware to acquire SpringSource

Steve_Herrod Posted by Steve Herrod
Chief Technology Officer and Senior Vice President of R&D

Hi Everyone,

extremely excited to announce VMware’s intention to acquire SpringSource, a 5
year-old company rapidly becoming a leader in enterprise and web application
development and management. The goal of this blog is to explain the
complementary benefits of this merger to longtime VMware fans as well as to the
vibrant Spring community who may know less about us. First, a quick
introduction to SpringSource…


began as the commercial development team leading the innovative Spring
portfolio of open source projects, an effort focused on providing a simpler,
lighter-weight alternative to the Java EE (J2EE) standard. Led by Rod Johnson
(author, enterprise java authority, and SpringSource CEO), Spring has become
the de facto standard programming model for modern enterprise Java, rich web,
and enterprise integration applications. Over the last couple of years,
SpringSource has expanded their purview across an even broader range of
offerings, employing the thought leaders within the Apache Tomcat, Apache HTTP Server, Hyperic, Groovy and Grails open source communities.

A Common Mission: Simplify IT

Since our
founding 11 years ago, VMware has focused on simplifying IT; removing the
rigidity baked into today’s desktop and datacenter infrastructure to save on
capital and operating expenses while simultaneously allowing enterprises to
move faster towards their business needs. Companies typically spend 70% of
their IT budgets just on keeping their datacenters going… replacing failed
components, troubleshooting outages, repelling security attacks, and doing
other tasks that are focused on keeping the lights on. Our mission (and in
fact, the promise of “Cloud Computing”) has been to shift the spending of this
70% budget towards activities that move the business forward… creating new
applications that generate revenue, make them more competitive, or just improve
the bottom line. The most recent deliverable on this mission is VMware vSphere 4. This is our datacenter offering that simplifies IT by
severing the tentacles that unnaturally tie software to hardware and reaping
the encapsulation, flexibility, and automation benefits that follow. [For those
of you new to vSphere and its goals, we have a (somewhat marketing-y) overview
video here.]

has also been a technology innovator with a very similar mission, but focused
on the application-centric areas of IT rather than on the hardware-infrastructure focus that VMware is associated with. SpringSource’s obsession
has been simplifying and automating the build-run-manage lifecycle that all
applications go through, and they have done so by attacking similar pockets of
complexity. They bring this complexity-busting focus to several areas…
high-productivity developer tools and frameworks, lightweight application
server runtimes, and application management and monitoring. The end goal is
very similar; attack the time and money spent on application complexity and
maintenance tasks, shifting the focus to new and more reliably deployed
applications. SpringSource summarizes this mission with the following picture:


This shared
mission is what brought us together in initial partnering efforts late last year. As a combined
entity, the existing efforts and missions will continue, but we’ll also work to
jointly sever a whole new collection of tentacles… the ones that unnaturally
tie an application to the rigid way it must be deployed and managed.

How do VMware and SpringSource

VMware has traditionally
treated the applications and operating systems running within our virtual
machines (VMs) as black boxes with relatively little knowledge about what they
were doing. However, whether it’s around speed of deployment, application
performance guarantees, or providing resiliency in the face of component
outages, we will be able to provide even more capabilities as we bring even
more knowledge of the application and infrastructure layers together. We will
do this by adding interfaces into vSphere that SpringSource offerings (and
other application frameworks) can take advantage of and by extending our
management and automation capabilities to be aware of these interactions. A lot
of our early “vApp” thinking has been based on this separation of application
code from the requirements it has on the infrastructure on which it will be


frameworks already separate out a lot of the hardware and software
infrastructure requirements from the application code itself, and we’ll focus
on building on and extending these capabilities. For example, as a developer packages
up their Java application for deployment, they can indicate at a higher-level
how this code will interact and communicate with other hardware and software components.
At deployment time, the virtualized infrastructure can automatically provision
the database and application server VMs required by this application, wire the
VMs’ network connections together, and program vShield Zones to open up only the appropriate network ports between them.

At runtime,
even more exciting things can happen. Information from the frameworks and tools
such as Hyperic can pinpoint slowness in the service, and we can remediate the problem
areas by altering settings of VMware DRS, cloning another instance of the web server VM, or even
interacting with the traffic managers of the datacenter to balance out the
load. And on the runtime availability front, backing all of this are
capabilities such as VMware Fault Tolerance and VMware HA, which can help the components survive hardware failures or
automatically restart as appropriate.

The above is
a fairly naïve and simplified example, but hopefully it gives you a flavor for
where these combined efforts can go. And we absolutely must
go on this journey with a continued emphasis on openness and in delivering
value in an evolutionary way.


VMware has always emphasized choice; choice in which
operating systems you leverage, which applications you run, and which hardware
you run VMware products on. We’ve also proactively pushed on industry standards
(such as OVF)
that make it easier to choose non-VMware virtualization solutions if so
desired. This openness is good on several fronts:

  • customers will more aggressively pursue
    solutions that don’t restrict their future options,
  • it enables and accelerates competition,
    which pushes vendors to
    continuously innovate and add value, and
  • it enables a more evolutionary path to
    reaching end goals versus requiring complete infrastructure or application

As we bring application-related assets into VMware, we know
that we must double-down on our focus on openness and choice. We want to enable
all applications, both existing and new, to reap the full benefits of
running on vSphere, and we will make the same virtualization and management
layer interfaces available to other application frameworks and middleware components.
We have early efforts underway around .Net, PhP, Ruby, and J2EE, and will
continue to focus on expanding these as well as newcomers in the rapidly
evolving development world. This picture attempts to show how this all comes
together around vSphere:


Furthermore, we will continue our openness at the vSphere management
layer, making the interfaces to the applications and infrastructure easily
available for non-VMware management tools to access and interact with.

SpringSource also has a huge focus on openness and choice.
SpringSource employees are stewards of Spring, Tomcat, Hyperic, and their other
offerings, but their respective successes are the result of the vibrant
communities that have grown up around them. Furthermore, this space is
characterized by customers who wish to pick and choose which of these
components they want to use and easily blend them together with other IDEs,
programming methodologies, application servers, and management tools.


Let me be absolutely clear on this… our commitment to openness
will continue and even grow.  And In
particular, the Spring framework will continue to be as open and portable as
ever. We’ll continue to target it at non-SpringSource middleware and management
tools, and we will also continue to enable and support deployment on non-VMware
virtualization offerings and even (gasp!) physical hardware. Rod Johnson
himself will make the decisions as to where Spring goes and how it remains as
open as it is today.

On a personal note, I’m as excited about the community
aspects of SpringSource’s offerings as the opportunity to work with Rod Johnson
and the other smart people and cool technologies at SpringSource. I believe
many of the existing VMware products will benefit from the lessons of openness and
community-building that SpringSource has learned.

And what about the whole “cloud”

openness, and in fact the complementary nature of what our two companies are
doing, makes even more sense in the context of cloud computing. We have spent a
lot of time discussing our views of cloud computing and launched the vCloud Initiative to realize this vision (more
detailed videos and slide shows are available here and here). Our approach to the cloud is

  1. Deliver
    software to the enterprise that brings the salient traits of cloud computing to
    their on-premise datacenters. These traits include resource elasticity,
    simplicity at scale, self-service portals, and the option of charging internal
    customers based on their resource usage. Building the “internal cloud” has been
    the focus of our vSphere and vCenter product lines.

  2. Offer
    software to hosters, service providers, telcos, outsourcers, and other owners
    of external datacenters that lets them offer computational capabilities to the
    enterprise. We base this software offering on vSphere and vCenter as well, and
    the beauty of this approach is that it is compatible with what companies are
    doing within their own datacenters. VMs are completely portable to these “external
    clouds”, and they’ll get the same levels of availability and performance
    guarantees when they run them here. This is the focus of our VMware Service Provider Partner Program.

  3. Connect
    internal and external datacenters together to create what is increasingly
    referred to as the “private cloud”. We are working with our partners to connect
    the internal and external clouds on a number of fronts such as how to migrate
    applications to and from the datacenters and a common management view of
    application assets regardless of where they’re running. In this way, we hope to
    provide an evolutionary path for companies to leverage externally provided
    datacenters on their own terms and as they’re comfortable with compliance,
    security, SLAs, data placement, or other concerns facing their business.

This is the canonical picture we use to illustrate the vCloud


So why did I
just babble on about this? The key is in how SpringSource and other application
frameworks enable and support this same view of the world as virtualization,
modern application frameworks, and cloud computing converge.

with choice

Our common
goal is for developers to easily build their applications and move from coding
to production execution as seamlessly as possible… regardless of whether they
will be deployed to a small internal datacenter for limited use or to a
completely external cloud provider for much larger scale audiences (and the hopes
of achieving Facebook application stardom!). This end
state has a lot in common with what is today referred to as “platform as a
service” (abbreviated PaaS). Salesforce.com’s
Force.com and Google’s AppEngine are two of the best known examples of PaaS today.

simplifies IT infrastructure and accelerates application development by
providing a self-service, self-managing utility for building, deploying, running,
and managing applications. As we see it, the key characteristics of PaaS are:

  1. Elasticity:
    automatically scaling up and down the infrastructure to meet the needs of the
  2. Multi-tenancy:
    being able to isolate resources and applications from one another in a shared
  3. Simplified
    provisioning: Isolate the developer from worrying about how is code gets
    installed and deployed
  4. Self-service:
    allowing developers to gain access to their development infrastructure at any
    time, in many cases to circumvent the processes and inefficiencies of their
    typical IT service request processes.
  5. Rapid
    development: go from code to cloud in a matter of minutes, particularly during
    the development and test phases
  6. Simplified (or invisible) management:
    PaaS offerings typically have built-in application availability and performance

vSphere, we are providing the elasticity, multi-tenancy, and simplified
provisioning traits. On the self-service front, we are aggressively extending
our VMware Lab Manager product to be a more general
self-service portal for both internal and external clouds. And when we combine
vSphere with the Spring framework, Spring runtime components, and Hyperic management
capabilities, we add rapid development models and simplified management to the

key difference between our offerings and existing offerings will be centered on
choice. By severing the tentacles that today tie what you want to run to where you want to run it, VMware can
provide the benefits of PaaS, but with significantly more customer choices. Combined
SpringSource/VMware PaaS offering can be hosted at
customer datacenters or at external service providers. For example, customers can
achieve many of the efficiencies and developer productivity gains of PaaS
without requiring the applications to be run outside of their walls. Today’s
PaaS offerings often force you to simultaneously commit to both a programming
model and to a vendor who will host the applications written to this model. With VMware’s strategy, any vendor in
the vCloud ecosystem will be able to offer a SpringSource-based PaaS offering,
allowing customers to select the partner that best suits their changing needs.

And one last point on openness of relevance here.
SpringSource will continue to seek out and embrace other virtualization and
cloud offerings that suit their customers and development community. Likewise,
we will focus on extending the above goals and capabilities to non-SpringSource
development frameworks. It certainly makes engineering work trickier, but
maintaining choice is an absolute requirement these days as VMware continues
the quest to simplify IT.

So pull it all together and what do you have… a morphing of
our two canonical pictures :-).


In verbal form, our shared vision is smarter infrastructure in which the virtualization platform
collaborates with application framework, server and management software to
ensure optimal efficiency and resilience.
And we will do this regardless of whether you run these applications inside or
outside of your datacenter.

And what’s next?

Whew… I’ve well exceeded the amount one should
attempt to squeeze into a single blog entry. There’s a lot more to talk about,
and you’ll see the combined vision and deliverables further gel in the coming
weeks. I’ll close with a shameless plug for VMworld where we’ll share
additional details and show some demonstrations of how SpringSource and VMware
can work together to simplify IT.


Thanks for reading this, and here’s to an
exciting future!


A SpringSource

November 2002:

Johnson (SpringSource CEO) publishes “J2EE Design and Development” including
30,000 lines of code that are the starting point on the Spring framework.

February 2003: Beginnings
of the Spring Framework open source project.

July 2004: SpringSource
founded by the core Spring developers.

Jan 2008: Acquires
Covalent Technologies, which provides services for users of Apache Software
Foundation projects. These include the Apache Tomcat and Geronimo application
servers and the Apache Axis Web services framework.

April 1, 2008: Microsoft
buys SpringSource in an April Fools’ Day stunner :-).

November 2008: Acquires
G2One Inc., the company behind the popular Groovy and Grails technologies.

May 2009: Acquires
open source system monitoring vendor Hyperic to provide availability monitoring
for hardware and operating systems, VMs, databases and application servers, and
is targeted at web infrastructure.