1 Comment

The beta release of VMware Studio 2.0 and using it to create vApps was the topic of this week’s podcast. Studio 1.0 came out last year; this beta moves the bar significantly. We also got into why you as a VMware admin should care about vApps – without being too hyperbolic I think it’s going to be the organizing paradigm that will change how we think of applications — from a VM level to something much higher-level and more manageable. Going back to Studio, here’s the high-level description:

VMware Studio 2.0 helps configure, build, deploy, customize and
maintain vApps and virtual appliances. These solution stacks can be
deployed on VMware vSphere 4.0 or in the cloud and can be managed from
the VMware Studio web console or from VMware vCenter Server. In this
webinar, software vendors, application developers and IT administrators
will get an overview of vApps and virtual appliances followed by what’s
new in Studio 2.0. We will walk you through the entire build process by
starting with an application created in Eclipse (via the Eclipse
plug-in in Studio) and demonstrating how it can be packaged as either a
vApp or virtual appliance in OVF format. The process will also reveal
various automated tools available, for creating a clean out-of-box
experience, such as specifying exact OS requirements, building an
update repository, adding custom management services and adding
existing VM builds as input.

As always, listen in via the widget to the right, the mp3, or via iTunes.

More links:

Non-Studio topics we discussed:

A few of the podcast attendees have already weighed in with their reactions – mostly about the significance of using vApps in the enterprise. I wasn’t kidding when I used the word ‘paradigm’ above.

Stu from, who is known to tell it like it is, liked it, he really liked it.

Rich Brambley:  VMware Studio 2.0 and OVF Exports: Blurred Products or Outside The Box Thinking? | VM /ETC.

outline potential Studio / OVF usage that may be “outside of the box”
from the VMware software’s intended purpose. Or is it? You tell me.

vCenter / Deploy from template

The ability to export any VM as an OVF from the VI Client by itself,
let alone VMware Studio, opens the door for template deployment in
environments without vCenter. Build a VM to desired corporate standards
and then export a copy of it to a shared network drive where it can be
used as a master image for future deployments on any virtual platform
that supports OVF.

With VMware Studio build a multiple VM apllication as a vApp.
Configure the web server and the database for example, and before
adding any data export the combination as an OVF. Deploy the vApp OVF
as a master template as needed.

Sure, vCenter offers so much more automation for this process, but
what about for deployment between ESX hosts that are not managed by the
same vCenter or don’t share the same storage? …

Daniel Eason: Virtually Insane?: The Virtual Glue.

By deploying turnkey Virtual Appliances with for example a new SAP ERP
Landscape on 10-20 Machines in a period of say 2-3 days rather than 2-3
Machines in 10-20 days clearly shows that current long deployment
processes are redced and less people need to be involved on a
deployment when using Virtual Appliances alongside side orchestration
and groupings such as vApp. The problem however with this is you get
people protective on roles and the oldage turf war developing so it is
not something that can be just implemented straight away. …

vApps functionality
in vSphere enables organisations to reduce even more manual and people
process. It enables you to compile the complete application stack and
configure all associated components by one single master definition.
Tie this in with some VMware orchestration capability where you could
say deploy via API the Database components as part of the VM build and
provision the relevant Networking components and it is clear the
potential is going to be huge.

For the Canadians hiding among us, happy belated Canada Day. For the USians, happy Fourth. For the rest of the world, keep on working and we’ll see you next week.