Appliances are a great way to approach system deployments for your VMware environment. We are seeing more and more of this method of delivery of application environments, and with the increased number of vendors jumping on board, this is a sign that something is being done right.
What is an Appliance?
The appliance in a VMware sense is a packaged server with a pre-installed application environment that is provided in OVF format which we can deploy directly into our vSphere environment without having to build the base machine and do all of the installation process ourselves.
Using appliances is much like the physical, black-box approach which can ease the pain of getting a new application environment up and running. Configuration is done minimally through the console, and a web application is almost always the way to complete additional customization and configuration.
Using the OVF Format
OVF, or Open Virtualization Format, is an industry standard for packaging defined by the DMTF (Distributed Management Task Force) to provide vendors and software providers with a supportable and standards based delivery format. Details on the OVF standard can be found here: http://www.dmtf.org/standards/ovf
A virtual appliance will come with a pre-configured virtual disk file and a configuration file to provide the vSphere with what is required to craft together the virtual machine including any additional hardware items such as network cards, drive controllers and anything that can be delivered as virtual hardware via the vSphere platform.
What wizardry is this?
The OVF deployment wizard in vSphere walks you through the configuration of specific virtual hardware including the selection of disk type, location, network type and location, IP configuration and also the VM location including resource pool, cluster and folder.
Very simply, you open the vSphere Client and under the File menu, select Deploy OVF Template. This will bring up the deployment wizard as you can see below.
The end result of the wizard is a fully functioning virtual guest. It doesn’t get much simpler than that.
A question that people may ask is “why use an OVF instead of just a VMDK and VMX file?”. The reason for the use of an OVF is to apply standardized deployment techniques to allow the deployer to make the choice about hardware specifics within their own environment.
Another clear reason is that the OVF standard is defined for open use across hypervisors. Yup, some people use other ones 😉
Using OVF makes the build and deployment of virtual appliances a snap, and for any vendor, enabling their customers is key when getting products to market.
What is the difference between OVF and a virtual appliance?
OVF is a virtual machine packaging method. The virtual appliance is the product itself. It is typically a blackbox type of build which would be not much different than a 1U server that you would have put into your physical network rack.
Using VMware Studio (http://www.vmware.com/products/studio/overview.html) you can build your appliance using a supported operating system (Supported OS list here) and package your application build.
You can also deploy a vApp with an OVF so you are not limited to a single machine deployment. Using the first-boot configuration script you have plenty of options for post deployment configuration. There are also a lot of great resources for building your OVF so getting help is just a few clicks away.
Should OVF replace my VM Templates?
Unless you have a lot of pre-defined applications and packaged builds, you probably won’t see the benefit of using OVF machines for your corporate environment. What you should concentrate on is the automation of your builds with other great tools like vCenter Orchestrator.
There may be some cases in your corporate environment where OVF is appropriate so perhaps you could give it a try and the worst case scenario is that you will become more familiar with build automation and deployment scripting, and nobody will lose in that scenario 🙂
What about upgrades?
The upgrade process can be scary with any environment. Many virtual appliance vendors will provide a simple configuration backup process (export to file, FTP etc…) and you can simply deploy an upgrade in place. It is even possible to use Update Manager to upgrade your virtual appliances.
The long and the short of it is that virtual appliances are fast becoming a part of many production environments and it may be a great way for you to speed deployment and ease the installation process for products. Anything to reduce the workload is definitely a positive step in my opinion.
The VMware Appliance Marketplace
Now that you are ready to take a look, there is no better place to begin than the VMware Virtual Appliance Marketplace. Through the marketplace site you can search for various application solutions from the VMware Certified vendors and from other supported parters who provide appliance based solutions.
So have a look around, and happy deploying!
2 thoughts on “Appliances and OVF: The packaged approach to deployment”
OMG how boring !! WTF!
copy paste and add cartoon pics bwahaha…dude why bother?
Appreciate the feedback. Sorry that it didn’t give much back from the article. If you’re looking for more info I’m always up to add more and expand on anything you’ll need help with. Thanks!