VMware Studio 2.0 helps author, configure, deploy and customize vApps and virtual appliances. vApps support the industry standard Open Virtualization Format (OVF). vApps can be deployed on VMware vSphere 4.0 or in the cloud. vCenter Server 4.0 now supports creating and running vApps, as well as importing and exporting them in compliance with OVF 1.0 standard.
Studio 2.0 is designed to be used by ISVs, developers, IT professionals and members of the virtualization community. It is a free product and is available as a virtual appliance.
VMware Studio Resources
Reduce Development Costs by Building Virtual Applications
VMware Studio is an integrated development tool that packages software applications into virtual appliances and vApps that are ready to run and optimized for VMware product platforms and the cloud. Virtual appliances and vApps generated by VMware Studio contain an in-guest management agent with a web console that an ISV can brand and ship as part of a customized virtual appliance. VMware Studio can build both Linux-based VMs and Windows-based virtual appliances and vApps, running single tier or multi-tier applications.
VMware Studio is now also available as a plug-in for the popular Eclipse IDE. The Studio plug-in for Eclipse enables developers to package their applications and deploy them quickly into a virtual appliance or a vApp. VMware Studio 2.0 also provides the unique capability of not requiring developers to start building a virtual machine from scratch each time. An existing virtual machine built with VMware Studio 2.0 can serve as input for the next build, saving time when only the contents (or application mix) of a virtual machine are changing.
What are vApps?
vApps are software solutions optimized for the cloud, consisting of multiple virtual machines, packaged and maintained as a single entity in OVF format. Just like the UPC bar code contains all information about a product, the vApp gives application owners a standard way to describe operational policies for an application which the cloud OS can automatically interpret and execute. Therefore, vApps are self-describing to and self-managing on the platform they run. vApps can comprise any applications running on any OS, and provide a mechanism for customers to move their applications between internal clouds or external clouds while retaining the same service levels. vApps are considered to be the next generation of virtual appliances. vApps cover a broad and diverse range of virtual applications that may be created by ISVs, developers, enterprise admins or IT professionals. Given the flexibility of vApps, virtual appliances may be viewed as “closed” vApps .
Anyone using VMware vSphere can use the vApp to encapsulate a multi-virtual machine application. ISVs can use VMware Studio to create vApps that can be automatically updated and maintained by VMware vSphere.
Virtual appliances or vApps created by VMware Studio run seamlessly on VMware products such as VMware vSphere, VMware Infrastructure, VMware ESXi, VMware Workstation, VMware Fusion and VMware Server, as well as on third-party virtualization products that support the OVF specification.
vApp and virtual appliance components
Virtual appliances and vApps created by VMware Studio have the following components:
- Operating System: VMware Studio can be used to author vApps on a large number of operating system distros. VMware Studio also supports Just enough Operating Systems (JeOS) - minimal operating system packages derived off standard OS packages, as may be specified by certain developers. This ensures a smaller and more secure footprint.
- VMware Tools: VMware Studio bundles a set of VMware tools during the build of a vApp. It enables better communication between VMware virtualization platforms and the vApp
- Virtual Appliance Management Infrastructure (VAMI): The in-guest management component provides a web console to manage the vApp. VAMI provides the ability to change network settings, update the virtual appliance or vApp, and control the state of the system (shutdown/reboot).
- Application: This developer created application (or a set of applications) performs the intended task for which the virtual appliance or vApp is built.
